This skill should be used when working with Chrome extension service workers or background scripts. Trigger when: "service worker lifecycle", "background script", "extension service worker", "chrome.alarms", "offscreen document", "service worker restart", "top-level listener", "service worker idle", "event listener…
This skill should be used when working with data storage in Chrome extensions or when the user asks about extension storage patterns. Trigger when: "chrome.storage", "extension storage", "storage.local", "storage.sync", "storage.session", "IndexedDB in extension", "extension data persistence", "write-through cache"…
This skill should be used when writing or setting up tests for a Chrome extension. Trigger when: "test chrome extension", "extension unit test", "extension e2e test", "Vitest extension", "Playwright extension", "@webext-core/fake-browser", "test content script", "test service worker", "test messaging", "test storage"…
This skill should be used when debugging Chrome extension issues, diagnosing Chrome Web Store rejections, or troubleshooting build problems. Trigger when: "extension not working", "CWS rejection", "Chrome Web Store rejected", "Yellow Magnesium", "Purple Potassium", "Blue Argon", "Red Magnesium", "extension build…
This skill should be used when building React UI for Chrome extensions or when the user asks about UI patterns in extensions. Trigger when: "React in extension", "extension popup React", "side panel React", "Shadow DOM React", "content script UI", "createShadowRootUi", "extension accessibility", "rem to px extension"…
The specialist lanes and memory that the built-in /code-review doesn't have. Invokes the built-in engine for general bug-finding (quick/standard/deep map to its effort levels), then adds what it lacks: a mechanical hallucinated-imports validator (lockfile-verified across Python/JS/TS/Rust/Go, with a vendored denylist…
Review my code, code review, is this ready to ship, check for bugs, security audit, review this PR, pre-merge check, is this safe to deploy, check code quality. The specialist lanes and memory that the built-in /code-review doesn't have: it invokes the built-in engine for general bug-finding, then adds a mechanical…
Write, debug, reverse-engineer, and migrate AI prompts — now including agentic loops and goal conditions. The prompt-engineering skill covers writing patterns and platform-specific shape (Claude, GPT, Gemini, Claude Code, OpenAI Codex/AGENTS.md, image generators, agentic tools). The loop-goal-engineering skill authors.
Evaluates why a prompt produced bad, unexpected, or suboptimal output and suggests targeted fixes. Use when a user says "my prompt isn't working", "this prompt gives bad results", "why is my prompt failing", "debug this prompt", "the AI keeps getting this wrong", "fix my prompt", "prompt not producing expected…
This skill should be used when the user wants to author agentic loops or goal/completion conditions — "write a loop prompt", "loop engineering", "set up a ralph loop", "run Claude overnight", "write a /goal condition", "goal mode", "goal engineering", "stop condition for my agent", "completion criteria", "definition…
This skill should be used when the user says "decompile this prompt", "reverse engineer this prompt", "analyze this prompt", "break down this prompt", "what does this prompt do", "adapt this prompt for", "simplify this prompt", "split this prompt", "migrate this prompt", "why does this prompt work", "explain this…
This skill should be used when the user says "write a prompt", "prompt engineering", "system prompt", "optimize my prompt", "create instructions for", "context engineering", "CLAUDE.md", "few-shot examples", "write me a Midjourney prompt", "create a GPT prompt", "prompt for Claude Code", "agentic prompt", "tool…
A council of cognitive-framework advisors that debates any decision — repo plans, website designs, product/codebase critiques, marketing plans, anything — then votes and returns one ranked, confidence-rated recommendation with dissent preserved and a single concrete next step. Diversity comes from incompatible reason.
A single council seat that reasons under one injected cognitive framework. Used by the convene skill to produce an independent first-round draft (Stage 1) or a blind peer review (Stage 2). Parametrized — the dispatching prompt supplies the framework, the problem, and the schema. JSON-first output. Not for direct user…
The Chairman that synthesizes a council's drafts and reviews into one decisive, confidence-rated recommendation with dissent preserved and a single concrete next step. Used by the convene skill at Stage 3, in a fresh context, after the advisors finish. JSON-first, then renders the user-facing markdown report. Not for…
Convene a council, ask the council, debate this, get a panel to critique, run this by a council of experts, council of advisors, devil's advocate panel, red-team this decision, what would a panel say, multi-perspective critique, stress-test this decision, get diverse expert opinions and a recommendation. Convenes 3–5…
Explain a project to humans, honestly — without overpromising or inventing features that aren't in the repo. Five skills generate audience-targeted communications from your project's actual artifacts (code, docs, planning files): narrate-project — plain-English description, audience-adaptive (non-dev / investor /.
This skill should be used when the user says "draft a pitch", "write a pitch for [project]", "one-pager", "executive summary", "investor pitch", "grant proposal", "pitch deck content", "partnership memo", "draft a funding pitch", "write a long-form pitch", or wants a longer-form pitch document (one-pager, executive…
This skill should be used when the user says "write me an elevator pitch", "give me an elevator pitch", "30-second pitch", "one-paragraph pitch", "quick pitch for [project]", "pitch this in 30 seconds", "short pitch", "compress this to an elevator pitch", or wants a roughly 150-word / 30-seconds-spoken pitch for a…
This skill should be used when the user says "explain this document", "interpret this file", "what does this plan commit me to", "what does this ADR say", "interpret this architecture doc", "what does this AI-generated plan actually mean", "decompile this doc", "what's this file saying", "explain this to me in plain…
This skill should be used when the user says "audit my README", "ground my README against the code", "check if my README overpromises", "review my README honestly", "rewrite my README without marketing language", "audit my marketplace listing", "check my plugin description", "ground this description against the code"…
This skill should be used when the user says "narrate this project", "explain this project in plain English", "describe what this repo does", "summarize this project for a non-developer", "write a project narrative", "tell me what this project is", "explain this codebase to a collaborator", "draft an onboarding…
RAD Fastify — comprehensive Fastify framework coding standards, architectural guidance, and anti-pattern enforcement. Covers the encapsulation model and plugin DAG, hook lifecycle, JSON Schema validation with Ajv, response serialization with fast-json-stringify, Pino logging, TypeScript type providers, in-process…
Reviews Fastify application code for anti-patterns, encapsulation violations, and production readiness issues. Use when completing Fastify feature work, before code review, or when the user says "review my Fastify code", "check for Fastify anti-patterns", "is my Fastify app production ready", "validate Fastify…