/stage
Turn an idea into clickable mock variants on a deployed subdomain. Two sizes: quick (~30 min, 2 variants) and light (~2h, 3 variants plus an Anthropic baseline). Operator picks a direction from phone before committing to build work.
/stageType it bare, or paste it with loose context after — Claude figures out the rest.
A UI idea needs to be seen before it can be judged. Prose and wireframes lose the story.
Turns an idea into clickable mocks on a deployed subdomain. Operator taps through and picks.
Takes in
- A UI intent or design goal
- Optional size — quick or light
Returns
- Deployed mock at a subdomain URL
- Multiple variants to compare
What it does
End-to-end workflow for prototype tiers (quick + light). Takes operator input (text in Phase B; URL / image / repo / transcript / napkin in Phase C) and produces a PR containing deployed prototype variants + clickable comparison gallery (with back-navigation from each variant) + bind-subdomain wiring.
After this skill + dependencies ship + merge, operator can dispatch a paragraph from phone to any consumer repo and /stage quick "<paragraph>" runs the chain end-to-end.
Read the full skill
The complete instructions live at .claude/skills/stage/SKILL.md in your repo after bassclef-sync. Open with your editor for phases, rules, and worked examples.
Where in the SDLC
Why this phase: Clickable mock variants on deployed subdomain — prototype gate.
Related
- Skills catalog — browse all skills grouped by lifecycle phase
- Tier system — what each tier gives you
FAQ
Terms from bassclef vocabulary that appear on this page.
- cameo
- A pattern for routing a specific practitioner's documented judgment into a specific software development task. Bassclef implements it as three parts — a curated catalog of practitioners, a matcher that connects problems to relevant experts, and invokable skills that channel the pick. You see 'Cooper says X' or 'Norman flags Y' inline rather than the skill running a full consult. Trades depth for speed on lower-stakes surfaces. See: /docs/skills/luminary, doi:10.5281/zenodo.22145491
- luminary
- A design or engineering thinker whose discipline bassclef borrows as a review lens — the practitioner in the cameo pattern above. Cooper for personas, Norman for signifiers, Feathers for characterization tests, Beck for TDD rhythm, plus about 90 others. Skills invoke a lens to check work against a specific discipline. `/luminary` browses the catalog. See: /docs/skills/luminary, doi:10.5281/zenodo.22145491
- GRASP
- Craig Larman's General Responsibility Assignment Software Patterns — 9 principles for assigning responsibility to objects (Information Expert, Creator, Controller, Low Coupling, High Cohesion, Polymorphism, Pure Fabrication, Indirection, Protected Variations). `/decompose` uses GRASP to identify interfaces + responsibilities from a spec.
- hook
- A shell script bassclef wires into Claude Code's tool-invocation lifecycle. Hooks fire at events like PreToolUse (before an Edit lands) or SessionStart (when a session opens). Hooks enforce rules mechanically — a rule says 'don't do X'; a hook fires and BLOCKs if X happens.
- rule
- A markdown file auto-loaded into every session's context. Rules pin discipline the agent applies to every response (plain-English writing, blocked-items protocol, temperance gates). Different from a hook — rules are steering; hooks are enforcement.
- skill
- A user-invocable command (like `/kiss` or `/temperance`) that runs a specific bassclef workflow. Every skill lives at `.claude/skills/<name>/SKILL.md` with frontmatter + procedure. Adopters type the slash command; Claude Code loads the skill and runs it.
- adopter
- A repo that has bassclef installed — either via `bassclef init` (lite tier from npm) or via the symlink pattern (standard tier with an Anthropic key). Bassclef's discipline: never break adopters. Every change to a downstream-observable surface ships with a compat shim.
- bassclef-upstream
- The private repo where bassclef substrate is authored. Ships to a public `bassclef` npm package + a public `bassclef-web` docs site. Adopters read the public tier; the operator maintains upstream.
Shipped by @kingofrock · Read the essays
/spec
Turn a canvas or issue into a structured spec. Names the What, the Why, and the acceptance list. Downstream skills read the spec as source-of-truth.
/use-case
Produce Cockburn-style use cases — main success scenario, numbered extensions, preconditions, postconditions, and stakeholders. Closes the gap between /user-stories and /spec. Distinct from /task-scenarios (UX narrative).