website-blueprint-first ยท diff
git:20260621.2caaecc to git:20260905.f7824ba
7 added, 7 removed. Audit A to A.
---
name: "website-blueprint-first"
- description: "Create a website blueprint before coding. Use for new sites, redesigns, image-to-site work, premium landing pages, portfolios, brand sites, product sites, and any frontend project where Codex should define pages, sections, assets, tokens, layout, motion, and QA criteria before implementation."
+ description: "Specify missing pages, sections and assets."
---
# Website Blueprint First
## Purpose
Lock the plan before coding so the build does not drift into generic filler.
## Required Use
Use this skill when the trigger description applies. Keep the `SKILL.md` lean, then read `references/website-blueprint-first-guide.md` for concrete rules before planning or editing a meaningful website change.
- ## Operating Contract
+ ## Scoped execution
- 1. Inspect before coding when code exists.
- 2. Convert vague taste into concrete rules.
- 3. Explain planned files before major changes unless the user clearly said to proceed.
- 4. Build, inspect, polish, and verify.
- 5. Report commands run, files changed, and anything not tested.
+ Apply the [shared web contract](../website-operating-rules/references/scoped-web-contract.md) once when execution crosses phases; reuse it if already read. Load only the specialist guidance relevant to the requested surface and deliverable.
## Detailed Guide
Read `references/website-blueprint-first-guide.md` when this skill is active for a build, redesign, review, or implementation plan.
+
+ ## Scope and evidence
+
+ Make the shared direction spec buildable; reuse an adequate approved spec. Planning-only output stops at the blueprint. Authorized implementation proceeds immediately after resolving actual missing requirements, without a second approval cycle.