macos-design — Claude Code skill: what it does, how to install
The macos-design skill guides macOS-style desktop UI work with system patterns, light and dark themes, and window behavior. Use it for apps and utilities.
MIT 192 installs ★ 3,785 updated 2026-10-25
npx skills add davepoon/buildwithclaude --skill macos-design -a claude-codeWhat macos-design does
macos-design guides the structure of a macOS interface: a top bar for global actions, a sidebar for navigation, a content area, a draggable window zone, and integrated traffic lights. It also covers empty states, search, drag and drop, keyboard shortcuts, feedback for state changes, and brief onboarding.
For React or HTML artifacts, the skill describes simulated window chrome, a system font stack, backdrop-filter: blur(), rounded surfaces, layered shadows, and prefers-color-scheme. With Electron, Tauri, or native frameworks, it points to system title bars, appearance settings, accent colors, and native drag-and-drop APIs.
The required starting reference is references/layout-and-composition.md; without it, the core layout guidance is incomplete.
What it helps with
- design a native-feeling macOS desktop interface
- split an app screen into a top bar, sidebar, and content area
- support light and dark appearance without simply inverting colors
- plan keyboard shortcuts, search, and state-change feedback
- build simulated macOS window chrome in React or HTML
Example prompts for the agent
- Design a macOS desktop app with a top bar, sidebar, and integrated traffic lights.
- Review this interface and add light and dark appearance, empty states, search, and transitions for state changes.
- Build this React web artifact with simulated macOS window chrome, the system font stack, and
prefers-color-scheme.
How to install macos-design
1Skills CLI (Vercel)
npx skills add davepoon/buildwithclaude --skill macos-design -a claude-code2Manually: put the files in place
~/.claude/skills/macos-design/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/macos-design/
1Skills CLI (Vercel)
npx skills add davepoon/buildwithclaude --skill macos-design -a codex2Manually: put the files in place
.agents/skills/macos-design/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add davepoon/buildwithclaude --skill macos-design -a cursor2Manually: put the files in place
.cursor/skills/macos-design/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install davepoon/buildwithclaude plugins/all-skills/skills/macos-design2Manually: put the files in place
.github/skills/macos-design/SKILL.md1Skills CLI (Vercel)
npx skills add davepoon/buildwithclaude --skill macos-design -a gemini-cli2Platform CLI
gemini skills install https://github.com/davepoon/buildwithclaude --path plugins/all-skills/skills/macos-designManually: put the files in place
.devin/skills/macos-design/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add davepoon/buildwithclaude --skill macos-design -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about macos-design
How do I install macos-design in Claude Code?
Run npx skills add davepoon/buildwithclaude --skill macos-design -a claude-code, then use ~/.claude/skills/macos-design/SKILL.md.
What does macos-design do?
It guides macOS-style UI work with system-oriented layout, appearance modes, search, keyboard shortcuts, drag and drop, and interaction feedback.
Which reference should I read before building a macOS app?
Start with references/layout-and-composition.md, which is required for all macOS apps. Interfaces with panels, popovers, or toasts also use references/interaction-patterns.md.
Source text
SKILL.md · MIT
--- name: macos-design category: design description: Design and build native-feeling macOS application UIs. Use this skill whenever the user asks to create a desktop app, macOS app, Mac-style interface, Apple-style UI, system utility, or anything that should look and feel like a native Mac application. Also trigger when users mention "native feel", "desktop app design", "Apple design patterns", "sidebar layout", "traffic lights", or want to build tools/utilities that feel like they belong on macOS. This skill covers layout, composition, interaction patterns, animations, light/dark mode, and all the subtle details that make an app feel like Apple built it. --- # macOS Native App Design Skill Build interfaces that feel like they belong on the user's computer — not websites crammed into a window. ## Core Philosophy A native app is not a destination. It is a **system tool** that lives where the user needs it. Design every interaction around this principle: appear when needed, get out of the way immediately after. ## Before You Code Read these references based on what you're building: - **All macOS apps** → Read `references/layout-and-composition.md` (required) - **Apps with keyboard shortcuts, panels, toasts, popovers** → Read `references/interaction-patterns.md` - **Light/dark mode, color, typography** → Read `references/visual-design.md` ## Quick-Start Checklist Use this as a pre-flight before writing any code: 1. **Layout**: Top bar for global actions, sidebar for navigation (skip if nav is minimal), center for content 2. **Traffic lights**: Integrate into the UI — top bar or sidebar, never floating awkwardly 3. **Window drag zone**: Top ~50px must be draggable, keep it uncluttered 4. **Empty states**: Show them. Progressive disclosure — only reveal UI when it's useful 5. **Keyboard shortcuts**: Every primary action needs one. Every shortcut needs visual feedback 6. **Light + Dark mode**: Design both. Do NOT directly invert colors (see visual-design reference) 7. **Search**: Always prominent and accessible. Consider floating search bar or command palette 8. **Drag and drop**: Content in AND out of the app. This is non-negotiable for native feel 9. **Micro-animations**: Every state change gets a transition. No interaction without feedback 10. **Onboarding**: Brief, modal-based, teaches shortcuts through doing (not reading) ## Implementation Notes When building as a web artifact (React/HTML): - Simulate the macOS window chrome (title bar, traffic light dots, rounded corners) - Use `-apple-system, BlinkMacSystemFont, "SF Pro Display", "SF Pro Text"` font stack - Use `backdrop-filter: blur()` for native vibrancy/translucency effects - Rounded corners: 10px for windows, 8px for cards, 6px for buttons, 4px for inputs - Respect `prefers-color-scheme` media query for automatic light/dark switching - Shadows should be subtle and layered, not a single heavy drop shadow When building with Electron, Tauri, or native frameworks: - Use system title bar integration where possible - Respect system accent color and appearance settings - Use native drag-and-drop APIs, not polyfills
© davepoon · MIT · davepoon/buildwithclaude