TheGoat395/Codex-Skills / skills/website-operating-rules
website-operating-rules
VerifiedCoordinate cross-phase web execution/evidence.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 775 B |
| agents/openai.yaml | config | 252 B |
| references/scoped-web-contract.md | markdown | 6.4 KB |
| references/website-operating-rules-guide.md | markdown | 3.6 KB |
| references/website-quality-tiers.md | markdown | 4.1 KB |
references/website-operating-rules-guide.md
View on GitHub# Website Operating Rules Guide
## Purpose
Make the default website workflow disciplined enough to prevent rushed, generic output.
## Use When
- Web work crossing multiple phases needs one shared scope and evidence contract; a focused specialist task can proceed directly.
- Open-ended prompts such as build a beautiful site, make it modern, make it premium, make it like Squarespace, Raycast, Linear, Vercel, or cinematic references.
- Cases where the user has strong taste expectations but has not yet provided a full brief.
## Do Not Use When
- Backend-only work with no UI surface.
- Tiny copy-only edits where no frontend behavior or design is involved.
- A code review where the user explicitly wants only bugs/security findings.
## Discovery Questions
- What is the site category: business, portfolio, product, luxury/editorial, commerce, dashboard, docs, game, tool?
- What are the existing framework, entry file, styling system, and motion/JS systems?
- What assets exist and which are missing: logo, copy, imagery, video, screenshots, product UI, fonts?
- What deliverable and scope has the user already authorized, and what material information is actually missing?
## Decision Tree
- If code exists, inspect files and commands before proposing implementation.
- If no code exists, choose a conservative modern stack only after naming why it fits the site.
- If the task is open-ended, create a design direction or blueprint before coding.
- If the site can run locally, run it and visually inspect desktop/mobile before final answer.
- If checks cannot run, state exactly why and what was still inspected.
## Implementation Rules
- Treat visual QA as part of the work, not an optional afterthought.
- Never let generic placeholders survive into final delivery unless the user explicitly accepts placeholders.
- Keep edits scoped to the requested site, but do enough polish to make the changed area feel finished.
- Prefer concrete acceptance criteria over subjective assurances like looks good.
- When references conflict, choose a primary reference family and state which traits are being borrowed.
## Useful Patterns
- Discovery -> plan -> build -> run -> inspect -> polish -> verify -> summarize.
- Use a short design contract for open-ended builds: mood, layout grammar, type, color, media, motion, QA.
- Pair high-level taste skills with implementation skills: style director plus Next/Tailwind/Motion/GSAP as needed.
## Anti-Patterns
- Starting by installing dependencies without reading the repo.
- Shipping a page that compiles but was never viewed.
- Saying premium/cinematic/modern without showing how that changed type, layout, assets, and motion.
- Leaving default buttons, unstyled forms, orphan text, or mobile overflow.
## QA Checklist
- Confirm exact commands run: lint, build, tests, dev server, browser checks.
- Check at least one desktop and one mobile viewport when tooling permits.
- Look for horizontal scroll, text overflow, broken images, console errors, and interaction states.
- Mention missing verification if network, dependencies, credentials, or tooling block checks.
## Acceptance Criteria
- The final work is traceable from brief to files to verification.
- The user can understand what changed and how to view it.
- The affected page was inspected; observed defects were fixed when authorized. No gratuitous edit is required when acceptance already holds.
## Scoped execution
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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |