Work: prototype

A prototype is throwaway code that answers a question. This skill is the dispatch wrapper around building one: you stay the conversation partner; a fresh subagent does the typing, so your context stays clear for the reaction loop instead of filling with build attempts.

Before dispatching — the beat that keeps trust

Tell the human, in one or two sentences: the question this artifact will answer, and what they will get to open or run. If the question came from you rather than from them, wait for a nod before building. The first mention of an artifact must never be in the past tense.

The artifact is never the first place a design decision appears. Name the direction you'd take — your recommendation in a line, plus one or two real alternatives when the human might see it differently or has no opinion yet to lean on. Taste calls — UI, interface shapes, data structures, and stack or architecture when they're genuinely open — belong to the human and are made at the offer, before the build. The offer is one message, not a ceremony; a nod is enough.

If the question's vocabulary came from an issue or doc (a "spike", a codename), say what it means in plain words the first time you use it.

Dispatch

One fresh builder subagent per artifact — parallel builders only for deliberately different takes on the same question (three UI variants, two competing state models). The dispatch contains: