▒ v-1 to Codex
Implement v-1.design prompts with Codex.
Use Codex with v-1.design prompts to turn a finished design handoff into production repo changes.
▒ best fit
Developers who want an agent to inspect the codebase, make scoped UI edits, run checks, and explain what changed.
▒ workflow
How to hand off a v-1 design to Codex
- 01Share the v-1 design prompt, live demo, and exact screen list with Codex.
- 02Ask Codex to inspect the existing app structure and choose the smallest safe implementation path.
- 03Add or map design tokens before changing individual screens.
- 04Implement screens route by route, keeping local conventions intact.
- 05Run typecheck, lint, tests, and browser screenshots where visual fidelity matters.
▒ prompt tip
Codex should treat the v-1 prompt as a spec, not inspiration. Ask for explicit verification against the visible demo.
▒ v-1 handoff includes
- Build prompt
- Design tokens
- Screen-level instructions
- Asset references
- Verification checklist
▒ questions
- Can Codex pull a v-1 design into my app?
- Yes. Codex can use the v-1 prompt and design system as implementation input for an existing codebase.
- Does v-1 replace code review?
- No. v-1 supplies the design handoff. You should still review the implementation, run checks, and test the real app.