Port the prototype

Port the prototype into code

A method by Alexis Boyer · version 4.0 · September 22, 2026

Gate 4. Hand the prototype and the starter to the coding agent, and keep it inside your organization's conventions. It is quoted here exactly as it appears in the core guide.

The text to copy

You are at Gate 4 of the method: porting the prototype into code.
You are implementing [PRODUCT / SLICE].

Read before coding:
- the prototype from Gate 3, in the form it was handed to you
- the PRD, whose first section is the strategic framing
- the approved frontend starter repository and its conventions
- the backend conventions
- the project memory and journal

Product boundary:
[WHO THE PRODUCT IS FOR, WHO IT IS NOT FOR, AND WHAT MUST NOT BE BUILT HERE]

Rules:
- the prototype is the visual and product reference;
- the starter repository and its conventions decide how the code is written;
- do not paste the design tool's export into the application foundation;
- keep routes thin;
- put domain logic in feature folders;
- use the organization's shared primitives before creating anything new;
- route mock data through API-shaped services that match the future backend contracts;
- centralize copy and localization;
- enforce role and privacy rules at the read-model level;
- do not redesign anything unless you are explicitly asked to;
- before each change to the code, re-read the starter's rules and the backend conventions.

Current task:
[THE FLOW, SCREEN OR FIX]

Acceptance criteria:
- the flow works end to end in the front-end mock;
- the result matches the design where the design is non-negotiable;
- no privacy regression;
- relevant tests added or updated;
- project memory and journal updated if this changed product behavior, architecture, a stakeholder decision or future reasoning.

Run before finishing:
- typecheck
- lint
- tests
- build
- click through the flow in a browser

Report:
- which gate you are at, what you have, what is missing, and what I must
  decide before you cross
- what changed
- what you actually ran and what it returned
- memory and journal updates made, or explicitly skipped with the reason
- remaining open product or backend decisions