Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
This skill guides the architecture of cross-platform desktop apps that must feel indistinguishable from native ones on macOS, Windows, and Linux. It draws on patterns from production tools like Raycast, offering reference files on WebView survival, IPC contracts, memory management, and native conventions. A decision tree and ship-readiness checklist help developers avoid the common traps—Electron theming, Tauri abstraction, dual UI codebases—that give cross-platform apps their characteristic web-like feel. It serves developers building desktop apps where every animation, hotkey, and window material must match the OS.
WHO IT'S FOR
Desktop App Architects
designing cross-platform native-feel architecture
Cross-Platform Desktop Developers
building native-feel desktop apps with WebView
Product Managers Evaluating Tech Stacks
evaluating Electron alternatives for desktop apps
Quality Assurance Engineers
auditing native feel and performance of desktop apps
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
Installs: User-level installation of the complete native-feel skill repository as `native-feel-cross-platform-desktop/`, including SKILL.md, references/, and checklists/. · Claude Code
In an AI agent session, paste the following prompt exactly. The agent should substitute its own user-level skills directory for the described location; for Claude Code, the documented example is `~/.claude/skills/`.
Install the native-feel skill for me:
1. Clone https://github.com/yetone/native-feel-skill into your
user-level skills directory as `native-feel-cross-platform-desktop/`
(whatever path your agent reads skills from on this machine — e.g.
`~/.claude/skills/` for Claude Code).
2. Verify that SKILL.md plus the references/ and checklists/ subdirs
are present.
3. Confirm the install path when done.
Assess whether the architecture fits a desktop app
Uses native-feel-cross-platform-desktop
Project description, including the native-feel requirement
Target operating systems
Relevant constraints such as UI sharing, performance, or platform integration
Use the native-feel-cross-platform-desktop skill to assess whether its architecture fits [PROJECT DESCRIPTION] on [TARGET OPERATING SYSTEMS]. Start with the philosophy and run the documented decision tree before recommending an architecture. Give me a brief fit/no-fit conclusion, the most relevant tenet, and the main trade-off.
Use the native-feel-cross-platform-desktop skill to diagnose this WebView problem: [FLICKER, STUTTER, OR HIDDEN-WINDOW FREEZE DESCRIPTION]. The app uses [WKWEBVIEW OR WEBVIEW2] on [OPERATING SYSTEM]. Consult the WebView survival guidance and return the likely cause, the smallest supported fix, and its trade-off.
Use the native-feel-cross-platform-desktop skill to review this IPC boundary: [INTERFACE OR MESSAGE DESCRIPTION]. The participating languages are [LANGUAGES]. Propose a small typed-contract approach that avoids hand-maintained type drift, and identify the main implementation trade-off.
Claude
Cursor