audit
On-demand audit and analysis of agent orchestration flows via Sentinel Protocol
anti-conflict
Prevent file conflicts between multiple AI agents working in parallel
skill-writer
Guide users through creating Agent Skills for Claude Code. Use when the user wants to create, write, author, or design a new Skill, or needs help with SKILL.md files, frontmatter, or skill structure.
status-map
Generate human-readable ASCII status visualizations for agent sessions
sync-to-git
Git synchronization automation for AI agents with GitHub/Bitbucket support
brainstorming
브레인스토밍, 아이디어, 기획, 구상, 아이디어회의, 설계, 요구사항 분석, 접근법 탐색 - You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
code-conventions
코드 컨벤션, 코딩 스타일, 코드 스타일, 네이밍, 컨벤션, 타입스크립트, 파이썬, 자바, 함수 크기, 파일 크기 - Always apply when writing code. Code style, naming rules, function/file size limits for TypeScript, Python, and Java.
code-reviewer
code review, PR review, quality review, performance review - Expert at reviewing code for quality, adherence to architectural principles, security, and performance. Use this to ensure code meets project standards before merging or after implementation.
code-simpler
코드 단순화, 복잡도 감소, 심플리파이, 가독성, KISS, 인사이트 - Simplifies overly complex code. Reduces nesting, cyclomatic complexity, and unnecessary abstractions based on insight reports or code analysis.
architect
아키텍처, 설계, 시스템 설계, 구조 설계, 레이어 설계, 블루프린트, 컴포넌트 설계 - Use when designing systems, layer structures, module boundaries, or feature architectures. Provides both high-level system design (Clean Architecture, DDD) and actionable implementation blueprints.
build-error-resolver
빌드 에러, 빌드 오류, 컴파일 에러, 빌드 실패 해결 - Specialized in resolving build errors, compilation failures, and dependency issues. Systematic approach to diagnose and fix build problems.
code-explorer
코드 탐색, 실행 흐름, 아키텍처 분석, 의존성 분석, 코드베이스 이해, 심볼 분석, 레퍼런스 추적 - Deeply analyzes codebase by tracing execution paths, mapping architecture layers, and using Serena MCP for symbol navigation. Use when exploring or understanding code.
security-review
보안, 보안 리뷰, 보안 검토, 취약점, 보안 분석, OWASP, 인증, 인가, 취약점 점검 - Use when reviewing code for security vulnerabilities, designing authentication/authorization, or ensuring secure architecture. Provides systematic security analysis based on OWASP guidelines.
debug-specialist
디버깅, 디버그, 버그, 에러, 오류, 버그 수정, 원인 분석, 로그 분석, 트러블슈팅, 문제 해결 - Specialized in identifying root causes of bugs, analyzing error logs, and providing robust fixes. Use this when the user reports an error, unexpected behavior, or needs performance troubleshooting.
refactor-cleaner
리팩토링, 데드 코드, 사용하지 않는 코드, 코드 정리, 클린업 - Identifies and removes dead code, unused imports, and redundant code. Systematic cleanup while maintaining functionality.
e2e-runner
E2E 테스트, Playwright, 엔드투엔드, 통합 테스트, UI 테스트 - End-to-end testing workflow using Playwright. Generates, runs, and maintains E2E tests for web applications.
doc-coauthoring
문서 작성, 문서화, 문서, 스펙 작성, 기술 문서, 제안서, RFC, 설계 문서, 의사결정 문서 - Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content.
sequential-thinking
순차적 사고, 분석, 문제 해결, 복잡한 문제, 단계별 분석, 의사결정, 트레이드오프, 가설 검증 - Use when solving complex problems. Systematic thinking workflow using Sequential Thinking MCP for multi-step analysis, trade-off evaluation, and architectural decisions.
tdd-workflow
TDD, 테스트 주도 개발, 테스트 먼저, RED-GREEN-REFACTOR - Test-Driven Development workflow. Write tests first, then implement code to make tests pass. Enforces 80%+ coverage.
testing-strategy
테스트, 테스팅, QA, 테스트 전략, 품질 보증, 유닛 테스트, 통합 테스트, E2E, 테스트 커버리지 - Use when designing test strategies, writing test plans, or ensuring quality assurance. Guides systematic testing approach from unit to E2E with proper coverage and scenario design.
ui-ux-design
UI, UX, Design, Implementation, Interaction, Live Review - Create and review high-end frontend interfaces with live browser testing. Focus on distinctive aesthetics and production-grade code while avoiding generic 'AI slop'.
writing-plans
계획, 구현 계획, 플랜 작성, 작업 계획, 구현 플랜, 플랜 저장, TODO 저장, 계획 캡처, plan 저장, 플랜 캡처 - Use when you have a spec or requirements for a multi-step task, before touching code. Also captures Plan mode output to structured markdown files.
feature-development
기능 개발, 기능 구현, 신규 개발, 피처 개발, 개발 워크플로우 - Guided feature development with codebase understanding and architecture focus. Systematic 7-phase approach from discovery to implementation.
github-operator
Git 및 GitHub 작업 - 커밋, 브랜치 관리, 푸시, PR 생성 등 Git/GitHub 워크플로우가 필요할 때 사용. Use when performing Git and GitHub operations such as committing changes, managing branches, pushing to remote repositories, or creating pull requests.
harness
하네스, 테스트 주도 팀, TDD 팀, 병렬 개발, 스펙 구현 - Spec/PRD-driven parallel development using Agent Teams. Generates tests first, then orchestrates teammates to make all tests pass. Use when implementing a feature or project from a spec with agent teams.
prd-strategist
PRD, 기획서, 요구사항, 제품 기획, MVP, 제품 전략 - Use when brainstorming product ideas, creating PRD documents, defining MVP scope, or planning new features. MUST BE USED for any product strategy or requirements documentation tasks.
execute
Use when the user wants to execute tasks autonomously, run compounder on a tasks.md file, start autonomous development, compound through a task list, or implement tasks iteratively. Guides autonomous task execution using compound loops.
init
Initialize a new feature workflow with git worktree. Use when the user wants to start a new feature, create an isolated development branch, says "init worktree", or needs to set up a feature branch for compounder workflow.
ideate
Use when the user has an idea to brainstorm, wants to design a feature, needs help refining a concept, says "let's ideate", or describes a vague project needing structure. Guides structured brainstorming to produce a clear feature description ready for speckit.
skill-creator
Guide for creating effective skills. Use this skill when users want to create a new skill (or update an existing skill) that extends your capabilities with specialized knowledge, workflows, or tool integrations.
coding-guidelines
Coding patterns and guidelines for TypeScript/JavaScript, Rust, and frontend frameworks. Use this skill when writing TypeScript/JavaScript or Rust code, or working with SolidJS, Tailwind CSS, daisyUI, React Native, Expo, or NativeWind. Provides idiomatic patterns and best practices.
feature-workflow
Structured workflow for implementing new features with planning, clarification, and documentation. Use when implementing new features, making significant changes, or when the user requests a feature that requires planning and multiple implementation steps. Triggers on feature requests, multi-step implementations, or when explicit planning is beneficial.
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
consult-outside-expert
|
rails-audit-thoughtbot
Perform comprehensive code audits of Ruby on Rails applications based on thoughtbot best practices. Use this skill when the user requests a code audit, code review, quality assessment, or analysis of a Rails application. The skill analyzes the entire codebase focusing on testing practices (RSpec), security vulnerabilities, code design (skinny controllers, domain models, PORO with ActiveModel), Rails conventions, database optimization, and Ruby best practices. Outputs a detailed markdown audit report grouped by category (Testing, Security, Models, Controllers, Code Design, Views) with severity levels (Critical, High, Medium, Low) within each category.
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
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
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
systematic-debugging
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
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
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
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
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
planning-with-files
Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Page 1385 of 1404 · 70182 results
