design-structure
Design directory structure from layer structure. Derives structure through iterative separation decisions. Use before code generation.
Découvrez les skills databases architecture patterns, comparez leurs dépôts et consultez leurs instructions.
Design directory structure from layer structure. Derives structure through iterative separation decisions. Use before code generation.
Derive layer structure from application requirements and propose changes if the current code structure differs. Use when designing architecture, reviewing code structure, or before generating application code.
Analyze domain models and infer entity relationships from naming conventions. Language-agnostic. Use when understanding data models, designing database schemas, or before generating API code.
Testing strategy, patterns, and best practices for unit, integration, and e2e tests
Go idioms, error handling, and API patterns
REST API design patterns for endpoints, responses, errors, and conventions
Security audit patterns for identifying vulnerabilities and security issues
Enforce a precise, minimal design system for Battery's dashboard UI. Use this skill when building admin interfaces, deployment management screens, or any dashboard components. Inspired by Linear, Notion, and St...
Phase 3 of feature development - Create domain events, external events, value objects, and aggregate changes for the Burraco system. Use after feature-design to implement the domain model.
Main workflow orchestrator for adding new features to the distributed Burraco card game system. Use this when implementing new game features across Game, Player, and Dealer services following CQRS, Event Sourci...
Phase 2 of feature development - Design architecture, events, commands, and service interactions for the Burraco distributed system. Use after running feature-discovery to create the technical design.
Phase 4 of feature development - Implement commands, REST handlers, Kafka consumers/producers in Kotlin for the Burraco distributed system. Use after domain-modeling to write the implementation code.
Use immediately when user mentions: "処理フロー", "processing flow", "フロー図", "flow diagram", "Mermaid", "アーキテクチャ", "architecture", "理解負債", "understanding debt", "なぜ", "why", "数式", "理論", "可...
Use immediately when user mentions: "Interface", "Protocol", "インターフェース", "プロトコル", "contract", "契約", "abstraction", "抽象化", "DI", "dependency injection", "Generic", "TypeVar". MUST USE this ski...
This skill should be used when implementing new features, understanding existing patterns, or when the user asks about "project-specific knowledge", "domain knowledge", "business logic", "data schema", "pipelin...
Design and architect microservices following Chris Richardson's Microservices Patterns. Use when designing services, APIs, data flows, or evaluating architecture decisions. Guides full workflow from feature int...
Audit backend services for security, reliability, performance, and operability issues. Use when reviewing APIs, microservices, workers, or backend code changes. Triggers on "audit backend", "security review", "...
Plan and implement microservices for Optima platform. Use when building new services, features, or integrations. Generates phased implementation roadmaps following Optima patterns - Database Gateway, append-onl...
Review architectural changes for coupling, blast radius, and long-term impact. Use when evaluating system design changes, cross-service dependencies, API changes, or infrastructure modifications. Triggers on "a...
OmO multi-agent orchestration skill. This skill should be used when the user invokes /omo or needs multi-agent coordination for complex tasks. Triggers on /omo command. Loads Sisyphus as the primary orchestrato...
comprehensive 12-step project development workflow from initialization through deployment. use when starting a new project, continuing project development, or user mentions project steps, architecture planning,...
Choose architecture, patterns, tech stack, trade-offs in MacroFlow.
Orchestrate MacroFlow as a flow network for dynamic AI orchestration.
Level 2 patterns - vulns, lic, sbom, doctor (security, compliance, environment health)
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.