#646 - Adopt Matt Pocock agent skills and restructure Claude Code config

[bracyw]

Changes

Adopts Matt Pocock's agent-skill framework as Argos's AI-driven path for issue authoring and engineering work, and restructures the repo's Claude Code config around it. Lands in three groups: docs (agent conventions under docs/agents/, ADRs 0001 and 0002, and a root CONTEXT.md domain glossary), skills (19 skill dirs under .claude/skills/ — Matt's engineering and issue-authoring set plus Argos's own workflow skills), and code rules (per-subdirectory CLAUDE.md for angular-client and scylla-server, plus the first project-level root CLAUDE.md).

Issue authoring is two-path: AI files via Matt's body shapes through the gh CLI, humans keep the YAML form templates, and the ready-for-agent label marks AI-filed issues. The rejected single-path alternative and its rationale live in docs/adr/0002. Five triage labels (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) are created on the repo; spike and other issue templates are removed, leaving task, bug-form, feature-request, epic.

Notes

• First committed CLAUDE.md in the repo: project-focused (overview, local dev, testing, conventions, safety) with pointers to the subdir files.
• The two subdir CLAUDE.md files port the former .claude/rules frontend and backend guidelines, minus the Cursor-style glob frontmatter that Claude Code ignores.
• Caveman terse mode ships as an opt-in repo-wide pilot — default-on, toggle off per session.
• Setup conventions live in docs (issue-tracker.md, triage-labels.md) rather than a setup skill; the labels are seeded once via gh label create.
• Follow-ups out of scope: revisiting individual skills (tdd, verify-graph, prototype, diagnose) after real-world usage, tracked separately.

Test Cases

• Verified skill and docs cross-references resolve, with no dangling skill invocations.
• Confirmed the five triage labels exist on the repo with the intended colors and descriptions.
• Confirmed no merge conflicts against develop.
• Spot-checked the migrated skill files and the pruned issue templates (four survivors).

Checklist

• All commits are tagged with the ticket number
• No linting errors / newline at end of file warnings
• All code follows repository-configured prettier formatting
• No merge conflicts
• All checks passing
• Remove any non-applicable sections of this template
• Assign the PR to yourself
• No package-lock.json changes (unless dependencies have changed)
• Request reviewers & ping on Slack
• PR is linked to the ticket (fill in the closes line below)

Closes #646

[TheJeffreyKuo]

lgtm!