craft-analyze
Post-cycle analysis — QA, UX, Creative, and Style audits using MCP browser tools.
Live HTML mockup funnel - 3 options, converge by reacting, graduate to tweak/story/todo.
> /plugin marketplace add drobins25/craft > /plugin install craft@craft
How it fires
How this command gets triggered: by you, by Claude, or both.
/craft-mockupContext preview
What this command does when you run it.
Live HTML mockup funnel - 3 options, converge by reacting, graduate to tweak/story/todo.
name: mockup
description: "Live HTML mockup funnel - 3 options, converge by reacting, graduate to tweak/story/todo."
when_to_use: |
Use on an explicit ask to mock something up or see visual options live
('mock up X', 'create a mockup for X', 'show me options for X'). Unsettled
direction is the point - if the look is already decided, route to tweak or
story instead. Not for non-visual uncertainty. On invoke, seed the brief
from the session context.
argument-hint: "[what to mock up]"A persistent alchemist builds 3 genuinely different live HTML options of a visual/interaction idea. You converge by reacting - diverge, refine, polish - new design values solidify to tokens.yaml at acceptance, and the converged mockup graduates on your choice: an immediate tweak, a story, or a parked notebook todo.
This shell owns only routing. The funnel lives in one reference file.
**If args provided:** the args are the subject - what to mock up.
**If no args:** take the subject from the session context (the conversation that led here names it). If nothing in context names a visual subject, ask conversationally - "What are we mocking up?" - no AskUserQuestion; the flow's question budget belongs to the funnel.
One mockup session at a time. Check for an open one:
grep -l "^status: converging" "${CRAFT_PROJECT_ROOT:-.}"/.craft/mockups/*/record.md 2>/dev/nullIf a record with `status: converging` exists, DECLINE the new invocation and point at the open record: name its path and offer to resume it instead. Converged/parked records don't block - only an actively converging one.
Read `${CLAUDE_PLUGIN_ROOT}/commands/references/mockup-inline.md` and execute it inline, from Step 1 (Brief), with the subject and session context in hand.
**Never invoke the funnel via the Skill tool** - a Skill-tool call ends the turn and control never comes back for the next round; inline execution is the contract (see .claude/rules/skill-invocation-chain-breaks.md).
Stop Vibing. Start Crafting. A Claude Code plugin that acts as an intelligent harness for your development workflow: your codebase is read-only by default, every change passes through a Write Gate as planned and approved work, and craft tracks your project's
Repo: drobins25/craft
Post-cycle analysis — QA, UX, Creative, and Style audits using MCP browser tools.
Consult a craft agent. Routes your question to the best mind in the workshop - not a menu, a recommendation.
Agent crystallization command. Studies a tool, role, or person and produces a portable 9-section agent that inhabits the domain - with beliefs, scar tissue,…
Complete a cycle. Triggers reflection if pending learnings, then archives.
Design a cycle — create new cycles with planned stories, detail existing planning cycles, or quick-sketch a roadmap. Detects planning docs in .craft/planning/…