agent-kit
Concepts

How the kit improves

From projects to the kit and back — retros, proposals, the weekly scout, releases.

Nothing changes without you: every step is a proposal you approve.

From your project

  • The retro skill gathers evidence (agent-kit usage --days 30, agent-kit context, git log, your corrections) and turns repeated corrections into knowledge, checks, hooks or promoted scripts.
  • An improvement any project would benefit from becomes a proposal to the kit:
Terminal
npx @razcue/agent-kit propose "Warn when a migration has no rollback note" --kind hook --body "problem, proposal, evidence"

agent-kit propose writes into the kit clone's work/proposals/ (when registered with agent-kit setup) or prints a ready gh issue create command.

From the ecosystem

node scripts/evolve/scout.mjs compares a reviewed baseline with new Claude Code versions, new hook events and template dependencies a major behind. A weekly cloud routine (scripts/evolve/ROUTINE.md, created with /schedule) adds web research on skills, harnesses and workflows and writes at most five proposals. It never edits code or releases.

Back to projects

Accepted proposals ship as a release. Projects update the plugin with /plugin marketplace update agent-kit and the project files with agent-kit upgrade.

Session context

What every session starts with, how work resumes, and how the context budget is kept.

New app monorepo

From an empty folder to a Nuxt + Supabase monorepo with the agent layer, auth starter and first change.