iterate

Iterate

Fast revision path for the sp-site-design-harness. create-design makes designs; this skill changes them. The whole point is speed: read as little as possible, edit directly, verify only what changed.

Do not load create-design's references, re-read research/brief.md, spawn critic subagents, re-run the deletion pass, or narrate CSS reasoning. The user is a designer who codes. When they name a variable, a selector, or a value, do exactly that.

Step 0 — Resolve the target (cheap)

Scope root: an explicit path in the arguments, else git rev-parse --show-toplevel, else $PWD (same resolution as /publish-design-options).

State	Target
No handoff/DESIGN.md	HTML phase. directions/NN-<slug>.html. Ask which one only if the request doesn't make it clear.
handoff/DESIGN.md exists and a theme path is known (arguments, or a .theme-path file at the scope root, absolute or relative to it)	Theme phase. The block theme.
handoff/DESIGN.md exists, no theme path	Ask once for the theme folder, then write it to .theme-path so nobody has to ask again.

After handoff, directions/*.html is frozen. Never edit it. If asked to, say it's frozen and make the change in the theme instead. Two live sources drift apart. See ../../DECISIONS.md (2026-09-25). If the request names a direction other than the one DESIGN.md describes, say so and ask before doing anything.

Step 1 — Classify, say so in one line, then act

Give each request a level and state it in one line, e.g. L0 — swapping --color-border to --stone in 02-conditions.html. The user can override ("just do it", "treat this as L1"). If the level isn't obvious, read references/levels.md.

L0 — Direct edit

Token or variable swap, copy change, one property.

• HTML: read only the :root block and grep for the selector or variable. Theme: read only the relevant theme.json settings/styles key, or grep the pattern/template.
• A color named in words ("plum", "the terracotta") means the palette token of that name if one exists. Otherwise pick a value that fits the palette and report it.
• Edit. That's it: no screenshot unless asked, no references, no critique.
• One exception, contrast. Whenever a color changes (a token's value, or a usage switched to a different token), check numerically against the surface each usage sits on: text 4.5:1 (3:1 at large sizes); borders, separators, focus rings and other UI 3:1. Reading the rules that set those surfaces is part of the check. Accessibility outranks everything (../../references/instruction-priority.md). Report a failure and suggest the nearest passing value rather than silently shipping it. Also update anything derived from the old value, such as a hard-coded hover shade or a contrast ratio recorded in .tokens.md.
• If the file has no role alias for what was asked (e.g. no --color-border, so borders reference --stone directly), make the change at each usage and offer to add the alias so next time it's a one-line change.