gentle-ui-design

1## Activation Contract
2 
3Use for web and product interfaces when shaping, implementing, or assessing a user experience. Pair with `gentle-design` when producing artboards: gentle-design owns delivery, this skill owns UX quality. Use `gentle-ai-tui-design` for terminal interfaces.
4 
5## Hard Rules
6 
7- Keep a read-only critique read-only; do not install tools or dependencies for this guidance.
8- Establish the user's job and success condition before appearance. Ask only when missing intent would materially change a decision.
9- Reuse the project's brand, components, and platform conventions; avoid universal aesthetic bans.
10- Do not invent evidence or conceal inaccessible controls. Model real content ranges and states; this guidance adds no hooks, detectors, or mandatory tool chains.
11 
12## Decision Gates
13 
14| Need or symptom | Load and apply |
15| --- | --- |
16| Unclear purpose, weak copy, or generic direction | `references/task-and-content.md` |
17| Search, large collections, or difficult comparison | `references/browse-and-compare.md` |
18| Flat hierarchy, clutter, or weak feedback | `references/composition-and-feedback.md` |
19| Narrow screens, input access, or missing states | `references/adaptive-interfaces.md` |
20 
21## Execution Steps
22 
231. Identify the audience, primary job, constraints, and likely content sizes; inspect existing project conventions when available.
242. Load only the relevant references and select defaults or justified exceptions for the task.
25…