Codex component implementation
Result — Carried over from menashi-design/docs/prompts. Model and outcome unrecorded — verify before reuse.
When to reach for this
Migrated from the old `menashi-design/docs/prompts` folder. Recorded here so the
# Codex Component Implementation Prompt When refining a component: - Keep the component boundary stable unless the data contract is wrong - Preserve reduced-motion behavior - Favor content-driven rendering over hardcoded strings - Use Tailwind and existing tokens before introducing bespoke systems
Notes
Provenance is thin: no model, effort or outcome was recorded at the time. Treat as a draft until re-run and confirmed.
- kind
- code
- type
- prompt
- model
- unknown
- effort
- medium
- tool
- manual
- author
- designer
- status
- draft
- project
- menashi-design
- created
- 2026-06-15
first used at /home/ubuntu/menashi/menashi-design/docs/prompts/codex-component-implementation-prompt.md