website-operating-rules ยท diff
git:20260621.2caaecc to git:20260905.f7824ba
3 added, 7 removed. Audit A to A.
---
name: "website-operating-rules"
- description: "Apply strict website-building operating rules for any frontend, website, landing page, portfolio, product site, luxury site, Squarespace-like site, modern SaaS/devtool site, or UI build. Use when Codex must inspect first, avoid generic design, explain planned files, run local verification, perform a second visual polish pass, and report tests honestly."
+ description: "Coordinate cross-phase web execution/evidence."
---
# Website Operating Rules
## Purpose
Make the default website workflow disciplined enough to prevent rushed, generic output.
## Required Use
Use this skill when the trigger description applies. Keep the `SKILL.md` lean, then read `references/website-operating-rules-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-operating-rules-guide.md` when this skill is active for a build, redesign, review, or implementation plan.