Skip to main content
ClaudeWave

Claude Code Skills · page 105

Individual Claude Code skills mined from every repository in the directory: each SKILL.md, installable with one command, with its full definition and the repository's trust signals.

15,309 skills1-command install
  1. Wave methodology knowledge for the buddy agent — what each wave does, its inputs and outputs, and how to route questions.

  2. nWave concierge — ask any question about methodology, project state, commands, migration, or troubleshooting. Read-only, contextual answers.

  3. Bug fix workflow: root cause analysis → user review → regression test + fix via TDD

  4. Canary skill for auto-injection detection

  5. CI/CD pipeline design methodology, deployment strategies, GitHub Actions patterns, and branch/release strategies. Load when designing pipelines or deployment workflows.

  6. Cross-agent collaboration protocols, workflow handoff patterns, and commit message formats for TDD/Mikado/refactoring workflows

  7. Documentation collapse anti-patterns - detection rules, bad examples, and remediation strategies for type-mixing violations

  8. Best practices for command definition files - size targets, declarative template, anti-patterns, and canonical examples based on research evidence

  9. Step-by-step workflow for converting bloated command files to lean declarative definitions

  10. Detects current wave progress for a feature and resumes at the next step. Scans docs/feature/ for artifacts.

  11. Crafter discipline contract for the ATDD-pure 7-phase workflow — what the slim crafter does in Phase A (GREEN-the-ATs), Phase B (coverage-driven dead-code elimination), and Phase E (batch L1-L6 refactor), plus hard prohibitions and the Phase B common-cuts taxonomy

  12. Data architecture patterns (warehouse, lake, lakehouse, mesh), ETL/ELT pipelines, streaming architectures, scaling strategies, and schema design patterns

  13. Database comparison catalogs, RDBMS vs NoSQL selection criteria, CAP/ACID/BASE theory, OLTP vs OLAP, and technology-specific characteristics

  14. Event Modeling facilitation technique — brainstorm events, identify commands and views, define aggregate boundaries, write Given-When-Then specifications

  15. Event Sourcing and CQRS as DDD implementation patterns — when to use, aggregate event streams, projections, snapshots, sagas, upcasting, conflict resolution

  16. Strategic DDD — bounded context discovery, context mapping patterns, subdomain classification, ubiquitous language, and organizational alignment

  17. Tactical DDD — aggregate design rules, entities, value objects, domain events, repositories, domain services, and anti-pattern detection

  18. DELIVER wave orchestration workflow -- 9 phases from baseline to finalization. Load when user invokes *deliver command. Covers state tracking, smart skip logic, retry, resume, and quality gate enforcement.

  19. Orchestrates the full DELIVER wave end-to-end (roadmap > execute-all > finalize). Use when all prior waves are complete and the feature is ready for implementation.

  20. Shared density-resolution contract for wave skills. Canonical detail on the D12 cascade, density resolver call, ad-hoc override workflow, and DocumentationDensityEvent telemetry emission. Referenced from nw-discover / nw-discuss / nw-design / nw-devops / nw-distill / nw-deliver.

  21. Rollback procedures, risk assessment, pre/post-deployment validation, and contingency planning. Load when orchestrating deployment or preparing rollback plans. For deployment strategy details (canary, blue-green, rolling), see `cicd-and-deployment` skill.

  22. Evaluation criteria and scoring for data engineering artifact reviews

  23. Apple LeanUX++ design workflow, journey schema, emotional arc patterns, and CLI UX patterns. Load when transitioning from discovery to visualization or when designing journey artifacts.

  24. 7 agentic design patterns with decision tree for choosing the right pattern for each agent type

  25. Designs system architecture with C4 diagrams and technology selection. Routes to the right architect based on design scope (system, domain, application, or full stack). Two interaction modes: guide (collaborative Q&A) or propose (architect presents options with trade-offs).

  26. Designs CI/CD pipelines, infrastructure, observability, and deployment strategy. Use when preparing platform readiness for a feature.

  27. Generates C4 architecture diagrams (context, container, component) in Mermaid or PlantUML. Use when creating or updating architecture visualizations.

  28. Conducts evidence-based product discovery through customer interviews and assumption testing. Use at project start to validate problem-solution fit.

  29. Question-first approach to understanding user journeys. Load when starting a new journey design or when the discovery phase needs deepening.

  30. 4-phase discovery workflow with decision gates, phase transitions, success metrics, and state tracking

  31. Conducts Jobs-to-be-Done analysis, UX journey design, and requirements gathering through interactive discovery. Use when starting feature analysis, defining user stories, or creating acceptance criteria.

  32. Acceptance test creation methodology for the DISTILL wave. Domain knowledge for the acceptance designer agent: port-to-port principle, prior wave reading, wave-decision reconciliation, graceful degradation, and document back-propagation.

  33. Generates 3-5 divergent design directions through JTBD analysis, competitive research, structured brainstorming, and taste evaluation before convergence. Use when the team has a validated problem but hasn't chosen a solution approach.

  34. Review criteria for the nw-diverger-reviewer — validates JTBD rigor, research quality, option diversity, taste application correctness, and recommendation coherence in DIVERGE wave artifacts

  35. DIVIO/Diataxis four-quadrant documentation framework - type definitions, classification decision tree, and signal catalog

  36. Creates evidence-based documentation following DIVIO/Diataxis principles. Use when writing tutorials, how-to guides, reference docs, or explanations.

  37. Strategic and tactical DDD patterns, bounded context discovery, context mapping, aggregate design rules, and decision frameworks for when to apply DDD

  38. Definition of Ready checklist criteria, antipattern detection patterns, UAT quality rules, and domain language enforcement for product owner review

  39. Critique dimensions, severity framework, verdict decision matrix, and review output format for documentation assessment reviews

  40. Use when a DELIVER roadmap already exists and you need to dispatch exactly one identified step through its TDD cycle. Use nw-roadmap to create the plan, nw-deliver for the whole wave, and nw-continue to resume at the next inferred step.

  41. Fast-forwards through remaining waves end-to-end without stopping for review between waves.

  42. Archives a completed feature to docs/evolution/, migrates lasting artifacts to permanent directories, and cleans up the temporary workspace. Use after all implementation steps pass and mutation testing completes.

  43. Toyota 5 Whys methodology with multi-causal branching, evidence requirements, and validation techniques

  44. Creates new specialized agents using the 5-phase workflow (ANALYZE > DESIGN > CREATE > VALIDATE > REFINE). Use when building a new AI agent or validating an existing agent specification.

  45. TLA+ and PlusCal for specifying distributed system invariants. Decision heuristics for when formal verification adds value, key patterns, state explosion management, and alternatives comparison.

  46. Algebra-driven API design with monoids, semigroups, and interpreters via algebraic equations

  47. Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec

  48. Domain modeling with algebraic data types, smart constructors, and type-level error handling

  49. F# language-specific patterns, Railway-Oriented Programming, and Computation Expressions

  50. Haskell language-specific patterns, GADTs, type classes, and effect systems

  51. Hexagonal architecture patterns with pure core and side-effect shell for functional codebases

  52. Kotlin language-specific patterns with Arrow, Raise DSL, and coroutine-based effects

  53. Core functional programming thinking patterns and type system foundations, language-agnostic

  54. Scala 3 language-specific patterns with ZIO, Cats Effect, and opaque types

  55. Naming conventions, API ergonomics, and usability patterns for functional code

  56. 5-layer agent output validation, I/O contract specification, vertical slice development, and test doubles policy with per-layer examples

  57. Git change frequency hotspot analysis — find the most-changed files in your codebase

  58. Infrastructure as Code patterns (Terraform, Kubernetes), observability design (SLOs, metrics, alerting, dashboards), and pipeline security stages. Load when designing infrastructure, observability, or security scanning.

  59. Mom Test questioning toolkit, JTBD analysis, interview conduct, assumption testing framework, and hypothesis design

  60. Evidence collection methods, problem categorization, analysis techniques, and solution design patterns

  61. JTBD methodology for extracting real jobs behind feature requests — job statements, abstraction layers, first-principles extraction, ODI outcome statements, and opportunity scoring

  62. Translating JTBD analysis to BDD scenarios - job story to Given-When-Then patterns, forces-based test discovery, job-map-based test discovery, and property-shaped criteria

  63. Core JTBD theory and job story format - job dimensions, job story template, job stories vs user stories, 8-step universal job map, outcome statements, and forces of progress

  64. JTBD discovery techniques adapted for AI product owner context. Four Forces extraction, job dimension probing, question banks, and anti-patterns for interactive feature discovery conversations.

  65. JTBD opportunity scoring and prioritization - outcome statement format, opportunity algorithm, scoring interpretation, feature prioritization, and opportunity matrix template

  66. JTBD workflow classification and routing - ODI two-phase framework, five job types with workflow sequences, baseline type selection, workflow anti-patterns, and common recipes

  67. Add a new model to an existing provider

  68. Review a provider implementation for correctness and consistency with other providers

  69. >

  70. >

  71. >

  72. >

  73. Build and review Remix 3 applications using the `remix` npm package and

  74. >

  75. How to run and test kody's multi-worker local dev (origin kody worker +

  76. Generate and maintain the system recap block in a PR description - a

  77. Draw.io 配图专家:用于生成和导出 `.drawio` 图表。在用户要求 draw.io、diagrams.net、流程图、架构图、时序图、ER 图、状态图、思维导图,或明确提到 `.drawio`、PNG、SVG、PDF 导出、技术文章配图时使用。默认输出专业技术风格,并遵循 floracat-architecture-diagram 的视觉规范。

  78. |

  79. |

  80. Use when bumping the Wayland version: update package.json, run checks, branch, commit, push, create PR, wait for merge, tag release.

  81. |

  82. |

  83. i18n604

    |

  84. Use when creating a pull request, after committing changes, or when user invokes /oss-pr. Covers branch management, quality checks, commit, push, and PR creation.

  85. |

  86. |

  87. |

  88. |

  89. |

  90. |

  91. Generate review + photo + video prompts at the right post-delivery moment by product type. Inputs: product type (consumable / durable / cosmetic / apparel), platform. Output: prompt-timing recommendation (D+3 / D+7 / D+14 by category), template copy, incentive structure (compliant with platform anti-incentive rules), photo-prompt CTA. Trigger phrases: 'review prompt', 'UGC prompt', 'ask for a photo review', 'request video testimonial', '/commerce ugc-prompts <product-type>'.

  92. |

  93. |

  94. |

  95. |

  96. |

  97. |

  98. |

  99. |