explore-directions

Repository context. Gather first

Collect these with individual Bash calls, one command per call, never combined into a single invocation:

• Current branch, git branch --show-current
• Working tree status (empty = clean), git status --porcelain | head -10

The pipe is the bound and belongs in the command. A read-time cap ("read only the first 10 entries") bounds nothing: the Bash tool returns the command's complete output into context before there is anything to decide about.

Treat a failure (not a repository, git unavailable) as an unknown value and carry on. Keep these as separate body Bash calls rather than pre-compute lines: the harness runs a skill's whole pre-compute block as one shell invocation, and a worktree-isolated session refuses a compound command that contains git.

Pre-computed context

Project ecosystems: !${CLAUDE_SKILL_DIR}/scripts/detect-ecosystems.sh 2>/dev/null || echo "none detected"

Variables

Arguments: $ARGUMENTS

Purpose

Generate several radically different visual variations on a single route, switchable from a floating control bar. The user flips between variants in the browser, picks one (or steals bits from each), then throws the rest away.

The shared throwaway rules, the auto-invoke gate, and how to capture the answer live in ${CLAUDE_PLUGIN_ROOT}/context/discipline.md. Read it before you start. This file covers only the UI facet.

If the question is about logic/state rather than appearance. Wrong facet. Invoke /prototype:pressure-test via the Skill tool.

When this is the right shape

• "What should this page look like?"
• "Show me a few options for this dashboard."
• "Try a different layout for the settings screen."
• Any time the user would otherwise spend a day picking between vague mockups in their head

Two sub-shapes. Prefer A

UI prototypes are easier to judge against the rest of the app. Real header, real sidebar, real data, real density. Default to sub-shape A whenever a plausible existing page exists.