consult-user-mcp: Command for Claude Code

<visual_direction> $ARGUMENTS </visual_direction>

If <visual_direction> is empty, stop and ask for it in one sentence. Do not invent one.

If it names a file or a design-handoff archive, unpack it to your scratchpad and read it before anything else. A handoff usually contains two kinds of document and they are not equal:

• A decision sheet ("pick one from each row") is a menu of options that may never have been answered. It is not the direction.
• A resolved system ("locked system: …", a logo-construction page, exported assets) carries the picks that were actually made. That is the direction. Where the two disagree, the resolved system wins.

Read the exported assets too — an .svg mark tells you the final geometry and which element owns the accent. A handoff may quote values from the current Theme.swift. Those are the appearance you are blind to. Take the system (which hue, which ground, which face, which element carries the accent) and discard any literal value it attributes to today's build.

Treat the blindfold as a rule, not just a wall:

• Do not read, search, reconstruct, or ask about the current appearance. If a tool call is denied, that is the system working. Move on — never route around it with a different tool, a shell command, or git history.
• The deny-list is not airtight and you must not lean on it. Theme/, Components/, Dialogs/ and the existing skins hold the current appearance. <chassis_api> below reproduces every declaration you need from them, with types. If you find yourself about to grep one of those paths, the answer is already in this brief — go read it again. If a value from the existing UI reaches you anyway, discard it.
• Never run a dialog without DIALOG_SKIN set to your own skin's id. The default renders the current UI.
• Screenshot only the window id returned by test-cases/capture-dialog.swift, never the screen or another window. Do not open the built app's other windows, the docs site, or any image in the repo.

If you catch yourself reasoning from "how it probably looks today", stop. The contract is the only input.

1. Pick your skin's name and confirm dialog-cli/Sources/DialogCLI/Skins/<YourName>/ is empty — find … -type f and git ls-files …. A stub directory may exist from an earlier attempt. Say in your first message to the user what folder you are building in and whether it was empty. If it has contents, stop and ask before touching them.
2. Confirm the repo is clean (git status). Commit anything outstanding first.

<the_contract> Read UI-BEHAVIOUR-SPECIFICATION.md in full before writing anything. It is the complete behavioural contract for eight surfaces and it is deliberately free of visual design. It is long; read it in two passes rather than skimming one.

How to read it:

• Read the tier before the requirement (§0.1). LAW is invariant — keyboard model, outcome model, what the agent receives. CAPABILITY means the person must be able to do a thing and the form is yours. DEFAULT is one workable answer you may replace outright. §0.2 lists what the contract deliberately does not specify — arrangement, decomposition, grouping, idiom — and that list is the size of your freedom.
• §3 is a list of capabilities, not components. Two entries may be one element; one entry may be three. Assembling it top to bottom in the order written is the failure mode §0.3 exists to prevent — run both checks there before you commit to a design.
• Everywhere it says a thing MUST be distinguishable, distinct, or not read as something else, it is handing you a design problem. Those are the requirements you are being paid to answer. Collect them first.
• §7.5 lists things a style may add that the default has not: a label naming the surface kind, an ordinal beside each option, a count of what is chosen, a placeholder on the text surface. It ends with "anything else" — the list is examples, not permission.
• §10 lists behavioural defects in the current build. You inherit the behaviour, not the defects — where a defect is a visual failure (10.4, 10.9, 10.12, 10.14, 10.26 especially), fix it in your skin rather than reproducing it.
• Where it is silent on appearance, you decide. Silence is permission, not an omission.