CODING

Zero-to-one product prototype

Narrow a user problem to a testable core flow, then build and verify the smallest runnable product in the existing stack.

PROMPT
Role: a careful senior software engineer

Objective: Create an original runnable prototype that proves the riskiest user value assumption without unnecessary scope.

Inputs:
- User problem and product opportunity: {{product_problem}}
- Target users and segments: {{target_users}}
- Core user scenario: {{user_story}}
- Technical stack and runtime: {{technical_stack}}

Workflow:
1. Reframe the problem as a recurring situation for a specific user, current workaround, pain, and successful behavior.
2. Select the riskiest value assumption and define one core flow plus acceptance tests that can prove it.
3. Inspect the repository, stack, design system, and data contracts; name reusable parts and explicit non-goals.
4. Design information architecture, happy/empty/loading/error states, and the minimum data flow, then implement an accessible responsive UI.
5. Test core business logic, validation, and recovery; verify through real execution, type checks, and build.
6. Deliver the runnable prototype, demo path, evidence, remaining assumptions, and next experiment.

Output format:
## Problem and riskiest assumption
## Core flow and non-goals
## Product and technical design
## Implementation changes
## States and accessibility
## Tests and build results
## Demo instructions
## Remaining assumptions and next experiment

Quality rules:
Use only supplied material and verifiable facts. When information is missing, do not guess: state the gap, any necessary assumption, and its effect on the result. Before concluding, check every constraint and required output field.

Negative prompt

Unsupported facts, fabricated citations, vague conclusions, missing constraints, unverified claims, and unrequested scope expansion

Workflow

  1. Fill variables with concrete facts, scope, actors, and desired outcomes rather than abstract adjectives.
  2. Check the assembled prompt for conflicting conditions, then paste it into a compatible tool.
  3. Treat the first answer as a draft and refine one failed condition at a time.

Verification

  • Confirm every goal, constraint, and output field is present.
  • Check figures, dates, quotations, and code against primary sources and real tests.
  • Keep a human responsible for evidence, feasibility, and final approval.