Use this skill when a repository already has an open pull request and you need to run the Coder Agents Review loop: request review with /coder-agents-review when needed, wait for feedback from the coder-agents-review GitHub app, fix issues, and repeat until the app comments approved.
Authoring workflow and guardrails for writing, moving, or restructuring Coder documentation under docs/. Points at the canonical content guidelines and prose style guide, then walks research, routing, Diátaxis mode, structure, pedagogy, and validation. Counterpart to the doc-check skill, which reviews changes for…
Turn a curious developer into an activated one: the docs, the quickstart, and the first-run experience that gets them to their first real win fast, and back again. Use when people sign up or star the repo but never get it working, come once and never return, or you're about to pour traffic into a first-run that leaks.
Help the user decide what to charge and how to package it: the value metric, the tiers, the free-to-paid line, and finding the actual number. Use when the user is guessing at a price, priced too cheap and can't change it, is stuck on free vs paid, or believes "developers won't pay" so never charges.
Turn hand-made first-50 traction into self-reinforcing acquisition loops, so the next 5,000 users come from usage, not founder hours. Use when growth stalls the moment the user stops pushing, every signup traces back to a DM or one launch spike, or they're reaching for "more channels" when the real gap is that using…
Use when reading, writing, extending, or testing Flemma configuration — covers the CoW layer store, schema DSL, proxy/lens API, and common patterns. Trigger on any work touching flemma.config, flemma.opt, config.get, config.writer, config.materialize, config.lens, schema definition, DISCOVER callbacks, or…
Use when asked to profile Flemma performance, compare keystroke latency between branches, or run the profiling harness. Trigger on "profile", "perf", "benchmark", "keystroke latency", or "InsertCharPre".
Use when naming or cutting a Flemma minor release — picking a codename, running pnpm changeset version, or writing GitHub release notes. Assigns a single-word typographic codename matched to the release's headline work and logs it in the ledger so names are never reused. Trigger on "release name", "codename", "name…
AI-optimized browser automation CLI with context-efficient snapshots. Use for long autonomous sessions, self-verifying workflows, video recording, and cloud browser testing (Browserbase).
Automate browsers with Puppeteer CLI scripts and persistent sessions. Use for screenshots, performance analysis, network monitoring, web scraping, form automation, JavaScript debugging.
ALWAYS activate this skill when you are asked to FIX a bug, error, test failure, CI/CD issue, type error, lint error, log error, UI issue, or code problem. Uses hapo:debug for evidence-first diagnosis before any code change.
Structured Chain-of-Thought (CoT) & Deep Reasoning Protocol for complex problem analysis, architectural decisions, security evaluations, and deep troubleshooting. Activate when --deep or --cot flag is present in workflows, or when deep architectural reasoning is required. Supports MCP Graph integration for…
Manage setmac releases, semantic-release versioning, signing, notarization, and packaged app hotfixes. Use when working on GitHub Actions release workflows, changelog/version bumps, DMG or standalone CLI artifacts, Gatekeeper issues, or launch failures in shipped builds.
Multi-round adversarial code review loop — four specialized agents (correctness, adversarial, API design, test rigor) run in parallel against a PR, repeated until all four return CLEAN — ship it or a budgeted number of rounds (default 5) is exhausted — whichever comes first, with two ask-first soft stops in between (a…
This skill should be used when the user is starting a new Electrobun project, is unsure which electrobun skill or command to use, wants an overview of the electrobun-dev plugin, or asks "which electrobun skill", "electrobun plugin guide", "electrobun overview". Lists all skills, commands, and agents with when-to-use…
This skill should be used when the user is building electrobun features for the milady-ai/milady project, submitting PRs to milady that will be reviewed by the agent-review system, asks about "electrobun milady", "milady electrobun PR", trust tiers, Biome compliance, or the release-electrobun.yml workflow.
This skill should be used when the user asks to "write electrobun tests", "add electrobun test coverage", "electrobun testing", "defineTest pattern", generating new electrobun test suites, or reverse-engineering electrobun component behaviour from test source.