review-initiative
Use after /breakdown-work or manual initiative creation, before running tasks. Use when initiative has 5+ tasks, multiple dependencies, or references a design document.
receiving-code-review
Use when receiving code review feedback - before implementing suggestions, especially if feedback seems unclear or technically questionable. Requires technical verification and honest evaluation, not performative agreement.
ralph-loop
Use when setting up autonomous agent execution loops for a project. Takes a completed design doc and produces IMPLEMENTATION.md, PROMPT files per loop, progress trackers, cross-validation, and ralph.sh runner. Use after brainstorming/design is done, before coding starts.
Python Style Standards
Python coding standards including line length (80 chars), naming conventions (snake_case, PascalCase), type hints, docstrings, exception handling, and logging patterns. Run python-code-quality script for automated checks (ruff + pyright + security). Use when writing new Python code or reviewing code quality.
plasma6-panel-config
Configure KDE Plasma 6 panels, widgets, digital clock fonts, and Panel Colorizer styling. Use when modifying panel appearance, copying panel configs between monitors, fixing widget fonts, or troubleshooting Panel Colorizer not applying styles.
cc-convo-explorer
Explore and search previous Claude Code conversations stored in ~/.claude/projects/
software-testing
Always use this skill when writing or editing software tests!
python
Always use this skill when writing or editing python code!
programming
Always use this skill when writing or editing code of any sort!
pdf-to-markdown
Extracting text and tables, merging/splitting documents. Use when needing to convert PDFs while preserving some structure.
markdown
Always use this skill when writing or editing markdown files!
command-creator
Create custom slash commands for AI coding assistants.
git-version-control
Always use this skill when using git!
week-report
Prepare weekly management report. Use when asked to create a weekly report,
google-docs-sheets
Export Google Docs and Google Sheets (spreadsheets) to Markdown files
commit
Auto-commit with smart branching. Use when asked to commit, push changes,
jira-confluence
Access Jira issues and Confluence pages via Python scripts with OAuth
demo-page
Create a polished, self-contained HTML demo page from any source material
data-analyst
Data analysis master. Use when asked to query a database, explore schema,
task-manager
Manage development tasks via md-task-mcp MCP server. Use when user asks about tasks, projects, or task management.
mvv-synthesis
Synthesize Mission, Vision, Values from ontological analysis output
agent-select
Analyze tasks and recommend optimal sub-agent(s) for execution
worktree-policy
Enforce mandatory git worktree usage for multi-agent file modifications
context-prep
Prepare optimal context package before delegating tasks to sub-agents
ttl-policy
Manage Time-To-Live policies for framework content freshness
hierarchical-merge
Enforce hierarchical merge protocol - branches merge to parent, not directly to main
ontological-analysis
Analyze repository through 8 philosophical dimensions for MVV extraction
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.
sync-to-git
Git synchronization automation for AI agents with GitHub/Bitbucket support
status-map
Generate human-readable ASCII status visualizations for agent sessions
code-conventions
코드 컨벤션, 코딩 스타일, 코드 스타일, 네이밍, 컨벤션, 타입스크립트, 파이썬, 자바, 함수 크기, 파일 크기 - Always apply when writing code. Code style, naming rules, function/file size limits for TypeScript, Python, and Java.
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.
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.
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.
feature-development
기능 개발, 기능 구현, 신규 개발, 피처 개발, 개발 워크플로우 - Guided feature development with codebase understanding and architecture focus. Systematic 7-phase approach from discovery to implementation.
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.
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.
refactor-cleaner
리팩토링, 데드 코드, 사용하지 않는 코드, 코드 정리, 클린업 - Identifies and removes dead code, unused imports, and redundant code. Systematic cleanup while maintaining functionality.
tdd-workflow
TDD, 테스트 주도 개발, 테스트 먼저, RED-GREEN-REFACTOR - Test-Driven Development workflow. Write tests first, then implement code to make tests pass. Enforces 80%+ coverage.
sequential-thinking
순차적 사고, 분석, 문제 해결, 복잡한 문제, 단계별 분석, 의사결정, 트레이드오프, 가설 검증 - Use when solving complex problems. Systematic thinking workflow using Sequential Thinking MCP for multi-step analysis, trade-off evaluation, and architectural decisions.
code-simpler
코드 단순화, 복잡도 감소, 심플리파이, 가독성, KISS, 인사이트 - Simplifies overly complex code. Reduces nesting, cyclomatic complexity, and unnecessary abstractions based on insight reports or code analysis.
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-explorer
코드 탐색, 실행 흐름, 아키텍처 분석, 의존성 분석, 코드베이스 이해, 심볼 분석, 레퍼런스 추적 - Deeply analyzes codebase by tracing execution paths, mapping architecture layers, and using Serena MCP for symbol navigation. Use when exploring or understanding code.
build-error-resolver
빌드 에러, 빌드 오류, 컴파일 에러, 빌드 실패 해결 - Specialized in resolving build errors, compilation failures, and dependency issues. Systematic approach to diagnose and fix build problems.
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.
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.
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.
Page 1527 of 1547 · 77309 results
