发现 databases architecture patterns 相关 Skills，比较来源仓库和用途，查看适合你工作流的技能说明。
Code-centric Goal-Oriented Action Planning integrated with SPARC methodology. Use for feature implementation planning, performance optimization goals, testing strategy development, or any software development o...
Automated release coordination and deployment with swarm orchestration for seamless version management, testing, and deployment across multiple packages. Use for release pipelines, version coordination, deploym...
Implementation specialist for writing clean, efficient code following best practices and design patterns
SPARC Architecture phase specialist for system design, component architecture, interface design, scalability planning, and technology selection
Adaptive resource allocation, predictive scaling with ML, capacity planning, circuit breakers, and performance profiling. Use for intelligent resource management, auto-scaling, and fault tolerance.
Orchestrate complex software releases using AI swarms that handle everything from changelog generation to multi-platform deployment. Use for release planning, automated versioning, artifact building, progressiv...
Enforces TypeORM implementation patterns for this NestJS backend project. This skill should be used when creating or modifying TypeORM entities, repositories, database configuration, migrations, or any database...
Enforces atomic design methodology (atoms, molecules, organisms, templates, pages) for React Native/Expo projects using Gluestack UI. This skill should be used when creating new components, validating existing...
Procedural rules and patterns for NestJS backend development. This skill should be used when creating new NestJS modules, services, resolvers, or controllers. It covers component generation with NestJS CLI, TDD...
Research technical solutions, analyze architectures, gather requirements thoroughly. Use for technology evaluation, best practices research, solution design, scalability/security/maintainability analysis.
Plan implementations, design architectures, create technical roadmaps with detailed phases. Use for feature planning, system design, solution architecture, implementation strategy, phase documentation.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Enforces JU-DO-KON! architectural boundaries, module responsibilities, and design intent. Use when designing, refactoring, or reviewing core game logic.
Backend architecture agent for API design, database schema, and microservices
Automated deployment orchestration with rollback, blue-green, and canary deployment strategies
Migrate legacy code to modern frameworks, languages, and patterns with automated refactoring and testing
Guardrails to keep the pipeline pure: specs + SEA™ + generators only.
Manage knowledge work using CMMN (Case Management Model and Notation) primitives including Cases, Stages, Tasks, and Artifacts. Use for discretionary workflows, research projects, consulting engagements, creati...
Build CADSL-based cognitive artifacts for SEA-Forge™ including checklists, planners, decision trees, kanban boards, and mind maps. Use for generating interactive, semantically-anchored artifacts that support kn...
Author SEA-DSL specifications with proper CQRS annotations, validation, and namespace conventions. Use when creating .sea files with entities, flows, and policies that require @cqrs, @tx, @outbox, and @idempote...
Enforce Flow-only CQRS tagging and recommended metadata.
Composable patterns for advanced skill usage including skill chaining, telemetry instrumentation, visual cataloging, and skill versioning. Use when building complex multi-skill workflows, adding observability t...
Debug and troubleshoot SEA-Forge™ services using OpenTelemetry traces, metrics, and logs. Use for investigating performance issues, distributed tracing, log analysis, and production incident response. Integrate...
Author ADR, PRD, and SDS specifications following SEA™ templates with full traceability. Use when creating architecture decision records (ADRs), product requirement documents (PRDs), or software design specific...
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库，同一仓库的多个技能可能共享相同数值；它反映仓库关注度，不代表单个技能的安装量或质量评分。