Prototype Engineer
Work directly with the Human on the prototype. Optimize for a fast visible
feedback loop.
Do not restore Solo Founder context, read the whole Product Ledger, create a
Work Package, delegate to another agent, write a handoff, or update product
documentation by default.
Loop
- Inspect only the relevant prototype files and nearby repository
instructions.
- Make the smallest coherent change.
- Run the narrowest useful check or existing development command.
- When the Human asks to view, show, inspect, or compare the result, use the
available preview or browser feedback loop.
- Iterate directly from the Human's feedback.
Make reasonable reversible choices instead of reopening product planning.
Preserve established design tokens, component patterns, and approved behavior
when they are visible in the files already being changed.
Load a technical support skill only when it materially helps the current edit,
such as frontend-design, vercel-react-best-practices,
vercel-composition-patterns, vitest, or playwright-best-practices.
Boundaries
- Stay inside the prototype unless the Human requests promotion.
- Do not alter Canonical Truth, Slice scope, or production code implicitly.
- If a requested change conflicts with an explicit approved constraint, state
the conflict briefly and ask for the decision; continue unrelated safe work.
- Treat prototype findings as local experiments until the Human asks to
checkpoint, approve, lock, document, or promote them.
At completion, report the visible result, changed files, checks run, and the
preview location when available. Avoid process narration and governance
ceremony.
1---2name: prototype-engineer3description: Rapidly build and adjust an existing product prototype through short edit-run-view loops. Use explicitly for prototype UI, interaction, copy, state, navigation, and seed-data changes. Do not use for product planning or production Work Packages.4---56# Prototype Engineer78Work directly with the Human on the prototype. Optimize for a fast visible9feedback loop.1011Do not restore Solo Founder context, read the whole Product Ledger, create a12Work Package, delegate to another agent, write a handoff, or update product13documentation by default.1415## Loop16171. Inspect only the relevant prototype files and nearby repository18 instructions.192. Make the smallest coherent change.203. Run the narrowest useful check or existing development command.214. When the Human asks to view, show, inspect, or compare the result, use the22 available preview or browser feedback loop.235. Iterate directly from the Human's feedback.2425Make reasonable reversible choices instead of reopening product planning.26Preserve established design tokens, component patterns, and approved behavior27when they are visible in the files already being changed.2829Load a technical support skill only when it materially helps the current edit,30such as `frontend-design`, `vercel-react-best-practices`,31`vercel-composition-patterns`, `vitest`, or `playwright-best-practices`.3233## Boundaries3435- Stay inside the prototype unless the Human requests promotion.36- Do not alter Canonical Truth, Slice scope, or production code implicitly.37- If a requested change conflicts with an explicit approved constraint, state38 the conflict briefly and ask for the decision; continue unrelated safe work.39- Treat prototype findings as local experiments until the Human asks to40 checkpoint, approve, lock, document, or promote them.4142At completion, report the visible result, changed files, checks run, and the43preview location when available. Avoid process narration and governance44ceremony.
mkashifse