game-development
Game development orchestrator. Routes to platform-specific skills based on project needs.
Découvrez les skills databases architecture patterns, comparez leurs dépôts et consultez leurs instructions.
Game development orchestrator. Routes to platform-specific skills based on project needs.
Orchestrate concurrent agents through brownfield modernization phases with checkpoint-based resumable workflows. Use when starting a modernization initiative, resuming from a checkpoint, or coordinating moderni...
Guides performance optimization: atomic clock service, performance monitoring, memory optimization, battery optimization. Use when optimizing performance, monitoring metrics, or improving app efficiency.
Perform in-depth architectural analysis of codebases through iterative dialog and visual diagrams. Use when users want to understand their software architecture, explore design patterns and anti-patterns, evalu...
This skill should be used when the user asks to 'review my architecture', 'improve testability', 'refactor for testing', 'reduce mocking in tests', 'too many mocks', 'extract pure functions', 'functional core i...
Review Flutter code for SOLID principles, clean architecture, and Riverpod best practices. Use when reviewing code, checking quality, analyzing implementations, or evaluating PRs.
Write minimum necessary code following YAGNI principle to prevent bloat and over-engineering. Use when implementing features to keep the codebase lean and avoid premature optimization or speculative features.
Brazilian healthcare compliance for regulated medical and psychological content. Includes LGPD data protection, CFM/CRP/ANVISA regulatory requirements, scientific research validation, and data sanitization. Use...
Core development principles and guidelines covering security, QA, performance, documentation, and coding standards. Used by all agents to ensure consistent quality across the Orchestra system.
Génère des mappers bidirectionnels entre Domain Entities et Prisma Models pour l'isolation de la couche persistence. À utiliser lors de la création de mappers, repositories, ou quand l'utilisateur mentionne "ma...
Implement robust error handling with user-friendly messages without technical details, fail fast with explicit error messages, specific exception types for targeted handling, centralized error handling at appro...
... # Trigger + examples REQUIRED
Apply MAKER (Massively Decomposed Agentic Processes) to solve long sequential tasks using task decomposition, multi-agent voting, and error correction. Use when facing complex multi-step problems, sequential pl...
作業の責任範囲を整理し、エージェント定義に必要な情報を抽出する。エージェント設計時、責任範囲整理時、またはユーザーが責任範囲、役割分担、責任境界、エージェント構成に言及した際に使用する。
Toegang tot het Hogeschool Utrecht Open-ICT competentiekader voor het analyseren en begrijpen van studentcompetenties en beroepstaken. Gebruik deze skill wanneer je: (1) Informatie nodig hebt over HBO-I beroeps...
Standard Operating Procedure for /plan phase. Covers research depth, code reuse detection, design pattern selection, and architecture planning.
Kotlin backend layering and packaging guidelines
Senior Quality Documentation Manager for comprehensive documentation control and regulatory document review. Provides document management system design, change control, configuration management, and regulatory...
Quick reference cheatsheet for Google ADK in Clojure. Includes agent creation patterns, model configuration, tool building, execution patterns, and common workflows. Use when writing ADK code, looking up API sy...
Migrate a docent v0.9 project to v1.0 skills-based architecture
Systematic REST API design expert with consistency-focused methodology
Generate STRIDE-based threat models with intelligent threat analysis, CVSS risk scoring, and mitigation recommendations
Proactively use this skill when starting any code writing or refactoring task and must uphold SOLID, DRY, KISS, YAGNI, and SSOT principles.
Méthodologie TDD/BDD pour refactoring sûr et systématique. MANDATORY pour code improvement. À utiliser lors de refactoring, amélioration de code, ou quand l'utilisateur mentionne "refactor", "améliorer", "netto...
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é.