Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/full-stack-development
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.
Passed 7 of 18 test cases with the skill, and 2 of 18 without it.
and 8 more in the full report
6 fixed3 passed either way13 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
We want to configure custom lifecycle hooks for our full-stack plugin. Should we add a hooks key directly into .codex-plugin/plugin.json?
| Checked | Without skill | With skill |
|---|---|---|
| rejects adding hooks field to plugin.json manifest | Passed | Passed |
| uses internal lifecycle hook registry and MCP hook runner | Missed | Passed |
The instructions your model reads when the skill loads.
This is the top-level delivery skill for full-stack product work and the general Codex product development plugin. It owns requirement clarification, Artifact Registry, Stage Gate review, backend/frontend contracts, visual approval, implementation gates, change handling, Completion Gate review, and verification.
HeroUI is not the top-level workflow. HeroUI is the front-end layer. Use hero-ui-craft as the required frontend UI sub-skill when a task reaches React Web UI, Pencil/Figma, HeroUI components, or visual verification.
If the user asks for a product, website, landing page, brand site, admin system, app, front-end design draft, Pencil/Figma design, or says "do not develop yet", this skill is the entry workflow.
When brainstorming also applies, do not let it replace this workflow. Treat brainstorming as optional raw material inside requirement discovery only after the fixed workspace has been started. Do not offer a visual companion, browser preview, Pencil/Figma drawing, or implementation before generate_requirement_workspace creates docs/full-stack-development/requirements/<feature-slug>/ and the current stage is recorded in 00-stage.json.
For a one-line request such as "I want a high-end coffee brand website, make the front-end design draft first, do not develop", the first observable actions must be:
generate_requirement_workspace.The user only needs to provide a rough goal, corrections, and confirmations. The agent must draft the missing structure: business requirements, product requirements, information architecture, interaction matrix, state requirements, backend/data/API contracts, frontend/HeroUI contracts, visual requirements, and acceptance criteria.
Do not begin Pencil/Figma or implementation from chat-only requirements.
For every feature, create or update:
docs/full-stack-development/requirements/<feature-slug>/
Then use the local MCP tools to generate/review the gate:
generate_requirement_workspacereview_requirement_workspace_stageplan_requirement_changelist_artifact_contractsreview_artifact_contractreview_stage_gatetest cases passed, vs 2 / 18 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.