← ClaudeAtlas

native-craftlisted

Native-feel declaration for desktop apps. Use when a cross-platform desktop app (macOS+Windows) must feel indistinguishable from native. Invoked before ui-picker for native-desktop targets, not web pages.
Bandersnatch0x/design-playbook · ★ 2 · Web & Frontend · score 58
Install: claude install-skill Bandersnatch0x/design-playbook
# native-craft **Native-feel** is a Design I/O **platform declaration**: it fixes the render-surface seam and the native conventions before any web shell is picked. It is the native-desktop twin of `craft-guard` (which owns web craft); the two do not overlap. Inspired by yetone/native-feel-skill (MIT) - see `NOTICE`. Depth lives in [`references/native-feel.md`](references/native-feel.md); do not load it until this skill applies. ## When to apply / skip - **Apply** when the target is a desktop app that must feel native on macOS + Windows (launcher, system utility, all-day productivity tool). - **Skip** when: one OS only (build pure native), Electron-is-fine polish bar, internal tool, cold-start < 100 ms hard, or pure web/mobile. The decision gate in `references/native-feel.md` rules this stack **out** for those shapes - say so directly. ## The declaration: place the seam at the rendering surface The cross-platform boundary is drawn at the **WebView surface**, nowhere else. - **Below the seam** - windowing, hotkeys, materials, file dialogs, tray, a11y, input methods, context menu - **native**, written twice in idiomatic Swift / C#. No abstraction is fast or correct enough. - **Above the seam** - React tree, business logic, extension API, AI orchestration - **shared**, written once in TS. Test every platform decision: *is this above or below the rendering surface?* Below -> write it twice. Above -> write it once. Refuse to draw the line elsewhere. ## Native-feel tenets