tdd-workflow
Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle.
Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle.
Transform ambiguous requirements into precise specifications. Use before any non-trivial implementation.
Environment standards for development, staging, and production: parity principles, data and access policies, configuration boundaries, and deployment controls
DDDアーキテクチャでHonoのバックエンドを新規実装または既存コードベースをリファクタリングする際のガイド。レイヤー構成(domain/application/infrastructure/controller)、依存方向、責務境界、Hono公式ミドルウェア/プラグインの活用、Hono OpenAPIプラグイン(hono-openapi)とzod-openapiの必須採用、Drizzle ORMの利用、トランザクション境界、エラーハンドリング、テスト指針、ESLint/Prettierの必須導入を含む。
표준 참조 분리 패턴(Standard Reference Separation Pattern)을 사용하여 워크플로우를 새로 생성하거나 개선합니다.
Prevents over-engineering by enforcing industry-proven principles: AHA (Avoid Hasty Abstractions), YAGNI, Colocation, and Rule of Three. Use when designing features, planning architecture, "architect this", "design the structure", or when the code-architect agent is dispatched. Triggers: file structure, module organization, abstraction decisions, component splitting.
modern practices Input System async await dependency injection pooling optimization
Spring Boot 4 后端开发规范。当创建 Controller、Service、Entity、Repository 或后端 API 时自动使用。
core.async.flow provides a declarative framework for building process flows with strict separation of application logic from topology, execution, and lifecycle management. Use when building multi-process systems, data pipelines, or when you need coordinated lifecycle management and error handling across communicating processes.
C# 12 / .NET 8 개발 전문가 - ASP.NET Core, Entity Framework, Blazor 및 현대적 C# 패턴 지원. .NET API, 웹 애플리케이션, 엔터프라이즈 솔루션 개발에 사용
应用面向对象设计五大原则(单一职责、开闭、里氏替换、接口隔离、依赖倒置),系统化评审类与模块设计质量。当需要评审架构设计、重构现有代码、审查类职责划分时使用。支持多层次检查清单和违反原则的诊断修复。
Enterprise context and session management with token budget optimization and state persistence
Skill for creating and modifying Golang microservices using DDD, immutable models, functional composition, GORM entities, JSON:API transport, and Kafka messaging with context based multi tenancy.
The final gatekeeper. Audits RFCs to reject over-engineering, unnecessary dependencies, and resume-driven development.
Create Repository interface and Finder interface for domain entity persistence. Use when entity needs persistence layer with commands (save, delete) and queries (find, findAll). Generates both Repository (commands) and Finder (queries) following CQRS pattern.
Explains the Display Identifier system in padz—a dual-identifier approach that provides stable, user-friendly IDs (1, 2, p1, d1) while internally using UUIDs. Use when working on pad listing, selection, or any CLI command that references pads by ID. Critical for understanding why filtered views preserve canonical indexes.
Ensure every meaningful output lands in the right place and stays findable
Senior Risk Management specialist for medical device companies implementing ISO 14971 risk management throughout product lifecycle. Provides risk analysis, risk evaluation, risk control, and post-production information analysis. Use for risk management planning, risk assessments, risk control verification, and risk management file maintenance.
Recall and reuse prior decisions, constraints, and artifacts using MCP memory (e.g., Neo4j). Use when the user references past work (“jak ostatnio”, “kontynuuj”), when resuming a project thread, or when a repeated topic suggests existing decisions.
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing applications for better maintainability.
Instrument error handling, retries, fallbacks, and failure patterns
SagebaseでのBAML (Boundary ML) 統合に関する知識とベストプラクティス。BAML定義ファイルの作成、クライアント再生成、Factory Pattern実装、ハイブリッドアプローチの設計を支援します。