design-directionslisted
Install: claude install-skill lloydbrian/lloydbriantech-ascent
# design-directions
Helps the operator choose a look and feel with real screens to compare, before code depends on it. It is the decide half of the ui-ux-designer role; [ux-review](../ux-review/SKILL.md) and [design-system-check](../design-system-check/SKILL.md) are the verify half. It is a sibling of `ux-review`: it uses that skill's contract, evidence rules and severities.
Each direction is a token set (Design Tokens format 2025.10, light and dark), not free-form CSS, so every option can be checked for contrast and carried straight into the repository. Sources: [the direction catalog](../../directions/README.md), [design-tokens.md](../../references/design-tokens.md), and the [accessible page blueprint](../../blueprints/accessible-page/README.md), which is the mock template.
`frontend-design` (installed with this plugin) guides new directions in Step 6, and `design:design-critique` can comment on a gallery. This skill keeps the catalog, the checks and the hand-off.
## Rules
- **Mocks are the only files this skill writes**, in the session scratchpad, or in `tmp/ux-mocks/` when `git check-ignore tmp/ux-mocks` confirms it is ignored. Never write tracked files, token files or styles in the repository. The ADR, the token file and the contract change are proposals the operator commits.
- **Every option shown has passed the checks** (Step 4). A direction that fails is fixed or dropped, never shown with a footnote.
- **No real personal data in mocks.** Use the project's public