Skip to content

TheGoat395/Codex-Skills / skills/website-operating-rules

website-operating-rules

Verified

Coordinate cross-phase web execution/evidence.

references/scoped-web-contract.md

View on GitHub
# Scoped web execution contract

Apply once to the actual task; reuse unchanged context, the agreed spec and existing relevant evidence. A selected specialist supplies craft procedure, not a new authorization or a larger deliverable.

## Scope, source and ownership

- Distinguish analysis, copy/prompt/spec output, implementation, selected-surface QA and full release. Analysis stays read-only; prompt/spec work does not automatically generate media, code, reports or deployment.
- Existing user authorization covers routine reversible work. State material assumptions and proceed when adequate context exists; ask only for a consequential unresolved choice, genuine missing access or an actual external commitment boundary. No required verb, designer-weight approval or second plan confirmation.
- Inspect the relevant source before editing: current project guidance, affected component/routes, stack and scripts, source content and assets. Inspect forms, CMS, analytics, environment configuration, deployment and ownership only when affected. Never expose secrets.
- Resolve fidelity mode: exact supplied/owned source, authorized faithful reference, original reconstruction, or style overlay. Preserve exact source details in fidelity work; require an originality delta for original work. Never invent source access, hidden code, authorship, rights, product proof, metrics or customer relationships.
- One shared design spec owns requested tier, audience/offer, page map, section intent, visual lane, typography/color/materials, assets, motion, responsive behavior and acceptance criteria. Use existing decisions; for a tiny change a local note is enough. `web-design-direction-system` owns direction; blueprint makes that same spec buildable; style director refines it; build gate checks applicable gaps. Use the bundled [quality tiers](website-quality-tiers.md) for an unresolved delivery-depth decision; `route-sellable-web-tier` is an optional separately installed specialist; the requested tier is a capability floor, not a command to rebuild an existing enterprise site for one label change.

## Craft and implementation

- Preserve project conventions and working behavior. Explain material dependencies and prefer existing project-local tools; no install is implied by reading a skill. Resolve actual commands/binaries and use a documented fallback if unavailable.
- Keep premium ambition, authored composition, content-specific copy, real proof, deliberate type/color/material, useful visual media and meaningful motion. Aesthetic numbers and catalog recommendations are tested starting points, subordinate to the brief and approved brand. Intentional repeated grids, static states and text-first work can be correct; do not add variation or media merely to satisfy a template.
- Keep semantic HTML, meaningful heading/link/button text, labeled controls, accessible names, logical DOM/tab order, visible focus, readable contrast and mobile hierarchy. Keep critical text in HTML; use informative alt text, empty decorative alt and captions/transcripts where relevant.
- Motion may serve feedback, continuity, narrative, artistic expression or delight. Preserve interruption, trigger origins, lifecycle cleanup and performance; provide equivalent reduced-motion states and relevant no-JS/no-WebGL/no-autoplay fallbacks. Content must remain available if animation fails.
- Reserve media dimensions, preserve reversible masters and source provenance, use responsive crops and loading/failure states. Label prototype/fictional UI as such; only real verified UI supports factual product proof. Actual image creation/editing follows the available image-tool contract; deterministic optimization uses permitted encoders.
- For affected forms, booking, checkout, CMS and analytics, account for loading, empty, error, success, retry and rollback behavior. Visual polish does not certify integrations. Use an authorized test environment; real sends, charges or external commitments need the actual scope authorization.

## Evidence and completion

- `browser-inspection-workflow` coordinates one affected route/viewport/state matrix. Reuse evidence until relevant code/state changes invalidate it. Specialists inspect their dimensions; do not repeat a whole-site loop in each skill.
- Render and inspect actual changed visual behavior at relevant desktop/mobile sizes. Inspect screenshots, real interactions, console/network and responsive composition; validate motion with reduced-motion state. Source-only review remains useful but cannot certify rendered quality. Width emulation and Playwright WebKit do not certify real mobile hardware or Safari.
- Run decisive applicable lint/build/test/runtime checks, fix material defects and recheck affected coverage. Add another polish pass when inspection finds a defect or an unresolved quality risk; never make a gratuitous edit to meet a pass count. Scope missing/untested evidence precisely.
- Captures, JSON validators and templates establish only their stated structural or file checks. Separate capture success, inspected quality, runtime testing, production-equivalent readiness and live production certification. N/A requires a scope rationale and is not a pass; untested/fail must remain visible.
- Use `frontend-quality-auditor` for an overall assessment only when requested/needed. A separately installed `qualify-enterprise-site-delivery` can aggregate adopted release gates; otherwise use actual project release requirements; `final-client-handoff` owns full client release evidence. Small fixes close with changed files, checks and limits, without a release manifest, deployment or new support infrastructure.

## Engineering controls when applicable

Honor the current framework, package manager, primitives and motion stack. CSS fits simple states; Motion fits React state/layout/gestures; GSAP fits earned timelines/scroll/SVG/text work. Native, authorship and graphics routes remain available without forcing a full stack. React render stays pure; derive render data during render and use effects to synchronize external systems with cleanup. Next App Router uses server components by default and narrow client islands; preserve imported client graph and secret boundaries. Preserve hover/touch parity, listener/observer/timeline cleanup, batch reads/writes and avoid scroll traps.

If this reference is unavailable in a relocated installation, use the entrypoint's scoped procedure and project rules; a missing sibling must not block authorized useful work.
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
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: 194kUpdated Claude CodeCodexVerifiedInstall