Design

This skill should be used when the user asks to "analyze my product", "research competitors", "find feature gaps", "create feature request", "prioritize backlog", "generate PRD", "plan roadmap", "what should we build next", "competitive analysis", "gap analysis", "sync issues", or mentions product management workflows. Provides AI-native PM capabilities for startups with signal-based feature tracking, the WINNING prioritization filter, and GitHub Issues integration with deduplication.

Universal challenge tracker with flexible cadence, intelligent insights, and cross-challenge learning detection. Use when user wants to track any personal challenge - learning, habits, building, fitness, creative, or custom. Supports daily, weekly, or N-day check-ins with type-adaptive preferences, backlog, and context files.

Systematic approach for creating minimal-change, reversible implementation plans. Claude invokes this skill when transforming requirements/research into executable blueprints. Emphasizes simplicity, safety, and clear verification steps.

Arma Reforger Workbench workflow, testing guidelines, and debugging patterns

Interactive project initialization with git setup, workflows, hooks, and build configuration.Triggers: project setup, initialization, scaffold, bootstrap, new projectUse when: starting new projects or initializing repositories

Transform specifications into structured implementation plans with architecture design and task breakdown

Analyze and enhance Makefiles for complete user functionality coverage.Triggers: Makefile analysis, Makefile gaps, missing targets, plugin release,Makefile coverage, build targets, make dogfood, plugin qualityUse when: analyzing Makefile completeness before releasing plugins, identifyinggaps during plugin maintenance, scoring Makefiles against best practices,verifying Makefiles support standard developer workflowsDO NOT use when: writing initial Makefiles from scratch.DO NOT use when: debugging specific build target failures.DO NOT use when: creating custom non-standard build systems.Use this skill BEFORE releasing any plugin to verify Makefile coverage.

Master Python asyncio, concurrent programming, and async/await patternsfor high-performance applications.Triggers: asyncio, async/await, coroutines, concurrent programming, async API,I/O-bound, websockets, background tasks, semaphores, async context managersUse when: building async APIs, concurrent systems, I/O-bound applications,implementing rate limiting, async context managersDO NOT use when: CPU-bound optimization - use python-performance instead.DO NOT use when: testing async code - use python-testing async module.Consult this skill for async Python patterns and concurrency.

Use a Layered (N-Tier) architecture to separate presentation, domain logic, anddata access responsibilities within a system.Triggers: layered architecture, n-tier, separation of concerns, presentation layer,data access layer, service layer, traditional architecture, monolith structure,layer enforcement, dependency directionUse when: building traditional applications with clear boundaries, working withmoderate-sized teams, needing familiar and well-understood patterns, compliancerequirements demand clear separationDO NOT use when: selecting from multiple paradigms - use architecture-paradigms first.DO NOT use when: high scalability needs independent component scaling.DO NOT use when: teams need independent deployment cycles - use microservices.Consult this skill when implementing layered patterns or enforcing layer boundaries.

Decompose systems into a suite of small, independently deployable services alignedto specific business capabilities.Triggers: microservices, service decomposition, independent deployment, team autonomy,distributed system, API gateway, service mesh, bounded contexts, polyglot persistenceUse when: teams need high autonomy and independent releases, different capabilitieshave distinct scaling needs, strong DevOps/SRE maturity exists, polyglot tech stacks neededDO NOT use when: selecting from multiple paradigms - use architecture-paradigms first.DO NOT use when: small team with low organizational complexity.DO NOT use when: lack of DevOps maturity or limited platform engineering resources.DO NOT use when: strong transactional consistency required across operations.Consult this skill when designing or evolving microservices architectures.

Evaluate and improve Claude skill quality through auditing.Triggers: skill audit, quality review, compliance check, improvement suggestions,token usage analysis, skill evaluation, skill assessment, skill optimization,skill standards, skill metrics, skill performanceUse when: reviewing skill quality, preparing skills for production, auditingexisting skills, generating improvement recommendations, checking compliancewith standards, analyzing token efficiency, benchmarking skill performanceDO NOT use when: creating new skills from scratch - use modular-skills instead.DO NOT use when: writing prose for humans - use writing-clearly-and-concisely.DO NOT use when: need architectural design patterns - use modular-skills.Use this skill BEFORE shipping any skill to production. Check even if unsure.

