macos-design
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.
95
92%
Does it follow best practices?
Impact
99%
1.13xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that excels across all dimensions. It provides specific capabilities, comprehensive trigger terms that users would naturally use, explicit 'Use when' guidance, and a clearly distinctive niche focused on macOS native UI design. The description is thorough without being unnecessarily verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and capabilities: 'layout, composition, interaction patterns, animations, light/dark mode' and describes the goal of building 'native-feeling macOS application UIs'. It goes beyond naming a domain and enumerates specific aspects covered. | 3 / 3 |
Completeness | Clearly answers both 'what' (design and build native-feeling macOS application UIs covering layout, composition, interaction patterns, animations, light/dark mode) and 'when' (explicit 'Use this skill whenever...' clause with detailed trigger scenarios and terms). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'desktop app', 'macOS app', 'Mac-style interface', 'Apple-style UI', 'system utility', 'native feel', 'desktop app design', 'Apple design patterns', 'sidebar layout', 'traffic lights'. These are highly natural phrases a user would actually use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused specifically on macOS native-feeling UIs. The triggers are clearly scoped to Apple/Mac-specific design patterns and would be unlikely to conflict with generic web UI, mobile, or Windows-focused skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill that efficiently communicates macOS design principles with good progressive disclosure to reference files. Its main weakness is the lack of executable code examples — the implementation notes describe what to do (specific CSS values, font stacks) but don't provide copy-paste ready component code. The checklist format and reference structure are strong.
Suggestions
Add a concrete, executable code example showing a minimal macOS-style window chrome component (title bar with traffic lights, sidebar, content area) in React/HTML+CSS to boost actionability.
Consider adding a small inline code snippet for the most common pattern (e.g., a styled top bar with draggable region and traffic light dots) so users can immediately see the implementation approach.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It doesn't explain what macOS is or how React works. Every section delivers actionable guidance without padding. The philosophy section is one sentence, which is appropriate framing without bloat. | 3 / 3 |
Actionability | The checklist and implementation notes provide concrete guidance (specific CSS properties, font stacks, border-radius values), but there are no executable code examples — no copy-paste ready component snippets showing a sidebar layout, traffic light implementation, or window chrome simulation. The guidance is specific but not fully executable. | 2 / 3 |
Workflow Clarity | The workflow is clear: read references based on what you're building, then use the pre-flight checklist before coding, then follow implementation notes. For a design skill (not a destructive/batch operation), this sequencing is appropriate and unambiguous. The checklist format provides a clear validation mechanism. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure — the SKILL.md serves as a concise overview with clear, well-signaled one-level-deep references to three specific reference files based on what the user is building. Content is appropriately split between the overview and detailed reference documents. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- davepoon/buildwithclaude
- Commit
7cc63f3
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.