Prompts
Prompt engineering and templates
estimation-fermi
by lyndonkl
Use when making quick order-of-magnitude estimates under uncertainty (market sizing, resource planning, feasibility checks), decomposing complex quantities into estimable parts, bounding unknowns with upper/lower limits, sanity-checking strategic assumptions, or when user mentions Fermi estimation, back-of-envelope calculation, order of magnitude, ballpark estimate, triangulation, or needs to assess feasibility before detailed analysis.
chef-assistant
by lyndonkl
Use when cooking or planning meals, troubleshooting recipes, learning culinary techniques (knife skills, sauces, searing), understanding food science (Maillard reaction, emulsions, brining), building flavor profiles (salt/acid/fat/heat balance), plating and presentation, exploring global cuisines and cultural food traditions, diagnosing taste problems, requesting substitutions or pantry hacks, planning menus, or when users mention cooking, recipes, chef, cuisine, flavor, technique, plating, food science, seasoning, or culinary questions.
video-prompting
by Square-Zero-Labs
Draft and refine prompts for video generation models (text-to-video and image-to-video). Use when a user asks for a "video prompt" or a model-specific prompt such as Ovi, Sora, Veo 3, Wan 2.2, or LTX-2, including requests like "text-to-video prompt", "image-to-video prompt", or "write a prompt for [model]".
clone-research
by wcygan
Comprehensive product research for building an MVP clone. Spawns 4 parallel research agents to produce 9 standardized documents: Product Thesis, Feature Priority Matrix, MVP Scope Contract, Core User Journeys, Domain Model, System Architecture, Revenue & Pricing Model, API Surface Spec, and Design System Brief. Use when planning a clone, building a competitor alternative, scoping an MVP, or analyzing a product to replicate. Keywords: clone, MVP, product research, teardown, feature matrix, domain model, reverse engineer, competitor clone
new-skill
by wcygan
Interactive wizard to create new agent skills for Claude Code. Use when creating skills, building agent capabilities, adding model-invoked workflows, or setting up skill directories. Keywords: create skill, new skill, agent skill, skill wizard, build skill, SKILL.md
new-global-skill
by wcygan
Interactive wizard to create new global Claude Code skills for dotfiles distribution. Use when creating skills available across all projects, adding personal workflows to dotfiles, or scaffolding ~/.claude/skills. Keywords: create global skill, new global skill, dotfiles skill, personal skill, cross-project skill, global workflow
competitor-analysis
by wcygan
Comprehensive competitor research using a 7-agent team. Spawns parallel research agents for product, marketing, UX, and technical analysis, then sequential synthesis agents for MVP spec, go-to-market strategy, and competitive landscape. Use when evaluating a competitor, planning a new product, or scoping an MVP. Keywords: competitor, competitive analysis, market research, product research, MVP, go-to-market, GTM, teardown, product teardown
context-decorate
by wcygan
Scan a codebase and place CLAUDE.md context files in directories that lack them. Spins up a team of subagents to parallelize the work — each agent covers a few directories and generates a succinct overview of the directory's purpose and key subdirectories. Use when onboarding to a new codebase, improving Claude context quality, annotating project structure, or scaffolding directory-level context for AI assistants. Keywords: context, CLAUDE.md, annotate, codebase, directory, onboard, decorate, scaffold context, context files.
new-agent
by wcygan
Create custom Claude Code subagents. Interactive wizard that gathers requirements, generates the agent .md file with proper frontmatter and system prompt. Use when creating a new agent, adding a subagent, or making a custom agent available globally. Keywords: agent, subagent, create agent, new agent, custom agent
llm-artifacts-detection
by existential-birds
Detects common LLM coding agent artifacts in codebases. Identifies test quality issues, dead code, over-abstraction, and verbose LLM style patterns. Use when cleaning up AI-generated code or reviewing for agent-introduced cruft.
op-session
by sd0xdev
"Initialize 1Password CLI session for Claude Code. Use when: starting a session that needs 1Password secrets, op CLI keeps prompting biometric auth, setting up OP_SESSION token. Solves: Claude Code's no-TTY subprocess model triggers 1Password biometric auth on every op call. After running once, all subsequent op commands use the cached session token."
request-tracking
by sd0xdev
"Request tracking knowledge base. Use when: querying request status, managing document references, tracking progress. Not for: creating requests (use create-request), tech specs (use tech-spec). Output: status report + progress tracking."
codex-code-review
by sd0xdev
"Code review using Codex MCP. Use when: PR review, code audit, second opinion on changes. Not for: doc review (use doc-review), security audit (use security-review). Output: severity-grouped findings + merge gate."
codex-architect
by sd0xdev
"Codex architecture consulting. Use when: designing features, evaluating architecture, getting second opinion on design. Not for: implementation (use codex-implement), code review (use codex-code-review). Output: architecture advice + design recommendations."
codex-brainstorm
by sd0xdev
"Adversarial brainstorming via Claude+Codex debate. Use when: exploring solutions, feasibility analysis, exhaustive enumeration. Not for: implementation (use feature-dev), architecture only (use codex-architect). Output: Nash equilibrium consensus + action items."
claude-health
by sd0xdev
"Claude Code config health check. Use when: auditing .claude/ structure, checking naming, verifying hook setup. Not for: skill quality (use skill-health-check), code review (use codex-code-review). Output: health report + fix recommendations."
code-investigate
by sd0xdev
"Dual-perspective code investigation. Use when: deep code analysis needing both Claude and Codex perspectives. Not for: quick exploration (use code-explore), code review (use codex-code-review). Output: integrated findings from dual analysis."
project-setup
by sd0xdev
"Project configuration initialization. Use when: first-time setup, auto-detecting framework, replacing CLAUDE.md placeholders. Not for: ongoing config checks (use claude-health), skill creation (use create-skill). Output: configured CLAUDE.md + project settings."
test-review
by sd0xdev
"Test coverage review via Codex MCP. Use when: reviewing test sufficiency, identifying coverage gaps, test quality audit. Not for: generating tests (use codex-test-gen), code review (use codex-code-review). Output: coverage analysis + gap report."
discovery-interviews-surveys
by lyndonkl
Use when validating product assumptions before building, discovering unmet user needs, understanding customer problems and workflows, testing concepts or positioning, researching target markets, identifying jobs-to-be-done and hiring triggers, uncovering pain points and workarounds, or when users mention user research, customer interviews, surveys, discovery interviews, validation studies, or voice of customer.
expected-value
by lyndonkl
Use when making decisions under uncertainty with quantifiable outcomes, comparing risky options (investments, product bets, strategic choices), prioritizing projects by expected return, assessing whether to take a gamble, or when user mentions expected value, EV calculation, risk-adjusted return, probability-weighted outcomes, decision tree, or needs to choose between uncertain alternatives.
chain-roleplay-debate-synthesis
by lyndonkl
Use when facing decisions with multiple legitimate perspectives and inherent tensions. Invoke when stakeholders have competing priorities (growth vs. sustainability, speed vs. quality, innovation vs. risk), need to pressure-test ideas from different angles before committing, exploring tradeoffs between incompatible values, synthesizing conflicting expert opinions into coherent strategy, or surfacing assumptions that single-viewpoint analysis would miss.
self-improvement
by pskoett
"Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Claude ('No, that's wrong...', 'Actually...'), (3) User requests a capability that doesn't exist, (4) An external API or tool fails, (5) Claude realizes its knowledge is outdated or incorrect, (6) A better approach is discovered for a recurring task. Also review learnings before major tasks. For CI-only/headless learning capture, use self-improvement-ci."
agent-sdk-builder
by OpenHands
Guided workflow for building custom AI agents using the OpenHands Software Agent SDK. Use when you want to create a new agent through an interactive interview process that gathers requirements and generates implementation plans.