website-operating-rules git:20260621.2caaeccA

Immutable. This exact content is served forever at /api/v1/blob/f561eda93c603c13.

---
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."
---

# 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

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.

## Detailed Guide

Read `references/website-operating-rules-guide.md` when this skill is active for a build, redesign, review, or implementation plan.