Agency Rules

What it does

Sets the non-negotiable quality floor (design, content, legal, technical and UX) for every page a project produces.

When to use it

Run it at the start of a project to set expectations, and again at final review to check nothing drifted below the floor.

Problems it prevents

Stops a project quietly sliding into shortcuts that show up later as inconsistent quality across pages.

Typical workflow

1. State the quality floor across six areas
2. Apply it at project kickoff
3. Re-apply it at final review
4. Flag anything that fell below it

Example output

A short standards checklist a whole build gets measured against, used the same way on day one and on the last day.

What's included

1. 01
   The complete prompt

   The full manual as a ready-to-save SKILL.md file, matched exactly to what ships in the T7 library.

2. 02
   Install walkthrough

   Personal (~/.claude/skills/) and project (.claude/skills/) folder instructions, whichever fits how you work.

3. 03
   Use notes

   How Claude invokes it, what a good result looks like, and what to check before you trust the output.

Works well with

• SystemProject Planner

  Turns a loose client brief into routes, features, content needs, dependencies, risks and acceptance checks.

• SystemLaunch Readiness

  Classifies and verifies what customers, search engines and operators actually need before a production launch.

• SystemWebsite Final Audit

  Orchestrates the final evidence-based quality gate: anti-vibecode, production security and launch-readiness checks combined.