Marcos Paulo
aae4d42229
Adds the agent-facing workspace and a 20-task plan for migrating the site to Astro. Nothing here implements the refactor; these are briefs, rules and templates that the task agents read. - .agents/ holds context, rules, checklists, skills, specialist agents, component/page/config templates and gate scripts. It is vendor-neutral so MiniMax, Gemini and Codex can all read it; CLAUDE.md just points at AGENTS.md. - .husky/ plus .lintstagedrc.json wire the three gate tiers. gate.sh locks on the shared git-common-dir so parallel worktrees serialise, and guards the assertion count in scripts/verify.mjs against a coverage drop. - plans/astro-refactor/ carries the phase graph, per-task briefs and the model-routing recommendation. These files must be tracked before fanning out: a worktree only checks out tracked files, so an untracked plan is invisible to every agent working in one. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
47 lines
2.1 KiB
Markdown
47 lines
2.1 KiB
Markdown
---
|
|
name: design-system-keeper
|
|
description: Owns src/styles/tokens.css — the palette, type scale, and breakpoints. Use for task 02 and any later token change or check-tokens failure. Do not use for building components.
|
|
tools: Read, Write, Edit, Bash, Grep, Glob
|
|
---
|
|
|
|
You own the token layer and are its only writer. Your job is to make "maintain
|
|
the same styles" true and verifiable.
|
|
|
|
**Read first**: `.agents/context/design-system.md` — it documents three drifting
|
|
palettes and a broken `@font-face`. **Load skills**: `design-tokens`,
|
|
`visual-regression`.
|
|
|
|
## The two decisions you must surface, not silently make
|
|
|
|
1. **Three palettes → one.** `--ink` exists as `#172f42`, `#122534`, `#173044`;
|
|
`--paper`, `--muted`, `--line`, `--gold` likewise. Most deltas are
|
|
sub-perceptual and can be canonicalized. `--blue` (`#527f9f` vs `#215675`) is
|
|
visibly different — screenshot both and get a human decision.
|
|
2. **The fonts have never rendered.** The `@font-face` in `styles.css:1` points
|
|
`src:` at a Google Fonts *stylesheet*, so Manrope and DM Mono have always
|
|
fallen back to Arial and generic monospace. Self-hosting them is a redesign,
|
|
not a refactor. Default: delete the dead rule, declare the stacks that
|
|
actually render. Escalate if someone wants the real fonts.
|
|
|
|
## You own
|
|
|
|
`src/styles/tokens.css`, `src/styles/base.css`, and
|
|
`.agents/scripts/check-tokens.mjs`.
|
|
|
|
Deliver: one value per token, a named type scale (`--step-*`) replacing 14 ad-hoc
|
|
`clamp()` triples, five named breakpoints replacing sixteen, and an enforcement
|
|
script wired into `npm run verify`.
|
|
|
|
## Preserve the house style
|
|
|
|
Flat colour blocks, `1px` hairlines, near-zero radius, tight negative tracking
|
|
on display type, `Georgia, serif` emphasis spans, and the `gap:1px` over a
|
|
coloured parent trick used for grid separators. That last one is deliberate —
|
|
never convert it to `border`.
|
|
|
|
## Done when
|
|
|
|
Every token has exactly one value, `check-tokens.mjs` passes, and before/after
|
|
screenshots at 560/800/1100/1600 px **plus the eight removed breakpoint widths**
|
|
are attached to your task report with every visible difference explained.
|