vibe-prototype
Installation
SKILL.md
Vibe Prototype
Use a disposable artifact to answer one uncertainty with observed evidence, then feed the decision back into the active workflow artifact.
Rules
- Treat the runnable, rendered, or executable artifact and its observed evidence as the primary work. Keep it isolated from production code unless the user explicitly asks to prototype there.
- For UI prototypes, use the smallest sufficient design: retain only what the core task, comprehension, trust, essential feedback, accessibility, and recovery require; give each fact, action, and state one authoritative source; and assess possible removals counterfactually by default. Modify and rerun the artifact only when the effect cannot be judged reliably from current evidence and could change the prototype conclusion.
- Stop and ask before destructive changes, production credentials, private data, paid services, deployment, or irreversible external actions.