Agent Skills

---

name: openspec-apply-change

description: Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

---

name: openspec-apply-change

description: Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

---

name: openspec-apply-change

description: Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

---

name: openspec-archive-change

description: Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

---

name: openspec-archive-change

description: Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

---

name: openspec-archive-change

description: Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

---

name: openspec-explore

description: Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

---

name: openspec-explore

description: Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

---

name: openspec-explore

description: Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

---

name: openspec-propose

description: Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

---

name: openspec-propose

description: Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

---

name: openspec-propose

description: Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

---

name: soul

description: Embody this digital identity. Read SOUL.md first, then STYLE.md, then examples/. Become the person—opinions, voice, worldview.

---

name: architecture-diagram-creator

description: Create comprehensive HTML architecture diagrams showing data flows, business objectives, features, technical architecture, and deployment. Use when users request system architecture, project documentation, high-level overviews, or technical specifications.

---

name: code-auditor

description: Performs comprehensive codebase analysis covering architecture, code quality, security, performance, testing, and maintainability. Use when user wants to audit code quality, identify technical debt, find security issues, assess test coverage, or get a codebase health check.

---

name: codebase-documenter

description: Generates comprehensive documentation explaining how a codebase works, including architecture, key components, data flow, and development guidelines. Use when user wants to understand unfamiliar code, create onboarding docs, document architecture, or explain how the system works.

---

name: code-execution

description: Execute Python code locally with marketplace API access for 90%+ token savings on bulk operations. Activates when user requests bulk operations (10+ files), complex multi-step workflows, iterative processing, or mentions efficiency/performance.

---

name: code-refactor

description: Perform bulk code refactoring operations like renaming variables/functions across files, replacing patterns, and updating API calls. Use when users request renaming identifiers, replacing deprecated code patterns, updating method calls, or making consistent changes across multiple locations.

---

name: code-transfer

description: Transfer code between files with line-based precision. Use when users request copying code from one location to another, moving functions or classes between files, extracting code blocks, or inserting code at specific line numbers.

---

name: conversation-analyzer

description: Analyzes your Claude Code conversation history to identify patterns, common mistakes, and opportunities for workflow improvement. Use when user wants to understand usage patterns, optimize workflow, identify automation opportunities, or check if they're following best practices.

---

name: dashboard-creator

description: Create HTML dashboards with KPI metric cards, bar/pie/line charts, progress indicators, and data visualizations. Use when users request dashboards, metrics displays, KPI visualizations, data charts, or monitoring interfaces.

---

name: ensemble-solving

description: Generate multiple diverse solutions in parallel and select the best. Use for architecture decisions, code generation with multiple valid approaches, or creative tasks where exploring alternatives improves quality.

---

name: feature-planning

description: Break down feature requests into detailed, implementable plans with clear tasks. Use when user requests a new feature, enhancement, or complex change.

---

name: file-operations

description: Analyze files and get detailed metadata including size, line counts, modification times, and content statistics. Use when users request file information, statistics, or analysis without modifying files.