← ClaudeAtlas

design-discipline-reviewlisted

Improve a screen that already exists — operate it, name the deficits, gather references, rebuild in small passes within the declaration's scope of change, compare. 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 `review` entry in Ways in. Write no record of the run to any file: what you named, gathered, and changed, you say to the person. 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. 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 `../design-discipline/` is not installed beside this skill, say this and stop: "The design-discipline skill isn't installed beside this command. Install the five directories toge