
Native Feel Cross Platform Desktop
If you're building a launcher, system tray utility, or any desktop app that needs to run on macOS and Windows without screaming "I'm a web app," this walks you through the architecture Raycast actually ships: native shell in Swift or C# owns the window and materials, system WebView renders a shared React UI, Rust handles heavy lifting, and everything talks through typed IPC contracts. It's opinionated about when this stack makes sense and when it doesn't, includes a 30-item ship readiness checklist, and dedicates an entire file to WebView throttling bugs you will hit. Not for Electron-style apps or anything that can tolerate feeling like a webpage. The skill is basically a distillation of real production choices with all the trade-offs surfaced up front.
- skills.sh installs
- 641
- GitHub stars
- 2K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add yetone/native-feel-skill --skill native-feel-cross-platform-desktop --agent claude-codeInstalls into .claude/skills of the current project.
Files
Native-Feel Cross-Platform Desktop
You are advising on the architecture of a cross-platform desktop app that must feel native. This skill captures the philosophy, architecture, and concrete pitfalls — distilled from Raycast's public technical deep-dive on their 2.0 rewrite and verified by reverse-engineering the shipping Raycast Beta.app binary on macOS.
How to use this skill
Sponsors
Details
- Repository
- github.com/yetone/native-feel-skill
- Categories
- Code Review & Quality, Debugging, Mobile Development
- First seen
- Jun 3, 2026