Skills native-feel-cross-platform-desktop

📦

native-feel-cross-platform-desktop

Name: native-feel-cross-platform-desktop
Author: yetone

Content revision r1 Safe ⚙️ External commands🌐 Network access📁 Filesystem access

Design Native-Feeling Desktop Apps

Cross-platform desktop teams often trade native feel for shared UI speed. This skill guides Claude, Codex, and Claude Code through architecture, WebView, IPC, memory, and launch-readiness checks.

Supports: Claude Codex Code(CC)

🥉 79 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "native-feel-cross-platform-desktop" from https://skillstore.io/skills/yetone-native-feel-cross-platform-desktop.md and its manifest at https://skillstore.io/api/skills/yetone-native-feel-cross-platform-desktop/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/yetone-native-feel-cross-platform-desktop.md Signed manifest GET /api/skills/yetone-native-feel-cross-platform-desktop/manifest Signed lockfile GET /api/skills/yetone-native-feel-cross-platform-desktop/lockfile

Test it

Using "native-feel-cross-platform-desktop". My Electron app feels web-like on macOS. Where should I start?

Expected outcome:

Start with the ship-readiness checklist, especially cursor behavior, native sheets, system accent color, and platform materials.
Keep Electron if the goal is good enough polish, but expect a ceiling on native window behavior and material fidelity.
Measure the gap with a short user-visible audit before considering a rewrite.

Using "native-feel-cross-platform-desktop". Should a new launcher use native UI or a shared React WebView?

Expected outcome:

Use the decision tree first: cold-start target, memory floor, extension needs, team skills, and delivery runway matter.
Choose native UI when sub-100ms launch or very low memory is mandatory.
Choose the hybrid architecture when shared iteration speed and extensions justify the WebView and Node baseline.

Using "native-feel-cross-platform-desktop". Our memory looks high in Activity Monitor.

Expected outcome:

Separate memory pressure from resident size before changing architecture.
Check dirty memory hotspots, then profile WebView, Node, and Rust separately.
Avoid migrating features to native only to reduce a number users may not perceive.

Security Audit

Safe

v4 • 7/8/2026 Open versioned report

Targeted review found the flagged patterns are documentation, architecture examples, or user-directed installation text. No executable scripts, hidden data collection, credential handling, prompt-injection attempt, or network exfiltration behavior was found in the audited skill files.

Files scanned

1,928

Lines analyzed

Review items

False positives ignored

Risk Factors

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/yetone-native-feel-cross-platform-desktop/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/yetone-native-feel-cross-platform-desktop/security.svg)](https://skillstore.io/skills/yetone-native-feel-cross-platform-desktop?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/yetone-native-feel-cross-platform-desktop?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/yetone-native-feel-cross-platform-desktop/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/yetone-native-feel-cross-platform-desktop.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

yetone. (2026). native-feel-cross-platform-desktop security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/yetone-native-feel-cross-platform-desktop/audits/4

BibTeX citation

@techreport{yetone-yetone-native-feel-cross-platform-desktop-2026,
  author = {yetone},
  title = {native-feel-cross-platform-desktop security audit report (audit version 4)},
  institution = {Skillstore},
  year = {2026},
  number = {4},
  url = {https://skillstore.io/skills/yetone-native-feel-cross-platform-desktop/audits/4},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "native-feel-cross-platform-desktop security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
  - name: "yetone"
date-released: "2026-07-08"
url: "https://skillstore.io/skills/yetone-native-feel-cross-platform-desktop/audits/4"
identifiers:
  - type: other
    value: "skillstore:yetone-native-feel-cross-platform-desktop:audit:4"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Audit a Web-Wrapped Desktop App

Find the visual, input, and windowing issues that make an Electron or Tauri app feel like a website.

Choose a Cross-Platform Architecture

Decide whether a native shell, system WebView, Node backend, and Rust core fit project constraints.

Prepare a Native-Feel Ship Review

Run readiness checks for launch behavior, keyboard handling, materials, memory, and platform conventions.

Try These Prompts

Audit My App Feel

My desktop app runs on macOS and Windows but feels like a web app. Use this skill to run the native-feel checklist and give prioritized fixes.

Pick the Right Stack

I am starting a desktop app that must feel native on macOS and Windows. Run the decision tree and recommend the architecture with trade-offs.

Plan the IPC Boundary

Help me design the IPC contract between native shell, WebView, Node backend, and Rust core. Focus on schema ownership and generated clients.

Review WebView Performance Risks

Review my WebView desktop architecture for launch latency, hidden-window throttling, animation flicker, memory accounting, and native material integration.

Best Practices

Run the decision tree before recommending this architecture.
Keep platform-owned behavior in native shell code and shared product UI in React.
Use one declared IPC schema and generate typed clients for each runtime.

Avoid

Choosing Electron or Tauri only because they sound lighter or easier.
Hand-writing IPC types separately in Swift, C#, TypeScript, and Rust.
Optimizing memory numbers before checking memory pressure and user-visible latency.