← ClaudeAtlas

frontend-foundationslisted

Use on any frontend delivery to hold the surface-specific quality floor that `engineering-craft` doesn't cover — intentional visual hierarchy over template defaults, accessible-by-default markup, design tokens instead of hardcoded values, reusable components matching the repo, and compositor-friendly motion. Invoke whenever the change touches UI (a component, screen, page, or style), as the always-on companion to the deeper `frontend-design`, `frontend-component`, `frontend-a11y`, and `frontend-responsive` packs. For "make the UI production-grade", "don't ship a generic template", "is this accessible?".
tmj-90/gaffer · ★ 0 · Web & Frontend · score 69
Install: claude install-skill tmj-90/gaffer
# Frontend foundations — the UI quality floor The frontend companion to `engineering-craft`. Craft holds the *code* bar (structure, errors, tests); this holds the *surface* bar — the things that separate a real product UI from a working-but-generic one. It is a floor and a lens, not the full treatment: for depth, invoke the deep packs it points to. Apply it on any change that touches UI, and confirm it in `self-review`. Composes with `minimalism` the same way craft does: this is never a licence to add chrome or animation the ticket didn't ask for — it's the quality bar for whatever UI you *are* building. ## The floor (hold all of these on UI work) 1. **Hierarchy over template defaults.** The surface should look intentional — clear scale/weight contrast so the eye lands on the right thing first, not uniform cards in a uniform grid. If it looks like an unmodified starter template, it isn't done. Depth → `frontend-design`. 2. **Accessible by default, not as a retrofit.** Semantic elements (`button`, `nav`, `main`, `label`) before `div` soup; every interactive element reachable and operable by keyboard with a visible focus state; images/icons have text alternatives; colour is never the only signal. Depth → `frontend-a11y`. 3. **Tokens, not magic values.** Use the repo's design tokens / theme variables for colour, spacing, type, and radius. Do not hardcode hex codes or `px` font sizes when a token exists — that's the frontend form of the DRY rule. 4. **