senior-architect
Software architecture guidance for designing scalable systems. Covers architecture patterns, tech stack decisions, system design trade-offs, and integration patterns.
Software architecture guidance for designing scalable systems. Covers architecture patterns, tech stack decisions, system design trade-offs, and integration patterns.
Create a new immutable domain entity following DDD patterns. Use when user needs to create a new business entity with domain logic, value objects, and behavior methods. Generates entity class with private constructor, static factory, and domain methods.
Domain-agnostic implementation task execution with two-tier skill loading
Use when building .NET 8 applications with minimal APIs, clean architecture, or cloud-native microservices. Invoke for Entity Framework Core, CQRS with MediatR, JWT authentication, AOT compilation. Keywords: .NET Core, .NET 8, ASP.NET Core, minimal API, EF Core, CQRS.
Use when analyzing existing codebases to generate architecture documentation - coordinates subagent-driven exploration with mandatory workspace structure, validation gates, and pressure-resistant workflows
アーキテクチャレビュー。SOLID/YAGNI/DRY/KISS原則に基づき、オーバーエンジニアリングを避けた実践的な設計改善を提案する。
Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments
Build modular, scalable Django backends using service layer pattern. Use when creating Django models, views, APIs, Celery tasks, or any backend feature. Enforces clean separation between data, business logic, and API layers.
Backend typed error handling and boundary mapping
Systematic REST API design expert with consistency-focused methodology
Type-safe error handling with discriminated unions and Result types. Use when designing error handling strategies.
Generate STRIDE-based threat models with intelligent threat analysis, CVSS risk scoring, and mitigation recommendations
IBL5 module refactoring using interface-driven architecture pattern with Repository/Service/View separation. Use when refactoring legacy PHP-Nuke modules to modern PHP.
Modern Python coding standards, best practices, testing patterns, and implementation guidelines
iOS画面実装のアーキテクチャ・設計思想スキル。Reduxパターンに基づくSingle Root State、Reducerによるビジネスロジック分離、テスタビリティを重視した実装を支援。使用シーン:(1)「このプロトタイプを本番実装にして」などの本格実装リクエスト (2)「状態管理を整理して」などのアーキテクチャ適用リクエスト (3) 画面の状態管理やテスト可能な設計が必要な場合 (4)「この画面をテストしやすくして」などのリファクタリングリクエスト
Use when implementing polymorphism and interfaces in object-oriented design. Use when creating flexible, extensible systems with interchangeable components.
実装時に遵守すべきコード品質ルール(500行ルール、固定アーキテクチャ、SOLID原則、命名規則、テストカバレッジ要件)を定義
Use when navigation is costly or module boundaries feel blurry due to messy directories, inconsistent naming, or cross-boundary imports. Goal: make architecture and dependency direction readable from the tree and imports, with minimal churn.
プロジェクト全域の命名規則。ディレクトリ、ファイル、コード内の全ルールを網羅した唯一の正解(SSoT)。
Redis 패턴 가이드. Cache-Aside, Rate Limiting, Pub/Sub, Streams 구현 시 참조. "redis", "cache", "rate limit", "pubsub", "streams" 키워드로 트리거.
Use when stakeholders pressure you to change technical priorities and you're tempted to compromise on security-first or call it synthesis - enforces risk-based prioritization over stakeholder preferences
Standardized patterns for ZIO dependency injection using the ZIO service pattern with ZLayer.derive. Use when creating new ZIO service classes, refactoring existing ZIO code to follow this pattern, reviewing code that incorrectly uses ZIO.service in business logic, or when working with ZIO layers and dependency injection. Apply this pattern for all service classes in the Scala backend.