Before Claude starts work, this drops a thin boundary frame: what you're asking for, what success looks like, where to stop, and what's out of scope. You trigger it with /aegis-goal or "Aegis goal:" when you want that explicit contract up front. It's not for tiny edits or quick questions. It's for the moment you realize you need a stop condition before Claude rewrites your entire auth system to fix one refresh bug. The frame is compact, routes you to the right workflow (TDD, debugging, planning), then execution continues in the same turn unless you asked to pause. It's opt-in guardrails, not ceremony.
npx -y skills add ganyuanran/aegis --skill goal-framing --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
juliusbrussee/caveman
mattpocock/skills
shadcn/improve
obra/superpowers
forrestchang/andrej-karpathy-skills
vercel-labs/skills