Creating and managing Supabase PostgreSQL databases for StickerNest. Use when the user asks to create tables, add columns, write migrations, design schemas, implement RLS policies, optimize indexes, partition tables, or scale the database. Covers enterprise-grade security, performance optimization, and social features.
Modern async ORM with type-safe models and efficient queries
Guide for Doctrine entity/aggregate mapping conventions. Use when mapping entities, configuring relationships, or adding custom types.
Use when invalid data causes failures deep in execution, requiring validation at multiple system layers - validates at every layer data passes through to make bugs structurally impossible
Single Responsibility Code in Self-Documented Folder Structure
Find and document external code patterns from public sources. Use when user mentions 'find examples', 'scout patterns', 'research implementations', or starting new feature without precedent.
Station Service SDK를 사용한 테스트 시퀀스 개발 가이드. SequenceBase 패턴, emit 메서드, manifest.yaml 작성법 제공. 사용자가 시퀀스 개발, SequenceBase 구현, 테스트 자동화 코드 작성, manifest.yaml 설정, emit 메서드 사용법을 문의할 때 활성화. (project)
Domain Layer 전문가. DDD Aggregate Root 설계, VO 불변 객체, Domain Event, Domain Exception 구현. Law of Demeter 적용, Tell Don't Ask 패턴 강제. Lombok 금지, Setter 금지, 외부 의존성 금지.
Modern Elixir idioms, functional patterns, testing strategies, and implementation best practices
Apply DDD tactical patterns (Entities, Value Objects, Aggregates, Domain Services, Repositories) and strategic design (Ubiquitous Language, Bounded Contexts). Use when modeling complex business logic.
Patterns and strategies for cache invalidation - one of the two hardest problems in computer science.
Advanced Backend Architecture (Clean/Hexagonal), Node.js, and Security Best Practices
本项目里面的各种架构设计, 设计中用到的各种概念例如 system, action, view-function, action-function, action-handler, base, component 等的解释
Chuyên gia Flutter với kiến thức sâu về Clean Architecture, Performance và Modern Dart 3
Guidelines for working with Option (nullable values) and Result (error handling) types in odu_core.
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.
Refactor ASP.NET Core/C# code to improve maintainability, readability, and adherence to best practices. Transforms fat controllers, duplicate code, and outdated patterns into clean, modern .NET code. Applies C# 12 features like primary constructors and collection expressions, SOLID principles, Clean Architecture patterns, and proper dependency injection. Identifies and fixes anti-patterns including service locator, captive dependencies, and missing async/await patterns.
Use when facing 2+ independent tasks that can be worked on without shared state. Dispatch one agent per problem domain for concurrent investigation.
Guide for building software with Clean Architecture, DDD, SOLID principles, and hexagonal/onion patterns. Use when designing new features, refactoring code, reviewing architecture, or when user mentions clean code, architecture patterns, layers, separation of concerns, maintainability, testability, or asks for architectural guidance.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Modern ESM import/export patterns. Use when writing or reviewing module structure.
Comprehensive backend development guide for Node.js/Express/TypeScript microservices. Use when creating routes, controllers, services, repositories, middleware, or working with Express APIs, Prisma database access, Sentry error tracking, Zod validation, unifiedConfig, dependency injection, or async patterns. Covers layered architecture (routes → controllers → services → repositories), BaseController pattern, error handling, performance monitoring, testing strategies, and migration from legacy patterns.
Comprehensive error handling patterns for Splits Network services and apps
Gate 5: Data structures document - defines entities, relationships, and ownership before database technology selection. Large Track only.
