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>
769 B
769 B
Checklist: before you merge a task branch
- Rebased on current
origin/main, conflicts resolved in the worktree npm run verifyandnode scripts/audit-ui.mjsboth green- Assertion count in
verify.mjsdid not fall (grep -c 'throw new Error' scripts/verify.mjs) - Only files in your task's scope changed —
git diff --stat origin/mainmatches the brief - No contended file edited unless you own it (see
rules/git-worktrees.md) - No
.serena/,__pycache__/,dist/, or scratch files staged - Commit message: what, why, and what you deliberately did not do
- Task report written: verified behaviours, known gaps, follow-ups
revieweragent has read the diff- Worktree and branch cleaned up after merge