architect
아키텍처, 설계, 시스템 설계, 구조 설계, 레이어 설계 - Use when designing systems, layer structures, or module boundaries. Architecture design guide based on Clean Architecture and DDD principles.
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
코드 리뷰, 코드리뷰, 리뷰, PR 리뷰, 검토 - 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.
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.
developer
개발, 구현, 기능 개발, 기능 구현, 코딩 - Use when implementing features. Business logic writing, library utilization, and implementation pattern guides.
doc-coauthoring
문서 작성, 문서화, 문서, 스펙 작성, 기술 문서, 제안서 - 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.
frontend-design
프론트엔드, 프론트, 웹 디자인, UI 개발, 웹 개발 - Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications.
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.
security-review
보안, 보안 리뷰, 보안 검토, 취약점, 보안 분석 - Use when reviewing code for security vulnerabilities, designing authentication/authorization, or ensuring secure architecture. Provides systematic security analysis based on OWASP guidelines.
sequential-thinking
순차적 사고, 분석, 문제 해결, 복잡한 문제, 단계별 분석 - Use when solving complex problems. Systematic thinking workflow using Sequential Thinking MCP for multi-step analysis, trade-off evaluation, and architectural decisions.
serena-exploration
코드 탐색, 코드 분석, 탐색, 코드 구조, 심볼 분석 - Use when exploring or analyzing code. Systematic code exploration workflow using Serena MCP tools for symbol navigation and reference tracking.
testing-strategy
테스트, 테스팅, QA, 테스트 전략, 품질 보증 - 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, 디자인, UI 디자인, UX 디자인, 사용자 경험 - 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.
writing-plans
계획, 구현 계획, 플랜 작성, 작업 계획, 구현 플랜 - Use when you have a spec or requirements for a multi-step task, before touching code