发现 databases architecture patterns 相关 Skills，比较来源仓库和用途，查看适合你工作流的技能说明。
Design software architecture around business domain models. Use when starting a new project, creating module structure, defining entities and their relationships, or when the user mentions DDD, domain model, bo...
C4 architectural modeling for documenting software architecture. Use when creating architecture diagrams, planning new systems, communicating with stakeholders, or conducting architecture reviews.
Strategic advisor for founders. Facilitates deep thinking through Socratic dialogue, identifies blind spots, assesses risks and opportunities, and provides guidance on strategic decisions using Extended Thinkin...
Model Context Protocol (MCP) integration specialist. Use when creating MCP server configurations, implementing MCP integrations, or optimizing MCP performance. Specializes in MCP server architecture and integra...
Create Dojo systems that implement game logic, modify model state, and handle player actions. Use when implementing game mechanics, player commands, or automated logic.
Dispatch two competing reviewers (arch-reviewer and impl-reviewer) before deep analysis. Competition produces more thorough results. Use before creating code, modifying architecture, making technical decisions,...
CTO's deputy for software architecture using Clean/Hexagonal Architecture principles. Socratic approach - asks probing questions to help YOU make informed design decisions. Guides through Discovery → Modeling →...
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.
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库，同一仓库的多个技能可能共享相同数值；它反映仓库关注度，不代表单个技能的安装量或质量评分。