authoring-mermaid-diagramsAuthors, repairs and validates Mermaid diagrams: picks the diagram type from what the reader must learn, writes the frontmatter config and accessibility header, and checks the source before it ships. ALWAYS invoke when asked to draw, diagram, chart or visualise something, to document an architecture
batch-task-executionGuidelines for planning and executing batches of tasks from todo lists, backlogs, or multi-item requests. ALWAYS invoke when asked to work through a list of tasks, start multiple sub-agents in parallel, or tackle several items at once. Do not fan out sub-agents or start a multi-item batch without th
complex-researchGuidelines for delegating complex research tasks that need multi-source investigation, synthesis, and comprehensive analysis. ALWAYS invoke when research needs extensive web searches, documentation queries, repository exploration, or cross-referencing multiple sources — delegate to a researcher agen
grill-meA relentless interview to sharpen a plan or design.
grillingGrill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
humanizerRemove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyse
meta-harnessAuthoring guide for the config an agent harness executes or installs: lifecycle hooks (*.hook.json, PreToolUse/PostToolUse/SessionStart matchers), MCP servers (apm.yml dependencies.mcp, stdio/http/sse transports, ${VAR} secrets) and plugin bundles (plugin.json, marketplace, apm pack). ALWAYS load be
meta-steeringAuthoring guide for every steering file an agent harness reads: skills (SKILL.md), subagents (*.agent.md), instructions (*.instructions.md, applyTo/paths) and prompts (*.prompt.md) — frontmatter, description shape, discovery budgets, provenance. ALWAYS load before creating or editing one of those fi
troubleshootingBehavioral rules for diagnosis and root-cause analysis: failures, tool quirks, command hangs, version-dependent behavior, and Docker container debugging (terminal state, script execution, entrypoint overrides, busybox differences). ALWAYS invoke when a command fails, hangs, or behaves unexpectedly,