Claude Skills

Implements authentication and payment features using Clerk, Supabase Auth, or Stripe. Use when user mentions login, authentication, payments, subscriptions, or Stripe. Do NOT load for: general UI work, database design, or non-auth features.

Accesses the claude-mem MCP server from Cursor to search session history and record observations. Triggers: memory search, claude-mem, past decisions, record this. Do NOT load for: normal coding, temporary notes, or implementation work.

Migrate Agentic QE projects from v2 to v3 with zero data loss

Triggers: workflow error, inefficient execution, workflow failure, execution monitor Monitor workflow executions for errors and inefficiencies. When issues are detected, automatically create GitHub issues for workflow improvements via /fix-workflow. Use when: workflows fail, timeout, or show inefficient patterns DO NOT use when: normal workflow execution, simple command errors

Generate language-specific Makefile with common development targets

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

Guide to effective Claude Code skill authoring using TDD methodology and persuasion principles. Triggers: skills, validation, skill, authoring, tdd, skill authoring, skill writing, new skill, TDD skills, skill creation, skill best practices, skill validation, skill deployment, skill compliance. Use when creating new skills, improving compliance, or validating quality before deployment. Do not use for evaluating existing skills (use skills-eval) or analyzing architecture (use modular-skills). Follow the Iron Law: write a failing test before writing any skill.

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

Triggers: KISS, YAGNI, SOLID, clean code, code quality, refactor, design principles Provides guidance on fundamental software design principles to reduce complexity, prevent over-engineering, and improve maintainability.

Detect codebase bloat through progressive analysis: dead code, duplication, complexity, documentation bloat. Triggers: bloat detection, dead code, code cleanup, duplication, technical debt, unused code Use when: context usage high, quarterly maintenance, pre-release cleanup, before refactoring DO NOT use when: active feature development, time-sensitive bugs, codebase < 1000 lines

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.

Enforces "prove before claim" discipline - validation, testing, and evidence requirements before declaring work complete. Triggers: validation, definition-of-done, proof, acceptance-criteria, testing, completion, finished, done, working, should work, configured, ready to use, implemented, fixed, improvement validated, workflow optimized, performance improved, issue resolved. Use when claiming work is complete, recommending solutions, or finishing implementations. Do not use when asking questions or for work clearly in-progress. MANDATORY: This skill is required before any completion claim.

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

TDD-style testing methodology for skills using fresh subagent instances to prevent priming bias and validate skill effectiveness. Triggers: test skill, validate skill, skill testing, subagent testing, fresh instance testing, TDD for skills, skill validation Use when: validating skill improvements, testing skill effectiveness, preventing priming bias, measuring skill impact on behavior DO NOT use when: implementing skills (use skill-authoring instead), creating hooks (use hook-authoring instead)

Triggers: verbose, bloat, concise, compress, direct, efficient response Eliminates response bloat including emojis, filler words, hedging language, hype, and unnecessary framing. Includes termination and directness guidelines.

Configure comprehensive three-layer pre-commit quality system with linting, type checking, and testing enforcement

Surfaces expert frameworks and proven methodologies before creating OR evaluating skills, hooks, agents, or commands. Helps select approaches from domain masters. Triggers: methodology, framework, expert approach, best practices, masters, proven method, domain expertise, how should I approach, what's the best way, evaluate skill, review methodology, is this grounded, optimization check. Use when starting creation workflows, evaluating methodology gaps, or seeking domain expertise. Do not use if you already have a specific methodology or are fixing syntax/structural issues.

Automatic context management with graceful handoff to continuation subagent. Triggers: context pressure, 80% threshold, auto-clear, context full, continuation, session state, checkpoint Use when: Context usage approaches 80% during long-running tasks. This skill enables automatic continuation without manual /clear. The key insight: Subagents have fresh context windows. By delegating remaining work to a continuation subagent, we achieve effective "auto-clear" without stopping the workflow.

Multi-LLM deliberation framework for strategic decisions through pressure-based expert consultation

Transform project brief into detailed, testable specifications using spec-driven development methodology

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

Systematic methodology to reduce skill file size through externalization, consolidation, and progressive loading patterns. Triggers: large skill, skill optimization, skill size, 300 lines, inline code, skill refactoring, skill context reduction, skill modularization Use when: skills exceed 300 lines, multiple code blocks (10+) with similar functionality, heavy Python inline with markdown, functions >20 lines embedded DO NOT use when: skill is under 300 lines and well-organized. DO NOT use when: creating new skills - use modular-skills instead. Consult this skill when skills-eval shows "Large skill file" warnings.

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.

Architect skills as modular blocks to control token usage and complexity. Triggers: skills, architecture, modular, design-patterns, modularity, skill design, skill architecture, modularization, token optimization, skill structure, refactoring skills, new skill creation, skill complexity. Use when creating skills >150 lines, breaking down monolithic skills, or planning new architecture. Do not use for evaluating existing skills (use skills-eval) or writing human-facing prose (use writing-clearly-and-concisely). Check this skill before starting any new skill development.