create-mcp-skill
Create a new skill that uses an MCP server, following best practices from the MCP CLI guide. Use when user wants to create a skill for a new MCP server or integrate MCP functionality into a skill.
create-plan
Create comprehensive implementation plan in .plans directory based on analysis or report. Use when user asks to create a plan, plan implementation, design a solution, or structure work for a feature/refactor/fix.
create-pr
Create a PR for this branch. ALWAYS links related issues and uses closing keywords to auto-close them on merge.
create-skill
This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
create-subagent
This skill should be used when creating custom subagents for Claude Code, configuring specialized AI assistants, or when the user asks about agent creation, agent configuration, or delegating tasks to subagents. Covers both file-based agents and Task tool invocation.
ctx
Use when starting a session on a project, returning after time away, or before making significant changes. Essential for building comprehensive understanding of project state through total recall and deep exploration.
delphi
This skill should be used when the user asks to "use delphi", "ask delphi", or wants multiple parallel oracle investigations of the same question to discover divergent insights. Delphi launches multiple oracle agents simultaneously with identical prompts, allowing them to independently explore and potentially discover different paths, clues, and solutions. Results are saved to .oracle/[topic]/ and synthesized into a final document.
design-spec-extraction
Extract comprehensive JSON design specifications from visual sources including Figma exports, UI mockups, screenshots, or live website captures. Produces W3C DTCG-compliant output with component trees, suitable for code generation, design documentation, and developer handoff.
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
file-name-wizard
Audit all filename and naming conventions in the codebase against CLAUDE.md standards and common patterns. Use when user asks to check naming conventions, audit filenames, find naming inconsistencies, or validate file naming patterns.
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
gh-ticket
Create or update comprehensive GitHub issues that capture ALL context, requirements, and implementation details. Use when creating or updating tickets, issues, feature requests, or bug reports. Ensures no context is lost between ticket creation and implementation - the moment you ask for a ticket, there's maximum context available that will be lost if not captured now.
obsidian-plan-wiki
Create and manage behavior specification wikis in Obsidian format. Use when creating specs, documenting features, or when user mentions "wiki", "spec", "feature", or "Obsidian".
obsidian-upgrade
Upgrade Obsidian wikis to latest format. Handles structure migration (phases/tasks → features/specs), comment format upgrades (adding emoji prefixes), and Johnny Decimal feature organization. Use when user mentions "upgrade wiki", "migrate wiki", "update wiki format", or has old-format comments.
receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
review-changes
Code review of current git changes, compare to related plan if exists, identify bad engineering, over-engineering, or suboptimal solutions. Use when user asks to review changes, check git diff, validate implementation quality, or assess code changes.
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
superpower-zustand
MANDATORY for creating Zustand stores. This skill is required when users request state management, creating stores, or mention Zustand. Do NOT create Zustand stores without this skill - all stores must use the required StoreBuilder pattern with immer middleware and factory pattern separation
systematic-debugging
ONLY USE THIS SKILL UPON USER/HOOMAN REQUEST TO USE EXACTLY THIS SKILL, ONLY RUN ON HOOMAN [OK]. Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
the-archivist
This skill should be used when engineering decisions are being made during code implementation. The Archivist enforces decision documentation as a standard practice, ensuring every engineering choice includes rationale and integrates with Architecture Decision Records (ADRs). Use when writing code that involves choosing between alternatives, selecting technologies, designing architectures, or making trade-offs.
the-oracle
This skill should be used when the user asks to "use the oracle" or "ask the oracle" for deep research, analysis, or architectural questions. The oracle excels at multi-source research combining codebase exploration and web searches, then synthesizing findings into actionable answers. Use for complex questions requiring investigation across multiple sources, architectural analysis, refactoring plans, debugging mysteries, and code reviews.
update-docs
Update all documentation in .plans, CLAUDE.md files, docs, and .tasks to match current codebase state. Use when user asks to update docs, refresh documentation, sync docs with code, or validate documentation accuracy.
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
using-superpowers
Guidelines for using skills effectively - load relevant skills before complex tasks, not every message
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
video-explorer
This skill should be used when analyzing video files. Claude cannot process video directly, so this skill extracts frames hierarchically - starting with a quick overview, then zooming into regions of interest with higher resolution and temporal density. Use when asked to watch, analyze, review, or understand video content.
writing-clearly-and-concisely
Apply Strunk's timeless writing rules to ANY prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Makes your writing clearer, stronger, and more professional.
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
webrecon
WebRecon - reconnaissance tool using parallel Chrome instances for competitive analysis, design extraction, and API discovery
memory-management
Manages long-term memory for users across conversations. Automatically queries relevant memories when starting a new topic, and saves important personal information, habits, schedules, and user-requested memories. Use this when discussing user background, preferences, or plans; starting a new task or project; users mention personal details or ask to remember something.
api-docs
Generate OpenAPI/Swagger documentation from code
code-docs
Generate or update documentation from code analysis
dependency-update
Check for outdated packages and create update PRs
hotfix-workflow
Rapid hotfix branch creation, fix application, and PR to main
security-scan
Run security checks before PR including secrets, vulnerabilities, and best practices
sprint-summary
Generate sprint review summary from completed Jira tickets
standup-report
Generate daily standup summary from Git commits and Jira activity
tech-debt-report
Find TODOs, deprecated APIs, and outdated patterns in codebase
context7-mcp
Retrieve official library documentation and API references. Use when the user asks for "docs", "API signature", "usage examples", or "how to use" a specific package.
flutter-std
Build and debug Flutter/Dart apps with Riverpod (codegen), Freezed, and GoRouter. Use when implementing Flutter features, running apps, hot reload/restart, or debugging UI.
gh-cli
Interact with GitHub repositories, PRs, and issues using the `gh` CLI. Use when the user asks to "list PRs", "check out PR", "view issue", or "create release".
supabase-rest
Inspect Supabase database schemas and data. Use when the user asks to "check table", "list columns", or "query data" in Supabase. READ-ONLY.
use-fllib
Use fl_lib stores, widgets, utils, and extensions in Flutter apps. Use when requests mention fl_lib APIs or integration.
use-zfeats
Plan and execute complex features using markdown checklists. Use when the user asks to "plan a feature", "create a checklist", or "break down a task".
customer-experience
Expert customer service guidance from Madame Zelda for managing guest interactions, queue flow, and creating memorable festival experiences
festival-marketing
Marketing and communications expertise from Elena covering last-minute requests, emergency protocols, channel selection, and timeline management for festival communications
Page 1012 of 1445 · 72244 results