spine-mcp-tools
Guide for creating MCP (Model Context Protocol) tools for Spine domains. Covers tool naming, parameter patterns, session context, error handling, and testing.
Découvrez les skills databases architecture patterns, comparez leurs dépôts et consultez leurs instructions.
Guide for creating MCP (Model Context Protocol) tools for Spine domains. Covers tool naming, parameter patterns, session context, error handling, and testing.
Guide for working with the Spine Framework - a foundation for building domain-specific authoring tools. Covers the framework/domain boundary, extension points, package structure, and patterns for adding new dom...
Spec-driven development workflow for AI coding assistants. Use when creating proposals, managing specs, implementing changes, or archiving completed features. Triggers on keywords like proposal, spec, change, p...
아키텍처, 설계, 시스템 설계, 구조 설계, 레이어 설계 - Use when designing systems, layer structures, or module boundaries. Architecture design guide based on Clean Architecture and DDD principles.
Comprehensive entity skill for breathe-together-v2. Create new entities, improve existing ones, debug issues, and systematically review all entities. Covers ECS Architecture, Triplex Integration, Performance Tu...
Skill for creating well-formed issues from discoveries during implementation or validation
Test-driven development workflow for writing reliable, maintainable code
Test-driven development workflow for writing reliable, maintainable code
Backend entity patterns - services with DI, Drizzle schemas (3-file pattern), ORPC routers, TypeIDs, neverthrow. Use when creating services, schemas, routers, or new entities.
Master error handling and recovery patterns for robust agent workflows. Learn retry strategies, timeout handling, optimistic updates with rollback, circuit breakers, and graceful degradation. Essential for prod...
Create Architecture Decision Records (ADRs) following project standards. Guides template usage, process, and best practices for documenting architecturally significant decisions.
システム全体のコア設計原則とパフォーマンス基準
リファクタリングのガイドラインと手順
Comprehensive guide for Test-Driven Development (TDD) methodology. Use this skill when the user asks to implement features using TDD, write tests first, follow red-green-refactor cycle, or develop code with tes...
Guide for porting code from optaic-v0 to optaic-trading. Use when migrating DataAPI, pipelines, stores, accessors, operators, or expressions into the Resource/Activity architecture. Covers pattern mappings for...
Analyze implementation failures and generate recovery plans. Use when an issue fails and needs diagnosis for retry or escalation.
Resolve disagreements between agents or approaches using test-based adjudication. Use when agents disagree, when multiple valid approaches exist, when the user asks "which approach", or when making architectura...
Feature development using DPPM framework (Discover, Plan, Prototype, Monitor). Use for feature planning and multi-agent orchestration.
Index of documented solution patterns from past engineering problems. Use this skill when encountering similar issues to leverage proven solutions for TypeScript strict mode compliance, authentication migration...
Feature development using DPPM framework (Discover, Plan, Prototype, Monitor). Use for feature planning and multi-agent orchestration.
Software architecture guidance for designing scalable systems. Covers architecture patterns, tech stack decisions, system design trade-offs, and integration patterns.
Component design patterns including composition, render props, compound components, and design systems. Use for reusable component architecture.
Build production-ready React applications with performance optimization, code splitting, state management, and accessibility. Use for React components requiring optimization or complex state patterns.
Software architecture guidance for designing scalable systems. Covers architecture patterns, tech stack decisions, system design trade-offs, and integration patterns.
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é.