finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
tidb-test-guidelines
Decide where to place TiDB tests and how to write them (basic structure, naming, testdata usage). Use when asked about test locations, writing conventions, shard_count limits, casetest categorization, or when reviewing test changes in code review.
content-strategy
When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," or "content planning." For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit.
front-loading
Put the answer first, then context and details follow. Use when writing documentation, tutorials, error messages, or any communication where readers need to decide quickly if something is relevant to them.
satori
Persistent long term memory for for continuity in ai sessions between providers and codegen tools. TRIGGERS - Activate this skill when: - User explicitly mentions "satori", "remember this", "save", "add", "save this for later", "store this", "add to memory" - User asks to recall/search past decisions: "what did we decide", "remind me", "search my notes", "what do I know about" - Conversation contains notable facts worth persisting: decisions, preferences, deadlines, names, tech stack choices, strategic directions - Starting a new conversation where proactive context retrieval would help - Use Satori search when user asks a question
ngrok-unofficial-webhook-skill
Start an ngrok tunnel to receive incoming webhooks and process them via the LLM. Use when the user asks to listen for webhooks, set up a webhook endpoint, start ngrok, or when another skill (like Zoom RTMS Meeting Assistant) needs a public webhook URL. Receives webhook payloads and lets the LLM decide how to handle them.
obra/superpowers@finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
my-skill-name
Brief description of what this skill does and when to use it. Be specific about capabilities and use cases to help agents decide when to load this skill.
pr-triage
Context-efficient PR comment triage. Evaluate, decide, act. Fix important issues, resolve the rest silently.
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
startup-pivoting
Help users decide when and how to pivot their startup. Use when someone is questioning their current direction, seeing poor traction, considering a major strategy change, or stuck in the pre-PMF stage.
quality-speed
Decides when quality matters vs move fast, based on Dylan Field (Figma) craft philosophy and Brian Chesky (Airbnb) details obsession. Use when balancing shipping speed with excellence, deciding if refactoring is needed, or determining which details create moats vs which to skip.
content-strategy
When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," or "content planning." For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit.
using-generic-agents
Use to decide what kind of generic agent you should use
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
aposd-maintaining-design-quality
Enforce strategic programming discipline when modifying existing code. Guide through STOP-ASK-DECIDE-VERIFY workflow with urgency tier assessment (trivial/minor/standard/emergency). Include when NOT to refactor (Chesterton's Fence, performance-critical, no tests) and block tactical shortcuts via anti-rationalization tables. Use when fixing bugs, extending features, or tempted to make quick fixes. Triggers on: modify code, fix bug, extend feature, quick fix, tactical change.
recall
Retrieves cross-session memories about past decisions, lessons, and patterns. Use when user asks about prior work, past decisions, or mentions a feature. Triggers include check memory, what did we decide, how did we solve.
sc-think
Socratic thinking partner for decisions, debugging mental models, and working through uncertainty. This skill SHOULD be used when the user says "I'm stuck", "should I", "can't decide", "not sure if", "is this the right approach", "what do you think about", "help me think through", "review my plan", "am I missing something", "what am I assuming", "let me think", "brainstorm", "help me figure out", "sanity check", "does this make sense", or expresses uncertainty about a decision, design, or direction. Activates dialectical reasoning to surface assumptions, challenge positions, and find the right question to ask.
task-router
Decision matrix for choosing optimal approach to any task. Helps Claude decide when to delegate to sub-agents vs. working directly. Use when starting a new task or unsure of best approach.
ooda
OODA loop decision framework (Observe, Orient, Decide, Act). Use for complex decisions, problem-solving, unclear situations, or when someone is jumping to solutions without analysis.
context-witness
Decide between Context Tag witness and capability patterns for dependency injection, understanding coupling trade-offs
aggregate-design
Performs code reviews and design assistance based on DDD aggregate design rules. Used for designing new aggregates, reviewing existing aggregates, and during refactoring. Triggered by aggregate-design–related requests such as: 'I want to design an aggregate', 'Review an aggregate', 'Implement an Aggregate', 'Decide aggregate boundaries', 'Implement with DDD', etc.
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
decision-frameworks
Expert in decision-making frameworks - systematic approaches to making better decisions under uncertainty. Covers decision criteria, reversibility assessment, stakeholder alignment, and decision documentation. Knows when to decide fast and when to deliberate. Use when "decision framework, how to decide, making a choice, tradeoff, should we, pros and cons, decision matrix, weighing options, " mentioned.
landing-page-design
World-class landing page expertise combining conversion rate optimization science, persuasive design psychology, and the craft of pages that turn visitors into customers. Landing pages are where marketing meets reality—the moment of truth where visitors decide. Great landing pages aren't just pretty—they're conversion machines. The best landing page designers understand that every element must earn its place, that friction is the enemy, and that the goal isn't to impress—it's to convert. Speed, clarity, and persuasion in perfect balance. Use when terms like 'landing page, conversion page, lead capture, signup page, pricing page, hero section, above the fold, CTA design, conversion rate, page optimization, lead gen page, squeeze page, sales page, landing-pages, conversion, CRO, design, optimization, lead-generation, signups, forms' are mentioned.
total-recall
Search past conversations and sessions with Antonio. Use when he asks to remember/find something discussed before, what was decided about X, or to look back at previous sessions. Triggers: 'recuerdas cuando...', '¿qué decidimos sobre...?', 'busca en conversaciones anteriores', 'find where we discussed...'. Requires contextify CLI.
effects
OCaml 5 algebraic effects design patterns. Use when Claude needs to: (1) Design APIs that interact with effect-based schedulers, (2) Decide between effects vs exceptions, (3) Integrate libraries with Eio or affect, (4) Handle suspension vs error cases in streaming code, (5) Understand the layered effect design principle
context-manager
Manages permanent memory storage for decisions, blockers, context, preferences, and procedures. Use when user says "remember", "save this decision", "what did we decide", "recall", "search memories", "any blockers", or when making important architectural decisions. Provides SDAM compensation through external memory.
startup-pivoting
Decide whether/how to pivot a startup or product and produce a Pivot Decision & Execution Pack (diagnosis, exhaustion check, pivot options map, pivot thesis + metrics, validation plan, execution plan, decision memo). Use for “should we pivot?”, “stuck pre-PMF”, “growth stalled”, “change ICP”, “reposition”, “major strategy reset”.
discover-discuss-decide-framework
A structured process for group decision-making that eliminates groupthink, surfaces hidden disagreements, and increases hit rates. Use this when building product roadmaps, hiring for key roles, or setting strategic priorities.
workflow-router
Determine next agent based on state machine rules. Use AFTER receiving any BAZINGA agent response to decide what to do next.
problem-solving
Systematic problem-solving with Good Teacher mode (default). AI guides through questions, not answers - inspired by Polya's "How to Solve It". Use when user needs to: (1) Solve problems methodically, (2) Learn to think through challenges, (3) Develop problem-solving skills, (4) Find root cause of issues. Triggers: "problem", "solve", "stuck", "how do I", "figure out", "analyze", "debug", "decide", "แก้ปัญหา", "ช่วยคิด", "ติดปัญหา"
website-structure
When the user wants to plan website structure, decide which pages to build, or prioritize pages for a new or existing site. Also use when the user mentions "website structure," "site structure," "which pages do I need," "page planning," "sitemap planning," "Must Have pages," "website architecture," or "site hierarchy."
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
calibrate
Post-launch AI feature calibration workflow. Document error patterns, review eval performance, and decide on agency promotion. Based on CC/CD framework for continuous calibration of AI products.
Skill Name
A clear description of what this skill does and when to use it. Include specific trigger keywords and task types that should activate this skill. Be specific about capabilities so the AI can decide when to load it. Maximum 1024 characters.
malware-triage
Systematic malware triage and initial assessment workflow for professional malware analysis. Use when the user needs to perform initial malware assessment, classify samples, determine analysis priority, identify quick indicators, or decide on next analysis steps. Also use for rapid malware identification and threat classification.
decide
Personal decision advisor that prioritizes QUALITY over speed. Uses exhaustive discovery, option finding, sequential elimination, and structured analysis. Intended for investments, purchases, career moves, and life decisions. Surfaces hidden factors, tracks eliminations with reasons, and produces confident recommendations. Triggers: "help me decide", "should I...", "which should I choose", "compare options", "what should I do", "weighing options".
chain-of-responsibility
Behavioral pattern that passes requests along a chain of handlers, where each handler decides to process the request or pass it to the next handler. Use when multiple objects may handle a request and the handler isn't known in advance.
context-manager
Manages permanent memory storage for decisions, blockers, context, preferences, and procedures. Use when user says "remember", "save this decision", "what did we decide", "recall", "search memories", "any blockers", or when making important architectural decisions. Provides SDAM compensation through external memory.
bonfire
Session context persistence for AI coding. Start/end sessions, create outcome specs and docs, review work. Use for session management, "start session", "end session", outcome specs, documentation, code review, or questions about previous work, decisions, blockers, "last time", "what we decided".
content-strategy
When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," or "content planning." For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit.
skill-anatomy
Comprehensive guide for understanding and fixing skill structure issues. Use this skill when skills aren't loading, when creating new skills, when organizing skills for open-source vs personal use, or when troubleshooting Claude Code skill discovery. Covers flat hierarchy requirement (each skill must be a direct child of .claude/skills/), required SKILL.md with YAML frontmatter containing name and description, and that the description is the primary trigger mechanism used to decide invocation. Provides concrete commands to create a new skill, reminder to restart Claude Code because skills load at startup, limits for the Markdown body, optional bundled resource folders, gitignore patterns, and the personal- prefix convention for local-only skills.
session-brain
Persistent working memory for coding sessions. Automatically tracks what you're doing, why you're doing it, decisions made, and what's next. Trigger phrases: - "resume where we left off" - "what were we doing?" - "recap this repo" / "catch me up" - "remember this decision: ..." - "why did we decide to ..." / "what was the rationale for ..." - "what's next?" / "what should I work on?" - "what are the open questions?" - "save this as a project rule"
analyze-m1-module-for-migration
Systematically analyze a Magento 1 module to determine its purpose, usage, and migration requirements for Magento 2. Use when you need to decide whether to migrate a M1 module, find alternatives, or skip it.
intent-changes
Manage structured change proposals for design documents with PR-like review experience. Use /intent-changes start <file> to begin, /intent-changes propose to suggest changes, /intent-changes accept/reject to decide, /intent-changes finalize to apply.
fullstory-privacy-strategy
Strategic guide for data privacy in Fullstory implementations. Teaches developers how to decide what data to send, mask, exclude, hash, or replace with joinable keys. Covers regulatory compliance (GDPR, HIPAA, PCI, CCPA), privacy-by-design principles, and balancing analytics value with privacy protection. Acts as a decision framework that references core privacy skills.