Skip to content

docs: add design guidelines, design-engineer principles, and CLAUDE.md - #473

Open
veksen wants to merge 1 commit into
mainfrom
docs/design-guidelines
Open

docs: add design guidelines, design-engineer principles, and CLAUDE.md#473
veksen wants to merge 1 commit into
mainfrom
docs/design-guidelines

Conversation

@veksen

@veksen veksen commented Jun 22, 2026

Copy link
Copy Markdown
Collaborator

Adds design reference docs to the repo (previously kept only as a local working copy under the gitignored .context/), plus a CLAUDE.md to wire them into agent sessions.

What's here

  • docs/design/web-interface-guidelines.md — a per-PR checklist adapted from Vercel's Web Interface Guidelines, tuned to this Gatsby + styled-components stack (interactivity, motion, a11y, color, content/state, performance).
  • docs/design/design-engineer.md — operating principles from Vercel's Design Engineer page, plus the enforcement ladder (prose → context-injection → lint → CI gates).
  • CLAUDE.md — points agents (and humans) at the two docs and states the two load-bearing rules: don't change visual design without sign-off; ship green, one improvement per commit.

Why

Prose guidelines are the weakest form of enforcement — an agent has to choose to read them. CLAUDE.md makes them load every session, and the mechanical rules are already enforced in .eslintrc.js (a companion change on the website branch) so CI blocks transition: all, bare :focus, and unguarded outline: none.

Notes

  • Docs-only; no code or build impact.
  • The CLAUDE.md is the only opinionated addition — if you'd rather land just the two docs, drop that file and the PR still stands.

🤖 Generated with Claude Code