sitesmithlisted
Install: claude install-skill byensitmagnus/sitesmith
# sitesmith
A website is not done when the code compiles. It is done when it has been rendered, looked at,
measured, and corrected. This skill enforces that loop.
Nothing here fires automatically. Read the brief, then pull only what fits. A rule applied in the
wrong context is its own kind of slop.
---
## 1. Route before you build
First action, always. Pick one row. It decides which reference you open and which rules govern.
| The situation | Mode | Open first |
| --- | --- | --- |
| Empty directory, no frontend stack | **SETUP** → then NEW | [10-setup.md](references/10-setup.md) — optional, gated |
| "Build a landing page / site / portfolio" | **NEW** | Step 2 below |
| Existing code, "redesign / improve / make it better" | **REDESIGN** | [06-redesign-audit.md](references/06-redesign-audit.md) — audit before touching anything |
| "Build a pricing table / modal / nav" | **COMPONENT** | [blocks/](blocks/README.md) — working implementations |
| "Review this UI / is it accessible?" | **AUDIT** | [07-ux-rules.md](references/07-ux-rules.md) + [05-ai-tells.md](references/05-ai-tells.md) |
| Dashboard, data table, admin, multi-step product UI | **PRODUCT UI** | [07-ux-rules.md](references/07-ux-rules.md) is primary; dials are secondary |
Marketing pages and portfolios are governed by the dials. Product UI is governed by the UX rules.
Do not mix the two governance models — that is how a dashboard ends up with a cinematic hero and a
landing page ends up looking like a settings