open-design-explore

name: "open-design-explore"description: Explore 2–4 deliberately different design directions for one brief, compare them side by side, then build out the one you pick — use whenever the user explicitly asks for several options, directions, alternatives or versions of a design to compare ("show me three directions for…", "a few different takes on…"), even if they don't mention Open Design; not for a single, ordinary design requestargument-hint: what to design, and optionally how many directions or what should vary (e.g. "pricing page, 3 directions")

Explore several deliberately different design directions with Open Design, compare them side by side, and take the chosen one forward.

Brief: "$ARGUMENTS" — or, if that is empty, the user's request in this conversation (if it isn't clear, ask the user: "What should we explore directions for?")

How to talk to the user. Many people using Open Design don't write code, so:

• Use the user's own words. If they say "artifact", "design tokens" or give a file path, use those terms back; otherwise use the plain words below.
• Keep the machinery out of replies: no tool names, no ids like od:prototype:poster-hero, no internal files (.artifact.json, .comments.json, config.json), and not the words "register", "manifest", "sidecar", "entry" or "surface", unless the user used them first.
• Explain a print term the first time it comes up, in one short clause, and not again.
• Say where a file is the way the user would find it ("in your Open Design folder, under seed-swap-flyer"). Give a raw path only where the user can click it (Claude Code, Claude Desktop's Code tab, VS Code) or asks for it.
• End each reply that finishes a step with one line on what they can do next, with at most two options ("Want it in Instagram sizes too, or is it ready to print?").

1. Plan the directions

If the brief is empty, ask the user what to design before doing anything else.

Call list_open_design_skills to find the skill that fits what's being designed (a landing page, a deck, a dashboard…). Then call prepare_open_design_exploration with that skillId and the brief:

• count: the number of directions the user asked for (2–4). Default 3.
• If the user named what should vary ("three hero concepts", "different pricing layouts"), pass axis: "custom" and customDirections, one { label, brief } per direction.
• Otherwise leave axis out. The tool picks visual styles when no design system is active, and layout or narrative structures when one is, so the brand is kept.
• Pass directionIds only when the brief's tone clearly calls for specific directions, e.g. editorial-monocle for a magazine or brutalist-experimental for an art or agency site.

If the result says the active design system was set aside, tell the user.

2. Generate each direction

For each direction in the result, follow sharedInstructions followed by that direction's own instructions. Write its file at exactly its suggestedEntryPath, then call register_open_design_artifact with the explorationId, the direction's directionId, kind, title and sourceSkillId.

These are sketches: one screen, or a cover plus two slides for a deck. Divergence matters more than polish. If you can delegate to sub-agents, generate the directions in parallel and give each one sharedInstructions plus its own instructions.

3. Compare

Call compare_open_design_exploration with contactSheet: true. If you can view images, open the contact sheet and check that the directions look clearly different (layout and hero pattern, not just colour). Regenerate any direction that resembles another, then compare again.

4. Present

Give the user the comparison page path (it opens in any browser straight from the file system and shows every direction side by side), and the contact sheet path if one was made. In one line each, say how the directions differ. Ask which one to take forward, and whether to:

• build it out at full fidelity,
• merge in parts of another direction ("B, with A's hero"), or
• save it as a design system for later work.

In Claude Desktop Chat, call show_open_design_artifact with the explorationId to show the directions side by side, and where show_open_design_questions is in your tool list, ask the choice through it instead of a chat message: a direction question with one option per direction (imageRef: "artifact:<its entryPath>"), a next question (Build it out, Merge in parts of another, Save as a design system) and a short text question for anything to change or take from another direction. Read the <!-- od-answers {...} --> line of the reply (you-pick means choose for them), then go on to step 5. If the user types their answer or taps "Take this one" instead, use that.

5. Take the choice forward

Call choose_open_design_direction with the explorationId, the chosen directionId, next (build-out, merge with mergeFrom, or save-design-system) and the user's own adjustments as notes. Follow the returned instructions and register the result as they say.

Artifact preview. If you have an Artifact tool, publish the result as its private artifact preview (the built-out design, not the sketches) once it's registered: call publish_open_design_artifact with provider: "claude-artifact" and follow what it returns. Publish again after each round of feedback you apply; it goes to the same artifact. Give the link once, then just say the preview was updated.