1,669 skills found · Page 49 of 56
nWave-ai / nw-density-resolution-contractShared 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.
nWave-ai / nw-discovery-methodologyQuestion-first approach to understanding user journeys. Load when starting a new journey design or when the discovery phase needs deepening.
nWave-ai / nw-fast-forwardFast-forwards through remaining waves end-to-end without stopping for review between waves.
nWave-ai / nw-data-architecture-patternsData architecture patterns (warehouse, lake, lakehouse, mesh), ETL/ELT pipelines, streaming architectures, scaling strategies, and schema design patterns
nWave-ai / nw-ddd-tacticalTactical DDD — aggregate design rules, entities, value objects, domain events, repositories, domain services, and anti-pattern detection
nWave-ai / nw-diagramGenerates C4 architecture diagrams (context, container, component) in Mermaid or PlantUML
nWave-ai / nw-distillAcceptance 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.
nWave-ai / nw-domain-driven-designStrategic and tactical DDD patterns, bounded context discovery, context mapping, aggregate design rules, and decision frameworks for when to apply DDD
nWave-ai / nw-legacy-refactoring-dddDDD-guided legacy refactoring patterns -- strangler fig, bubble context, ACL migration, 14 tactical/strategic/infrastructure patterns, and incremental monolith-to-microservices methodology
nWave-ai / nw-sd-case-studies25 real-world system design case studies condensed from Alex Xu's System Design Interview Vol 1 and 2 - requirements, architecture, deep dive insights, key takeaways
nWave-ai / nw-spike-methodologyTeaches agents how to run a timeboxed spike - throwaway code that validates one assumption before DESIGN
nWave-ai / nw-ux-principlesCore UX principles for product owners. Load when evaluating interface designs, writing acceptance criteria with UX requirements, or reviewing wireframes and mockups.
nWave-ai / nw-design-patterns7 agentic design patterns with decision tree for choosing the right pattern for each agent type
nWave-ai / nw-interviewing-techniquesMom Test questioning toolkit, JTBD analysis, interview conduct, assumption testing framework, and hypothesis design
nWave-ai / nw-sd-framework4-step system design framework with back-of-envelope estimation, scaling ladder, and common pitfalls
anombyte93 / execute-taskExecute the next TaskMaster task using the implementation plan with CDD verification. Picks the next ready task, matches it to the plan step, implements via a dispatched subagent, verifies subtasks with evidence, marks the task done, and loops until every task is complete.
superdesigndev / superdesignDesign or redesign frontend UI, presentations, and graphics on the Superdesign canvas with a choice of leading AI models
howseen-ai / motion-designCode-only motion design pipeline (no After Effects) for Raphaël / Howseen: launch films, showreels, product promos, LinkedIn/X videos, meme clips
oliver-kriska / analyzeAnalyze a legacy app in any language before rewriting it in Elixir: inventory, features as goals, why each mechanism exists, runtime topology, external contracts. Use to start or refresh a rewrite.
oliver-kriska / architectDesign the idiomatic Elixir architecture for a rewrite: set the compatibility bar (ADR-000), consult phx specialists on open questions, then build contexts, ledger and ADRs. Use after /rewrite:analyze.
oliver-kriska / planPlan features spanning multiple domains: billing (Stripe), auth (RBAC), real-time (Presence), webhooks, jobs (Oban)
oliver-kriska / briefInteractive briefing of a plan file — explains reasoning, schema decisions, component choices
oliver-kriska / elixir-idiomsOTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes
oliver-kriska / phx-briefInteractive briefing of a plan file — explains reasoning, schema decisions,
oliver-kriska / phoenix-contextsPhoenix context design — creating/splitting contexts, Scope (1.8+), Ecto.Multi, PubSub, routers, plugs, controllers
oliver-kriska / phx-document'Use when asked to document Elixir code: add or fill in @moduledoc and
oliver-kriska / phx-plan'Plan features spanning multiple domains: billing (Stripe), auth (RBAC),
oliver-kriska / challengeChallenge mode reviews - rigorous questioning before approving changes
oliver-kriska / phx-challengeChallenge mode reviews - rigorous questioning before approving changes.
levnikolaevich / ln-46-quality-gate-engineerConfigures and verifies lint, type, architecture and other engineering checks; not product cleanup, policy invention or deployment redesign.
