Claude Skills

Systematic task execution with checkpoint validation, progress tracking, and quality gates

Triggers: writing style, voice, tone, style guide, exemplar, style learning Learn and extract writing style patterns from exemplar text for consistent application. Triggers: learn style, extract style, style profile, writing voice, tone analysis, style guide generation, exemplar analysis Use when: creating a style guide from existing content, ensuring consistency across documents, learning a specific author's voice, customizing AI output style DO NOT use when: detecting AI slop - use slop-detector instead. DO NOT use when: just need to clean up existing content - use doc-generator with --remediate. Use this skill to build style profiles from exemplar text.

Triggers: refine, code quality, clean code, refactor, duplication, algorithm efficiency, complexity reduction, code smell, anti-slop, craft Analyze and improve living code quality: duplication, algorithmic efficiency, clean code principles, architectural fit, anti-slop patterns, and error handling robustness. Use when: improving code quality, reducing AI slop, refactoring for clarity, optimizing algorithms, applying clean code principles DO NOT use when: removing dead/unused code (use conserve:bloat-detector). DO NOT use when: reviewing for bugs (use pensive:bug-review). DO NOT use when: selecting architecture paradigms (use archetypes skills). This skill actively improves living code, complementing bloat detection (dead code removal) with quality refinement (living code improvement).

Evaluate and improve Claude skill quality through auditing. Triggers: quality-assurance, skills, optimization, tool-use, performance-metrics, skill audit, quality review, compliance check, improvement suggestions, token usage analysis, skill evaluation, skill assessment, skill optimization, skill standards, skill metrics, skill performance. Use when reviewing skill quality, preparing skills for production, or auditing existing skills. Do not use when creating new skills (use modular-skills) or writing prose (use writing-clearly-and-concisely). Use this skill before shipping any skill to production.

Socratic questioning and ideation methodology for project conception using structured brainstorming frameworks

Inline reversibility assessment for embedded War Room escalation from other commands

Configure GitHub Actions workflows for CI/CD (test, lint, typecheck, publish)

Interactive selector and router for architecture paradigms. Triggers: architecture selection, pattern comparison, system design, ADR creation, architecture decision, paradigm evaluation, new system architecture, architecture planning, which architecture, compare architectures Use when: selecting architecture patterns for new systems, comparing paradigm trade-offs, creating architecture decision records, evaluating architecture fit for team size and domain complexity, planning implementation roadmaps DO NOT use when: implementing a specific known paradigm - use the specific architecture-paradigm-* skill (hexagonal, layered, microservices, etc.) instead. DO NOT use when: reviewing existing architecture - use architecture-review instead. Use this skill BEFORE making architecture decisions. Check even if unsure about needs.

Triggers: source, cite, reference, factual claim, verify, attribution Intelligent sourcing that requires citations only for high-value factual claims, balancing accuracy with token efficiency.

Triggers: safety, critical, NASA, power of 10, defensive coding, assertions, bounds checking Guidelines from NASA's Power of 10 rules for writing robust, verifiable code. Adapted for general software development with context-appropriate rigor. Use when: Writing critical code paths, reviewing for robustness, improving code quality DO NOT use: As rigid requirements for all code - match rigor to consequence

Detect and flag AI-generated content markers in documentation and prose. Triggers: ai slop, ai-generated, llm markers, chatgpt phrases, claude tells, slop detection, ai cleanup, humanize text, remove ai markers, detect chatgpt, detect llm, writing quality, ai tells. Use when reviewing documentation for AI markers, cleaning up LLM-generated content, or auditing prose quality. Do not use when generating new content (use doc-generator) or learning writing styles (use style-learner).

Delegate tasks to external LLM services (Gemini, Qwen) with quota, logging, and error handling.

Implements features and writes code based on Plans.md tasks. Use when user mentions implementation, adding features, writing code, or creating new functions. Do not use for review or build verification.

Manages workflow transitions including handoffs between PM and implementation roles, and auto-fixes review comments. Use when user mentions handoffs, reporting to PM, handing off to implementation, completion reports, or auto-fix. Do not use for 2-Agent setup—use 2agent skill instead.

Sets up deployment, analytics, and health monitoring for projects. Use when user mentions deployment, Vercel, Netlify, analytics, or health checks. Do NOT load for: implementation work, local development, reviews, or setup.

Controls session resume/fork for /work based on flags. Use only from workflow.

Research Hex packages (Sobelow, Phoenix, Ecto, Credo, Ash, etc). Use when investigating packages, understanding integration patterns, or finding module/function docs and usage examples. Automatically fetches missing documentation and source code locally.

Integrates OpenAI Codex CLI as an MCP server to provide second-opinion reviews. Triggered by requests for Codex review, second opinion, or Codex setup. Do NOT load for: standard reviews without Codex, implementation work, or non-setup tasks.