← ClaudeAtlas

design-discipline-inspectlisted

Run every applicable design inspection against every screen the product has and return the repair list, each repair marked structural or surface, without touching the product. Part of design-discipline.
shumatsumonobu/vitruvian-design · ★ 1 · Web & Frontend · score 75
Install: claude install-skill shumatsumonobu/vitruvian-design
Read `${CLAUDE_SKILL_DIR}/../design-discipline/SKILL.md` and follow its `inspect` entry in Ways in. Read `${CLAUDE_SKILL_DIR}/../design-discipline/inspections.md` for the counts and checks: every rule file's Inspection is in that one file. Open a rule file only for a section a line there points at. Write the repair list to `.design/repairs.md`, in place of any list there, and write no record of the run to any file: what you counted and found, you say in your last message. 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. When the conversation has been compacted — its earlier turns replaced by a summary — read that SKILL.md and the rule files of the step you are on again before your next tool call, and say so to the person. Everything that skill references sits beside it — its rules are `${CLAUDE_SKILL_DIR}/../design-discipline/rules/`. Do not search for any of it. If