chore: consolidate the skill packages under .agents/

The repository had two skill directories. `skills/` held the four written
for this project; `.agents/skills/` held the ones the agent context refers
to. Nothing said which an agent should read, and `.agents/ORCHESTRATOR.md`
only ever pointed at the second.

Move the first four into `.agents/skills/` so there is one location, and
add the vendored packages this chapter work used: `animation-vocabulary`
and `improve-animations` (emilkowalski/skills), `teach` (mattpocock/skills),
plus a local `translation` skill and `audit-translations.mjs` for the EN/PT
pairs.

`skills-lock.json` pins the vendored three by source and content hash, so a
later re-vendor is a diff rather than a guess. `.claude/skills/` is
symlinks into `.agents/skills/`, which is what makes them loadable here
without a second copy on disk.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

.agents/skills/improve-animations/PLAN-TEMPLATE.md

@@ -0,0 +1,80 @@
+# Plan Template
+
+Every plan written by `improve-animations` follows this structure. The executor
+may be a less capable model with zero context and zero taste — the plan must
+contain everything, exactly. No references to "the audit above" or "the easing
+we discussed."
+
+````markdown
+# NNN — <Short imperative title>
+
+- **Status**: TODO
+- **Commit**: <output of `git rev-parse --short HEAD` when this plan was
+  written>
+- **Severity**: HIGH | MEDIUM | LOW
+- **Category**: <audit category>
+- **Estimated scope**: <n files, rough size>
+
+## Problem
+
+What is wrong, where, and why it matters to how the product feels. Cite every
+location as `path/to/file.tsx:123` and include the current code verbatim:
+
+​`css /* src/components/dropdown.css:14 — current */ .dropdown { transition: all 400ms ease-in; } ​`
+
+## Target
+
+The exact end state. Every value spelled out — curves, durations, spring
+configs, media queries. Never "use a nicer easing":
+
+​`css /* target */ .dropdown {   transition: transform 200ms var(--ease-out), opacity 200ms var(--ease-out);   transform-origin: var(--transform-origin); } ​`
+
+## Repo conventions to follow
+
+How this codebase already does it, with one exemplar the executor should imitate
+(token names, file placement, prop patterns):
+
+- Easing tokens live in `src/styles/tokens.css`; add new curves there, e.g.
+  `--ease-out: cubic-bezier(0.23, 1, 0.32, 1);`
+- <exemplar file:line that already does this correctly>
+
+## Steps
+
+1. <One concrete edit per step: file, what changes, resulting code.>
+2. …
+
+## Boundaries
+
+- Do NOT touch <files/components out of scope>.
+- Do NOT change markup/structure — motion properties only (unless a step says
+  otherwise).
+- Do NOT add new dependencies.
+- If a step doesn't match the code you find (drift since the commit stamp), STOP
+  and report instead of improvising.
+
+## Verification
+
+- **Mechanical**: <exact commands — typecheck, lint, build — with expected
+  outcome>.
+- **Feel check**: run the UI, trigger <interaction>, and confirm:
+  - <observable check, e.g. "the dropdown scales from its trigger, not from
+    center">
+  - <e.g. "spamming the toggle never restarts the animation from zero">
+  - In DevTools, set playback to 10% (Animations panel) and confirm <detail>.
+  - Toggle `prefers-reduced-motion` (Rendering panel) and confirm movement is
+    dropped but opacity feedback remains.
+- **Done when**: <machine- or eye-checkable completion criteria>.
+````
+
+## Notes for the plan author
+
+- One plan per finding. If two findings share every file and the same fix
+  pattern (e.g. the same easing token swap across components), they may merge
+  into one plan.
+- Pull every value from [AUDIT.md](AUDIT.md) — never approximate from memory.
+- The feel check is not optional. Motion can be mechanically correct and still
+  feel wrong; give the executor (or the human reviewing the executor's diff)
+  concrete things to watch for in slow motion.
+- After writing plans, create or update `plans/README.md` with: a table of plans
+  (number, title, severity, status), the recommended execution order, and any
+  dependencies between plans.