writing-skills
Use when creating new skills, editing existing skills, or verifying skills work correctly. Applies TDD methodology to process documentation - test with pressure scenarios, write the skill, verify compliance.
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.
MCP Integration
Set up and use MCP (Model Context Protocol) servers to extend Claude Code capabilities including PRISM semantic memory, filesystem access, and database integration. Use when setting up MCP servers, debugging MCP connections, or understanding MCP tool usage.
AI Documentation Standards
Write AI-readable documentation using context engineering principles, nested AGENTS.md hierarchy (CLAUDE.md is a thin shim), .claude/rules/ with path-scoping, structured formats, and the litmus test. Use when writing documentation, updating docs, or optimizing existing docs.
brainstorm
Use when starting any non-trivial feature, design, or behavior change - before writing code or creating tasks. Guides collaborative design exploration through focused questioning to produce a validated spec.
agent-prompting
Write effective prompts for Task tool sub-agents, slash commands, and system prompts. Covers Claude 4.x prompting patterns, context engineering, output format specification, and parallel delegation. Use when spawning sub-agents, creating slash commands, or writing system prompts.
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.
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.
programming
Always use this skill when writing or editing code of any sort!
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!
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!
git-version-control
Always use this skill when using git!
command-creator
Create custom slash commands for AI coding assistants.
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
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
data-analyst
Data analysis master. Use when asked to query a database, explore schema,
commit
Auto-commit with smart branching. Use when asked to commit, push changes,
task-manager
Manage development tasks via md-task-mcp MCP server. Use when user asks about tasks, projects, or task management.
ttl-policy
Manage Time-To-Live policies for framework content freshness
ontological-analysis
Analyze repository through 8 philosophical dimensions for MVV extraction
worktree-policy
Enforce mandatory git worktree usage for multi-agent file modifications
status-map
Generate human-readable ASCII status visualizations for agent sessions
sync-to-git
Git synchronization automation for AI agents with GitHub/Bitbucket support
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.
context-prep
Prepare optimal context package before delegating tasks to sub-agents
audit
On-demand audit and analysis of agent orchestration flows via Sentinel Protocol
hierarchical-merge
Enforce hierarchical merge protocol - branches merge to parent, not directly to main
anti-conflict
Prevent file conflicts between multiple AI agents working in parallel
agent-select
Analyze tasks and recommend optimal sub-agent(s) for execution
mvv-synthesis
Synthesize Mission, Vision, Values from ontological analysis output
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.
e2e-runner
E2E 테스트, Playwright, 엔드투엔드, 통합 테스트, UI 테스트 - End-to-end testing workflow using Playwright. Generates, runs, and maintains E2E tests for web applications.
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.
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'.
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.
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.
refactor-cleaner
리팩토링, 데드 코드, 사용하지 않는 코드, 코드 정리, 클린업 - Identifies and removes dead code, unused imports, and redundant code. Systematic cleanup while maintaining functionality.
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.
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.
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.
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.
Page 1613 of 1635 · 81720 results
