orchestrate
End-to-end project orchestration from idea to implementation. Use when user wants to build a complete project, implement an MVP, or says "build this app/feature". Coordinates product-design, architecture, task-...
Découvrez les skills devops architecture patterns, comparez leurs dépôts et consultez leurs instructions.
End-to-end project orchestration from idea to implementation. Use when user wants to build a complete project, implement an MVP, or says "build this app/feature". Coordinates product-design, architecture, task-...
Break down PRD and Architecture into implementable engineering tasks. Use when user wants to create a task list, plan implementation work, decompose features into stories and tasks, or needs to translate requir...
Ensure code follows DDD architecture and DAL separation principles. Triggers: DDD, arch, 架構, 新功能, 新模組, new feature, scaffold, 骨架, domain.
Proactively detect and execute code refactoring to maintain DDD architecture and code quality. Triggers: RF, refactor, 重構, 拆分, split, 模組化, modularize, 太長, cleanup.
Principal Engineer focused on maintainability, SOLID principles, and clean code.
Design systems for change. Trade-off analysis, ADR documentation, pattern selection. Architecture decisions must have documented rationale.
Professional skepticism with pattern enforcement. Verify before agreeing, challenge violations, propose instead of asking. Concise output, research before asking, answer questions literally.
Add retry, timeout, and circuit breaker patterns at the workflow level. Business functions stay clean.
Software design beyond syntax. Fail-fast over fallbacks, explicit over implicit, composition over inheritance. Integrates with fn(args, deps) and Result type patterns. Includes 8-dimension design analysis.
Never throw for expected failures. Use Result types with explicit error handling and workflow composition.
Enforce the fn(args, deps) pattern: functions over classes with explicit dependency injection
Design system principles for distinctive, implementation-ready interfaces. Context before design, show don't tell, every state documented.
Use when facing 2+ independent tasks that can be worked on without shared state. Dispatch one agent per problem domain for concurrent investigation.
Create multi-step workflow skills with progressive step loading, state management, and interactive decisions. Use when building complex skills like APEX that need structured phases.
Apply when improving code structure without changing behavior: reducing duplication, simplifying complexity, or improving readability.
Apply when containerizing applications: writing Dockerfiles, docker-compose configurations, and multi-stage builds.
Apply when implementing real-time features: live updates, presence, broadcast messages, or database change subscriptions.
Reduce cognitive complexity of functions while preserving behavior
Systematically diagnose errors and produce durable fixes
Refactor code applying KISS, DRY, SOLID, and YAGNI principles
Detects and captures technical decisions during conversations. Use when architectural choices, library selections, design patterns, API designs, or trade-off decisions are made. Automatically prompts user to sa...
Provides Next.js project architecture expertise and implementation patterns. Enforces BFF (Backend for Frontend) pattern, Server Components strategy, and data fetching policies. Specializes in App Router archit...
Provides NestJS framework development standards and architectural patterns. Ensures domain-centric architecture, proper dependency injection, and decorator pattern utilization. Specializes in modular design, pr...
Applies system architecture and design frameworks for software systems. Provides discovery protocols, system design workflows, architecture decision records (ADRs), and quality evaluation criteria. PROACTIVELY...
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é.