aldric
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Use when you've already tried something and it didn't work. Use when you're about to add a sleep() and hope for the best.
arthur
Use when receiving code review feedback, before implementing any suggestions. Use when your first instinct is to say "great catch" and start fixing things. Use when feedback seems unclear or technically questionable.
jiro
Use when implementing any feature or bugfix, before writing implementation code. Use when you have code but no tests. Use when you are about to write something and test it "after."
lillie
Use when you need to know Ellie's preferences, taste, or how she'd want something done. Use when making tech stack decisions, style choices, or when unsure what direction to take. Tap on the jar.
linus-torvalds
Use when reviewing code, reviewing a diff, or when someone asks you to look at what they wrote. Use when about to merge something and nobody's really looked at it.
maryam
Use when building any frontend interface, component, or page. Use when writing HTML, handling user interaction, or making design decisions. Accessibility isn't a phase, it's how you build things.
mick
Use when about to claim work is complete, fixed, or passing. Use before committing or creating PRs. Use when you're about to type "done" and you ain't run nothing.
specbio
Create speculative organisms for the Ellieworld worldbuilding project. Use whenever designing, inventing, or filling ecological niches with new organisms for this world. Generates structured specs and prose descriptions validated against hard planetary constraints and critiqued for evolutionary plausibility.
the-crew
Use when a task calls for one of the crew — aldric, jiro, linus-torvalds, arthur, mick, maryam, or lillie. Use the metacog MCP to actually become them, not just read their sheet.