← ClaudeAtlas

design-discipline-fixlisted

Work a design repair list down to empty within the declaration's scope of change — at most five repairs per pass, the failed counts and the counts on what the pass touched rerun after each, and every applicable Inspection once after the last. Part of design-discipline.
shumatsumonobu/vitruvian-design · ★ 1 · Web & Frontend · score 77
Install: claude install-skill shumatsumonobu/vitruvian-design
Read `${CLAUDE_SKILL_DIR}/../design-discipline/SKILL.md` and follow its `fix` entry in Ways in. Put each question under What it asks you through the AskUserQuestion tool where that tool exists. Every line of text you write is read by the person — a progress line or a note to yourself included — so every one is in the user's language. Before your first tool call of any kind, say one line to the person, in the user's language, on what you are about to do. Every line after it stays in that language. Code and its comments may stay in English; the line you write after an edit, a script's output, a failed call, or a subagent's answer is in the user's language however much English came before it. A line that says what you will do next — "Next, I'll…", "Now I'll…" — is the line a long run writes in English most often: its first word is in the user's language. After the last pass, run every rule file's Inspection, not only the counts the passes touched — a list of one repair included — before you say the run is done; they are gathered in `${CLAUDE_SKILL_DIR}/../design-discipline/inspections.md`, read in place of opening each rule file. What that run finds new, the reviewer's findings among them, is one more pass before the end, as the `fix` entry in Ways in says. Take each repair off `.design/repairs.md` as you make it; what is left when the run ends, say to the person in your last message, then delete that file — it stays only where the scope of change is report only. Write no record