dev-execution
Unified execution engine for all development workflows. Progressive disclosure for phase execution, quick features, story completion, and scaffolding. Integrates with artifact-tracking and meatycapture-capture....
发现 databases architecture patterns 相关 Skills,比较来源仓库和用途,查看适合你工作流的技能说明。
Unified execution engine for all development workflows. Progressive disclosure for phase execution, quick features, story completion, and scaffolding. Integrates with artifact-tracking and meatycapture-capture....
High-velocity, intent-driven development using agentic workflows and MCP servers.
Implement features following Domain-Driven Design (DDD) and CQRS patterns with event-driven architecture, Kafka, and BullMQ
Review architecture decisions and code changes against documented architecture principles. Use this skill before implementing new features or refactoring existing code to ensure compliance with layer boundaries...
Distributed systems patterns for BEAM/OTP including clustering, supervision, and multi-region deployment
API versioning strategies including URL-based, header-based, and breaking change management
Resilience and error recovery patterns including circuit breaker, retry strategies, and graceful degradation
Elixir-specific security patterns, OWASP mitigations, and compliance best practices
Single Responsibility Code in Self-Documented Folder Structure
Implements OTP design patterns including GenServer, Supervisor, and Application behaviors.
Enforce SOLID design principles during code generation, refactors, and code review (SRP/OCP/LSP/ISP/DIP). Use when changing architecture, introducing new abstractions, reducing coupling, eliminating type-switch...
Recall and reuse prior decisions, constraints, and artifacts using MCP memory (e.g., Neo4j). Use when the user references past work (“jak ostatnio”, “kontynuuj”), when resuming a project thread, or when a repea...
Use Neo4j memory MCP for creating/updating linked memories (entities, relations), de-duplication (DRY), and retrieval queries for project continuity. Use when saving global learnings or querying graph relations...
Full-stack development context for coordinating changes across contracts and frontend. Use this skill when changes span both backend contracts and frontend code, requiring synchronized updates across the stack.
Enterprise-level rules for Melos/Mason project structure (Core, Common, Package)
Infrastructure and deployment standards for Dutch government systems. Use when deploying to Haven (government Kubernetes), setting up FSC (Federated Service Connectivity), or checking infrastructure compliance.
NeRDS software development guidelines for Dutch government projects. Use when making architectural decisions, setting up CI/CD, implementing security practices, handling privacy requirements, or ensuring access...
Expert in building distributed systems using Dapr. Use this for implementing pub/sub, state management, jobs, and secrets abstraction.
Expert in the Spec-Kit Plus lifecycle (Specify -> Plan -> Tasks -> Implement). Use this when the user needs to define new features, plan architecture, or decompose work into atomic units.
Expert in event-driven architecture using Kafka. Use this for designing topics, schemas, and processing logic for asynchronous tasks.
Opinionated UI constraints and patterns for building better interfaces. Focuses on accessibility, usability, and implementation best practices.
Error handling patterns for this project. Uses neverthrow for new code, custom Result type for legacy. Includes retry logic, parallel execution, and circuit breaker integration. Triggers on "error handling", "R...
Cost control patterns preventing bankruptcy in this indie SaaS. Hard $1/run limit, service-specific cost calculation, graceful degradation. Triggers on "cost", "budget", "api calls", "cost tracking", "spending...
Opossum circuit breaker patterns for resilience. Singleton pattern per service, timeout from env, event listeners. Triggers on "circuit breaker", "resilience", "external api", "failure handling", "opossum".
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库,同一仓库的多个技能可能共享相同数值;它反映仓库关注度,不代表单个技能的安装量或质量评分。