golang-enterprise-patterns
Enterprise-level Go architecture patterns including clean architecture, hexagonal architecture, DDD, and production-ready application structure.
Découvrez les skills documentation architecture patterns, comparez leurs dépôts et consultez leurs instructions.
Enterprise-level Go architecture patterns including clean architecture, hexagonal architecture, DDD, and production-ready application structure.
Network architecture, troubleshooting, and infrastructure patterns. Use when designing network topologies, debugging connectivity issues, configuring load balancers, DNS, or implementing network security.
Plan and review architecture decisions via a structured interview and ADR output. Use when choosing between system design alternatives.
Patterns for designing PDAs: seed strategy, collision avoidance, upgrade considerations, and bump handling. Use when creating or auditing PDAs.
Generate an architecture specification from a PRD or tech spec. Use when architecture boundaries and diagrams must be defined before build.
Project-specific code patterns for Server Actions, data fetching, error handling, file organization. Use when implementing features to follow established patterns, or when user asks about project conventions/pa...
This skill should be used when the user asks to "review code", "check for anti-patterns", "audit my code", "find issues in code", "review this file", "check this component", or mentions code review, linting, or...
This skill should be used when the user asks to "analyze error handling", "review exception handling", "check error patterns", "audit error recovery", "review logging", "check error boundaries", or mentions err...
This skill should be used when the user asks to "analyze local-first patterns", "review offline support", "check sync implementation", "audit conflict resolution", "review optimistic updates", "check offline ca...
This skill should be used when the user asks to "analyze architecture", "review code structure", "check SOLID principles", "evaluate layering", "assess separation of concerns", "review module organization", or...
Go backend patterns including chi router, gRPC, pgx, context handling, and concurrency.
Incident response and remediation patterns including observability, diagnosis, and targeted fixes.
Supervisor, swarm, and hierarchical multi-agent architectures with context isolation patterns.
Test-driven development discipline - RED-GREEN-REFACTOR cycle with strict enforcement. Use when implementing any feature or bugfix, before writing implementation code.
CTO Platform lifecycle expertise - Play workflow orchestration, intake processing, MCP tools, and agent sequencing. Use when managing the full development lifecycle from PRD to deployed code.
Model UI updates as transactions to ensure consistency across complex interactions.
Design deterministic state machines that remain correct under concurrent rendering and re-entrancy.
Build collaborative surfaces using CRDTs or OT, synchronized with React's update model.
Model complex UI flows using finite state machines to ensure deterministic behavior.
Decouple business logic from UI using Inversion of Control with Context and Hooks.
Design UI graphs that remain resilient to partial failures and unstable dependencies.
Engineer hook ecosystems with composable, scalable abstractions that preserve correctness under concurrency.
Build mechanisms to debounce and deduplicate redundant data fetching requests.
Establish governance models for large React 18 codebases to preserve architectural integrity.
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é.