Design

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.

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.

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

Master Python asyncio, concurrent programming, and async/await patterns for high-performance applications. Triggers: asyncio, async/await, coroutines, concurrent programming, async API, I/O-bound, websockets, background tasks, semaphores, async context managers Use when: building async APIs, concurrent systems, I/O-bound applications, implementing rate limiting, async context managers DO 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, and data 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 direction Use when: building traditional applications with clear boundaries, working with moderate-sized teams, needing familiar and well-understood patterns, compliance requirements demand clear separation DO 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 aligned to specific business capabilities. Triggers: microservices, service decomposition, independent deployment, team autonomy, distributed system, API gateway, service mesh, bounded contexts, polyglot persistence Use when: teams need high autonomy and independent releases, different capabilities have distinct scaling needs, strong DevOps/SRE maturity exists, polyglot tech stacks needed DO 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 performance Use when: reviewing skill quality, preparing skills for production, auditing existing skills, generating improvement recommendations, checking compliance with standards, analyzing token efficiency, benchmarking skill performance DO 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 evidence requirements before declaring work complete. Triggers: completion, finished, done, working, should work, configured, ready to use, implemented, fixed Use when: claiming ANY work is complete, recommending solutions, stating something will work, finishing implementations DO NOT use when: explicitly asking questions or requesting clarification DO NOT use when: work is clearly in-progress and not claiming completion CRITICAL: This skill is MANDATORY before any completion claim. Violations result in wasted time and eroded trust.

Interactive project initialization with git setup, workflows, hooks, and build configuration. Triggers: project setup, initialization, scaffold, bootstrap, new project Use 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 quality Use when: analyzing Makefile completeness before releasing plugins, identifying gaps during plugin maintenance, scoring Makefiles against best practices, verifying Makefiles support standard developer workflows DO 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.

Monitor and optimize CPU/GPU usage with load measurement and cost-effective validation strategies. Triggers: CPU usage, GPU usage, performance, load monitoring, build performance, training, resource consumption, test suite, compilation Use when: session starts (auto-load with token-conservation), planning builds or training that could pin CPUs/GPUs for >1 minute, retrying failed resource-heavy commands DO 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 template Use when: starting any detailed review workflow, needing consistent structure for capturing context and findings, ensuring comparable review outputs DO 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-peer nodes for traditional distributed applications. Triggers: client-server, web architecture, mobile backend, API design, thin client, thick client, peer-to-peer, P2P, offline-first, synchronization Use when: traditional web/mobile applications with centralized services, clear separation between client and server responsibilities needed DO 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.

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 gates Use when: preparing releases, validating deployment gates, conducting release reviews, embedding release gate snippets in PRs DO 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.

Update and maintain tests following TDD/BDD principles with detailed quality assurance. Triggers: test updates, test maintenance, test generation, TDD workflow, BDD patterns, test coverage, pytest, test enhancement, quality assurance Use when: updating existing tests, generating new tests for features, enhancing test quality, ensuring detailed coverage, pre-commit validation DO 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, naming conventions, knowledge storage, configuration templates, documentation patterns Use when: organizing knowledge storage, managing configuration lifecycle, creating structured documentation, establishing naming conventions DO NOT use when: simple storage without lifecycle or structure needs. Consult this skill when designing storage and documentation systems.

Design, manage, and evolve digital gardens as living knowledge bases within memory palaces. Triggers: digital garden, knowledge base, linking, note curation, content lifecycle, garden maintenance, bidirectional links, knowledge evolution Use when: managing note collections, creating link structures, maintaining knowledge bases, tending garden health and growth DO NOT use when: creating memory palace structures - use memory-palace-architect. DO NOT use when: evaluating new knowledge - use knowledge-intake. Consult this skill when cultivating and maintaining digital gardens.

Guide to formatting review deliverables for consistency, ensuring findings are comparable across different types of analysis. Triggers: report formatting, deliverable structure, consistent output, review output, findings format, report template, output consistency Use when: formatting final review outputs, ensuring consistent deliverable structure, making findings comparable across reviews DO NOT use when: capturing evidence during analysis - use evidence-logging. DO NOT use when: reviewing changes - use diff-analysis or review-core first. Consult this skill when formatting final review deliverables.