Codex Full Stack Workflow

Use when Codex works on any front-end implementation, UI polish, dashboard, product screen, internal tool, design system, React component, Tailwind CSS v4 surface, HeroUI React v3 setup, shadcn-to-HeroUI migration, or any task that should use HeroUI. Enforces official HeroUI context, Pencil/Figma component-detail visual approval before coding, HeroUI component selection, and final visual/accessibility verification.

Use whenever the user changes, upgrades, or corrects requirements after initial intake.

Use before completion or release to audit visual metrics, HeroUI component graph, backend/API contracts, code review evidence, and official docs freshness.

Use before claiming a feature, plugin change, UI, API, backend, or full-stack implementation is complete.

Use before moving from requirements to design, design to implementation, implementation to verification, or verification to release.

Use after requirements are approved and before UI implementation when a product feature needs Pencil or Figma visual design evidence.

MUST use before brainstorming, visual companion, Pencil/Figma, or implementation when a user gives a rough product, feature, app, website, landing page, brand site, front-end design draft, or "do not develop yet" goal. Draft the first structured requirement contract and fixed workspace before design or implementation.

MUST use first when Codex works on a product, feature, app, website, landing page, brand site, admin system, backend, database, API, front-end design draft, Pencil/Figma design, full-stack implementation, or any rough goal needing requirements, architecture, design, implementation, verification, or requirement-change handling. When brainstorming also applies, this skill's requirement-discovery and fixed workspace run before brainstorming, visual companion, Pencil/Figma, or code.

Use after requirements, contracts, and visual gates pass to create a TDD-ready implementation plan.

Use when maintaining or releasing a public open-source repository, including issue triage, pull request review, dependency or security remediation, release preparation, and source-linked adoption reporting.

Use when creating, reviewing, or updating the Artifact Registry and artifact PASS conditions for a product development workspace.

Use when the user provides a local TailwindUI or Tailwind Plus folder as visual reference material for a HeroUI React/Tailwind v4 implementation.

Use after requirements are approved to run the one-pass Pencil or Figma workflow that creates visual boards, exports images, records approval, and hands off to implementation gates.