gentle-design

1## Activation Contract
2 
3Use this skill by default whenever the user asks, in plain words, for a UI design, mockup, screen, landing page, or visual directions, or iterates on artboards under `design/`. Do not use it to implement production code in the project's stack.
4 
5The `/gentle:design` commands are optional shortcuts: every action also works from a plain request, through this skill and the `gentle_design` tool (`list`, `open`, `stop`, `implement`, `handoff`).
6 
7## Hard Rules
8 
9- Every artboard is one self-contained HTML file: inline CSS, JS, and SVG; system font stacks only. Never reference external URLs, CDNs, remote fonts, images, or scripts.
10- Use realistic content for the audience; no lorem ipsum or placeholder names.
11- Accessible markup: semantic elements and landmarks, WCAG AA contrast, visible focus styles, `prefers-reduced-motion` respected for any motion.
12- When `design/system.md` exists, read it first and use only its tokens and component rules; run the Self-check from "Design system sync" before finishing any artboard.
13- Ask at most one clarifying question, and only when the brief lacks the goal or the content.
14- Iterating edits only the targeted artboard. Never rewrite the others.
15 
16## Decision Gates
17 
18| Situation | Action |
19| --- | --- |
20| New brief | Write N clearly different directions (3 by default, or the number asked) to a new `design/<slug>/` |
21| Feedback on one artboard | Edit that file only; keep its manifest entry, update `tradeoff` if it changed |
22…