13 posts tagged with "Skills"

The Aider drone brief (AIDER.md) and its skills index are sized for a mid-class model. A ≤8B local model — Qwen3 4B in particular, Anchor's default swarm-local pick — doesn't have the context budget to reason about either one reliably: a live canary from a 2026-09-08 session shows a plain hello sending a 4B model into a 600-second confusion loop, treating Aider's own edit-format rules as the task. anchor --platform aider now also scaffolds a thinner, script-first card built for exactly that class of model — and along the way, live testing turned up a real bug in how the whole Aider platform is invoked.

Yesterday's Aider platform scaffold shipped AIDER.md — a brief that teaches a drone session to run /work and nothing else. It didn't say much about why nothing else: an operator typing /draft or /review at a drone just got a one-line redirect buried in prose. anchor --platform aider now also writes a small skills-index.md that makes that roster explicit.

Anchor's scaffold has covered Claude Code and Grok Build for a while — both harnesses with a real slash-command runtime, so a scaffolded project gets the full skill suite (/work, /draft, /review, and the rest). Aider is different: it's usually the harness running a small local model, and it has no slash-command runtime to hook into. anchor --platform aider now scaffolds it anyway, with a brief scoped to what that actually calls for.

Anchor's hard rule used to read: run /commit-prep before any commit. /review had been ignoring it for months.

/local-models used to exist only after you scaffolded a project. It now lives in the Anchor checkout the same way /work does — so you can ask "what can this box run?" before a project exists — and is still copied into Claude and Grok projects. The probe is still this host only.

/push publishes the current branch and nothing else. /release is the moment pending branches get reviewed and a version goes out. Neither one does the other's job.

Until now, only a /review survey could land a branch on dev. That rule is amended: a /work session may merge its own finished work onto integration — when the operator answers its end-of-run question in-session, and the branch passes a mechanical scoped-merge gate.

/tag answers one question — what's the next version, and can I mark it — without doing anything a release actually requires. It never pushes, and it is deliberately not a release.

Every project accumulates the same small gaps: no robots.txt, no llms.txt, a single stray favicon.ico instead of a real icon set, no dependency-update bot. /optimize scans for the standards that actually apply to this project's type, and turns the gaps into .plans you pick from — not a wall of text you have to triage by hand.

Every project already has a way to go live — a workflow file, a vercel.json, a deploy.php, or just a production remote someone pushes to. /deploy finds that path and runs it. It only proposes tooling when a project genuinely has none.