
Use when turning a textbook, PDF, blog post, article, paper, course, notes, transcript, or other source material into suggested agent skills or skill improvements. Triggers on "what skills could come from this", "extract skills from", "turn this into skills", "skill ideas from this source".
Use when creating a polished self-contained HTML page would help the user understand, compare, review, present, tune, or interact with information better than Markdown. Triggers on "make an HTML page", "HTML artifact", "nice HTML", "visual report", "interactive explainer", "one-page dashboard", "shareable page".
Use when planning or synthesizing user tests for prototypes, mockups, clickable demos, product concepts, design flows, landing pages, or early product specs. Triggers on "test this prototype", "prototype testing", "user test plan", "validate this product idea", "test with users".
Commit, push, open, and land a pull request through CI handoff. Use when work is complete and the user wants an agent to create or update a PR, open it as a draft, monitor GitHub checks with `gh pr checks`, fix failed checks, retry up to three remediation pushes, mark the PR ready for review once green, and move a linked Linear ticket to Human Review when one exists. Trigger on requests like 'land this PR', 'open and monitor a PR', 'commit push and watch CI', 'get this ready for review', or 'finish the PR workflow'.
Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for large prs, new features/architectures, a deep code quality audit, or especially harsh maintainability review.
Use when reviewing a PR, reviewing the current branch, or posting code review feedback to GitHub. Triggers on "review this PR", "code review", "check this pull request", "review my branch", "review and fix".
Use when addressing PR review comments or resolving unresolved PR review threads from Copilot, Code Factory, bots, or humans. Triggers on "fix review comments", "address review feedback", "address code factory", "respond to PR comments", "resolve conversations", "unresolved review threads".
Use when generating a changelog from recent merged PRs or documenting releases. Triggers on "write changelog", "release notes", "what shipped".
Use when reviewing a plan, PRD, product direction, or implementation proposal for strategy, scope, user value, ambition, and hidden assumptions. Triggers on "strategy review", "CEO review", "founder review", "think bigger", "rethink this", "is this ambitious enough".
Use when a first-pass fix works but is exploratory, messy, or overbuilt, and you want to delete it and reimplement a better version using what the first pass taught you. Triggers on "delete your fix and implement a better version", "hindsight refactor", "second pass refactor", "second pass rewrite", "rewrite after exploration", and "clean reimplementation".
Use when removing AI-generated slop, cleaning up verbose code, or removing unnecessary defensive checks. Triggers on "remove slop", "clean up AI code", "deslop".
Autonomous optimization loop inspired by Karpathy's AutoResearch. Point it at any measurable target and it will modify, measure, keep improvements, and discard regressions. Triggers on "autoresearch", "optimize this", "run the loop", "karpathy loop", "improvement loop".
Use when writing commands, hooks, skills for agents, or prompts for sub-agents or any other LLM interaction. Triggers on "optimize prompt", "improve LLM output", "prompt template", "write a skill", "system prompt".
Use when refactoring code for simplicity, removing duplication, or applying KISS/DRY/SOLID/YAGNI. Triggers on "refactor", "clean up code", "apply DRY".
Use when reviewing recent code changes for reuse, unnecessary complexity, quality issues, or efficiency problems before considering the work done. Triggers on "simplify", "clean up this diff", "review for reuse", "make this simpler", "quality pass", "efficiency pass".
Use when reducing cognitive complexity, flattening nested code, or simplifying functions. Triggers on "reduce complexity", "simplify", "too nested".
Use when the user provides an idea, feature request, Linear ticket, or concept that needs fleshing out, product validation, or office-hours-style questioning. Triggers on "interview me about X", "help me spec out Y", "I have an idea for Z", "flesh out this idea", "office hours", "is this worth building".
Use when creating, writing, editing, or improving shared skills for Codex, Claude Code, or other agent runtimes. Triggers on "create a skill", "write a skill", "improve skill", "skill description", "SKILL.md".
Use when debugging errors, diagnosing failures, performance regressions, flaky behavior, or tracing root causes from error output. Triggers on "debug this", "diagnose this", "why is this failing", "trace the error".
Use when writing a PRD from a Linear ticket or feature request. Triggers on "write PRD", "create requirements doc", "PRD from ticket".
Use when tests are failing and need systematic fixing until all pass. Triggers on "fix tests", "tests failing", "make tests pass".
Use when documentation should be synchronized after code changes, new skills, releases, merged PRs, or shipped work. Triggers on "update the docs", "sync docs", "post-ship docs", "documentation is stale", "refresh README".
Use when a plan, PRD, proposal, or implementation outline is overscoped, too ambitious for the immediate goal, or needs to be reduced to a bare-bones version. Triggers on "bare bones", "no damn whistles", "no bells and whistles", "strip this plan", "trim this plan", "scope creep", "descope this plan", "MVP only".
Conducts multi-source deep research with iterative refinement and structured synthesis. Triggers on "deep research", "research report", "comprehensive analysis", "analyze X", "compare X vs Y", "state of the art", "what does the research say about". NOT for: simple lookups, debugging, questions answerable in 1-2 searches, code review.
Use when writing, updating, or auditing a GitHub PR title or description. Triggers on "write PR description", "update PR body", "describe this PR", "refresh PR description", "PR title".
Convert a Markdown file into a nicely formatted Google Doc and open it in the browser. Use when the user wants to create a Google Doc from a .md file, share markdown content as a Google Doc, or invoke md2docs. Handles headings, bold, italic, inline code, fenced code blocks, tables, lists, links, horizontal rules, and mermaid diagrams.
Use when writing, migrating, or reviewing prompts, system prompts, commands, hooks, or agent skills for GPT-5.5 workflows, especially OpenAI Responses API or OpenRouter chat/completions hosts. Triggers on "GPT-5.5 prompt", "OpenRouter prompt", "prompt migration", "reasoning effort", "reasoning_details", "OpenAI system prompt".
Extract a DDD-style language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".
Use when panning recent merged PRs and agent session logs (Claude Code, Codex, Cursor) for compound-worthy moments to document, then queueing the gold through /ce-compound. Triggers on "goldpan", "pan for compound candidates", "pan for gems", "what should I /ce-compound", "find solutions to document", "scan sessions for learnings", "what did we learn last week", "compound candidates", "/v1-goldpan".
Use when implementing E2E tests, debugging flaky tests, testing web applications with Playwright, or establishing E2E testing standards. Triggers on "e2e test", "end-to-end", "Playwright", "flaky test", "browser test".
Use when shipping local work as a pull request. Triggers on "ship it", "create PR", "open PR", "submit PR", "/v1-pr".
Use when generating visual proof-of-work GIFs for PRs, recording browser demos of completed features, or creating animated artifacts of UI changes. Triggers on "prove work", "record demo", "GIF for PR", "visual proof", "proof of work", "/v1-prove-work".
Use when writing unit tests for code changes or new functionality. Triggers on "write tests", "add tests", "test this code".
Use when writing or improving communications to be more memorable and persuasive. Applies when drafting pitches, presentations, marketing copy, product messaging, emails, announcements, or any text that needs to stick. Also use proactively whenever producing copy that would benefit from stickiness -- landing pages, taglines, investor updates, team announcements, product descriptions. Triggers on "stickify", "make this sticky", "make this memorable", "SUCCESs framework", "Made to Stick".