watchos-design-guidelines
by ehmowatchos-design-guidelines is a focused Apple Watch UI design skill for watchOS apps, complications, workouts, notifications, and wrist-based interactions. Use this watchos-design-guidelines guide to check glanceability, Digital Crown behavior, Always On states, accessibility, and whether a screen is usable on the wrist.
This skill scores 78/100, which means it is a solid listing candidate for directory users who need Apple Watch design guidance. It has enough triggerability and rule-based workflow content to reduce guesswork versus a generic prompt, though users should still expect a documentation-heavy skill rather than an execution-oriented tool.
- Clear trigger language for watchOS app, complication, workout, Digital Crown, and wrist-interaction tasks.
- Substantial rule set and sectioned guidance: valid frontmatter, long SKILL.md, 9 H2s/28 H3s, plus a cross-referenced rules index.
- Helpful supporting metadata and AGENTS.md that explain purpose, when to use, and key principles with Apple documentation references.
- No install command or scripts, so adoption is manual and there is no automation or runtime integration evidence.
- Placeholder markers and truncated excerpts suggest some polish gaps, so users may need to consult multiple files to fully understand the workflow.
Overview of watchos-design-guidelines skill
watchos-design-guidelines is a focused Apple Watch UI design skill for teams that need watchOS guidance faster than a full HIG read. It is best for product designers, iOS/watchOS developers, and AI-assisted reviewers who want to validate whether a screen, complication, workout flow, or notification is actually usable on the wrist.
What this skill is for
Use this watchos-design-guidelines skill when the real job is to decide what belongs on a tiny, time-limited display and what should be removed. It helps with glanceability, Crown-driven interaction, Always On behavior, accessibility, and watch-specific tradeoffs that generic mobile prompts often miss.
Why it is worth installing
The main value is decision clarity: the guidance is organized around practical watch constraints, not broad design theory. If you are comparing layouts, writing a design review prompt, or checking whether an experience fits Apple Watch conventions, this skill gives you a tighter, more installation-ready watchOS design guideline workflow.
Best fit and misfit cases
Best fit: new watch UI concepts, interface critique, complication strategy, workout and health flows, and wrist-based interaction checks. Less useful: general iPhone UI work, brand design, or tasks where watchOS is only incidental and no screen-level tradeoff is being made.
How to Use watchos-design-guidelines skill
Install it and load the right files
Install with npx skills add ehmo/platform-design-skills --skill watchos-design-guidelines. After install, start with SKILL.md, then read AGENTS.md, metadata.json, and rules/_sections.md to capture the rule structure, priority system, and cross-reference IDs before you draft or critique anything.
Turn a rough idea into a useful prompt
The watchos-design-guidelines install works best when you provide the screen, user goal, and constraint in one sentence. Strong inputs look like: “Review this watchOS workout summary screen for glanceability, Crown navigation, and text length,” or “Design a complication that shows battery status without scrolling or long labels.”
What input the skill needs
Include the feature type, the primary user action, and the context of use. For example: watch face complication, workout pause screen, notification action, settings picker, or quick status card. If you omit context, the output will usually overgeneralize and miss whether the design should optimize for brief glance, rapid adjustment, or passive monitoring.
Practical workflow for better output
Use the skill in two passes: first ask for a rule-based critique or layout outline, then ask for a revised version that removes any violations. If you are evaluating an existing mockup, tell it which files or screenshots matter and ask it to prioritize the most constrained screen first, since watchOS design often fails at the first glance rather than the full flow.
watchos-design-guidelines skill FAQ
Is this better than a normal prompt?
Yes, when the work depends on watch-specific constraints. A normal prompt may produce generic mobile advice, while watchos-design-guidelines is tuned for the short attention window, small screen, Digital Crown behavior, and the “raise-glance-lower” interaction model.
Do I need watchOS experience to use it?
No. The skill is useful for beginners because it surfaces the core constraints and common mistakes early. That said, you will get better results if you provide a concrete interface goal instead of asking for “watch app ideas” in the abstract.
When should I not use it?
Do not reach for this skill when you are designing a phone-first product, a tablet dashboard, or a watch-themed marketing asset. It is most valuable when the output must be judged by whether it works on an actual Apple Watch screen.
What if my task is only partially watch-related?
Use it if the watchOS part changes the interaction model, even if the main product is broader. A notification, shortcut, or health summary that appears on the wrist still needs watchos-design-guidelines thinking because space, timing, and input are fundamentally different there.
How to Improve watchos-design-guidelines skill
Give the first prompt more structure
The strongest inputs state the screen type, the top user task, and the constraint you care about most. Example: “Improve this watchOS medication reminder so the next action is visible in 2 seconds and the text fits without scrolling.” That is better than “make it cleaner” because it tells the skill what to optimize.
Watch for the common failure modes
The most common misses are too much text, unclear hierarchy, overreliance on scrolling, and ignoring wrist-down behavior. If your first output feels generic, ask it to re-check against glanceability, Crown input, and any constraint that affects the first screen only.
Iterate using rule IDs and concrete evidence
If the repository output cites a rule or section ID, use that in your next prompt to tighten the revision. For example, ask for a redesign that resolves glanceability and accessibility together, then verify the result against the relevant watchOS design guideline sections instead of asking for another broad rewrite.
Improve fit by supplying real content
For better watchos-design-guidelines usage, provide actual labels, metrics, and actions rather than placeholders. A prompt with “Heart rate: 128 bpm, Recovery: 84%, button: Start Cooldown” produces far stronger guidance than one that says “show fitness data,” because the skill can judge what deserves the primary screen.