Enforces "prove before claim" discipline - validation, testing, and evidencerequirements before declaring work complete.Triggers: completion, finished, done, working, should work, configured,ready to use, implemented, fixedUse when: claiming ANY work is complete, recommending solutions, statingsomething will work, finishing implementationsDO NOT use when: explicitly asking questions or requesting clarificationDO NOT use when: work is clearly in-progress and not claiming completionCRITICAL: This skill is MANDATORY before any completion claim. Violationsresult in wasted time and eroded trust.

Guide to effective Claude Code skill authoring using TDD methodology andpersuasion principles.Triggers: skill authoring, skill writing, new skill, TDD skills, skill creation,skill best practices, skill validation, skill deployment, skill complianceUse when: creating new skills from scratch, improving existing skills withlow compliance rates, learning skill authoring best practices, validatingskill quality before deployment, understanding what makes skills effectiveDO NOT use when: evaluating existing skills - use skills-eval instead.DO NOT use when: analyzing skill architecture - use modular-skills instead.DO NOT use when: writing general documentation for humans.YOU MUST write a failing test before writing any skill. This is the Iron Law.

Monitor and optimize CPU/GPU usage with load measurement and cost-effectivevalidation strategies.Triggers: CPU usage, GPU usage, performance, load monitoring, build performance,training, resource consumption, test suite, compilationUse when: session starts (auto-load with token-conservation), planning buildsor training that could pin CPUs/GPUs for >1 minute, retrying failed resource-heavy commandsDO NOT use when: simple operations with no resource impact.DO NOT use when: quick single-file operations.Use this skill BEFORE resource-intensive operations. Establish baselines proactively.

Foundational workflow for preparing and structuring detailed reviews(architecture, API, code quality).Triggers: review workflow, structured review, review scaffolding, evidence capture,review preparation, analysis framework, review templateUse when: starting any detailed review workflow, needing consistent structurefor capturing context and findings, ensuring comparable review outputsDO NOT use when: quick catchup without formal review - use catchup.DO NOT use when: diff-focused analysis - use diff-analysis.Use this skill at the BEGINNING of any detailed review for consistent structure.

Model system responsibilities across clients, servers, and optional peer-to-peernodes for traditional distributed applications.Triggers: client-server, web architecture, mobile backend, API design, thin client,thick client, peer-to-peer, P2P, offline-first, synchronizationUse when: traditional web/mobile applications with centralized services,clear separation between client and server responsibilities neededDO NOT use when: selecting from multiple paradigms - use architecture-paradigms first.DO NOT use when: peer-to-peer dominates - consider dedicated P2P patterns.Consult this skill when designing client-server systems or API architectures.

Update and maintain tests following TDD/BDD principles with detailedquality assurance.Triggers: test updates, test maintenance, test generation, TDD workflow,BDD patterns, test coverage, pytest, test enhancement, quality assuranceUse when: updating existing tests, generating new tests for features,enhancing test quality, ensuring detailed coverage, pre-commit validationDO NOT use when: auditing test suites - use pensive:test-review.DO NOT use when: writing production code - focus on implementation first.Run git-workspace-review first to understand which tests need updates.

Generic template patterns and lifecycle stages for knowledge storage,configuration management, and structured documentation.Triggers: storage templates, lifecycle stages, maturity progression, namingconventions, knowledge storage, configuration templates, documentation patternsUse when: organizing knowledge storage, managing configuration lifecycle,creating structured documentation, establishing naming conventionsDO NOT use when: simple storage without lifecycle or structure needs.Consult this skill when designing storage and documentation systems.

Declarative release readiness checklist that mirrors GitHub checks,deployment issues, and documentation requirements.Triggers: release gates, release readiness, deployment checklist, release review,quality signals, rollout scorecard, QA handshake, deployment gatesUse when: preparing releases, validating deployment gates, conducting releasereviews, embedding release gate snippets in PRsDO NOT use when: weekly status updates - use github-initiative-pulse.DO NOT use when: code reviews - use pensive review skills.Standardizes release approvals with GitHub-aware checklists.

Consolidates ephemeral LLM-generated markdown files into permanent documentation.Triggers: consolidate docs, untracked reports, ephemeral files, git cleanup,report consolidation, knowledge extraction, REPORT.md files, ANALYSIS.md filesUse when: you have untracked *_REPORT.md or *_ANALYSIS.md files, git statusshows markdown artifacts that shouldn't be committed, preparing PR and needto clean up working artifacts, preserving insights from code reviewsDO NOT use when: files are already in docs/ or skills/ locations.DO NOT use when: files are intentionally temporary scratch notes.DO NOT use when: source files have no extractable value.Merges valuable content into permanent documentation, then deletes source files.