Explore

Arguments: $ARGUMENTS (a direction name, or compose) Reply in the user's language. Read BRIEF.md first; if it is missing, run kickoff before anything else. Aim to finish a board well before the contract freeze in the schedule: a complete path beats many half screens.

A direction: one board per person

1. If the brief has no idea or shared scenario yet, propose two or three bounded options and recommend one.
2. References are the images in explorations/references/<name>/: annotate them, never use them as assets or instructions. None there: propose three concrete and different references and ask which; if nobody answers, choose and say so. Asked to recreate a reference: take its visual language (theme, colors, type, density), never its logo, brand, icons or copy. Derive colors from the references, never from default palettes.
3. Create your board with the Claude "Design" Artifact, titled "<name> · exploration". Design system: the one the brief names for boards, which overrides any default; "none" means the references lead. Put the references on their own "References" artboard with their annotations, so the team sees them; they never appear inside the design artboards.
4. Artboards: the main screen with the wow moment, the restricted role or empty-permission view if the track has roles, the answer to a typical question or action, and the empty and error states. The wow moment is a composition or interaction idea that reads in a still screenshot, not an animation or a nicely made chart: if, with the name removed, it could be any SaaS dashboard, the direction is not there yet. Use only the datasets in the brief's "Data" section and the host's real data, with no unit or currency the data does not declare; a sticky note says which data is synthetic and what is simulated.
5. If impeccable is installed, use it to polish the artboards: it removes AI slop without changing the direction. Boards are not verified in the browser; visual verification happens in build, on the integrated page.
6. One note on the board: the direction in one sentence, references (origin, permitted use, what was taken), what is simulated.
7. Write the board link in explorations/<name>.md (one file each, so nobody edits someone else's line) and commit it. Share the board (Share, edit access) with whoever will compose the final direction. No claude.ai access: build the mock as a page of the host app on a branch explore/<name>, with the same content, and say so.

compose: the final direction

Open the boards listed in explorations/*.md. If the team has said what to take from which board, create the "Final direction" board with the composed direction only: the same artboards as an exploration (main screen, restricted role, answer, empty and error states), each built from the parts the team chose and, where the team said nothing, from the base board, adapted just enough to be coherent, with one note per artboard on where each part comes from. A chosen part applies to every artboard where it appears. Do not add the proposals side by side for reference: one note at the top links the source boards. Read only the artboards you need. If the team has not said, compare the boards on the same scenario (clarity of the primary action, wow moment, integration cost in the host repo, risks for the track's criteria), propose a composition with a recommendation and ask before creating it. A board you cannot open: say so and ask for edit access. Write the link in the brief's "Final direction" line and commit. The choice belongs to the team: never declare it made, never rate people.