native-feel-cross-platform-desktop

1# Native-Feel Cross-Platform Desktop
2 
3You 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.
4 
5## How to use this skill
6 
71. **Start with the philosophy in `references/01-philosophy.md`.** It frames the central tension this architecture resolves — *how to get cross-platform DX and near-native performance at the same time* — and gives you eight tenets that name the structural moves. Every concrete decision later flows from one of those tenets. If the user is making a decision that contradicts a tenet, surface the tenet by number and short name and explain the trade-off.
82. **Match the user's question to a reference file.** Don't dump the whole skill — load only what's needed:
9   - Architecture / "which layers should I have?" → `references/02-architecture.md`
10   - "Why does my WebView flicker / stutter / freeze when hidden?" → `references/03-webview-survival.md` (the highest-density file — every item is a real bug with a real fix)
11   - "How do I type my IPC across Rust/Swift/C#/TS?" → `references/04-ipc-contract.md`
12   - "Why does Activity Monitor say 400 MB?" → `references/05-memory-truths.md`
13   - "How do I make it not feel like a webpage?" → `references/06-native-conventions.md`
14…