๋ถ๊ธฐ์ค๊ณ์(branch-architect)๊ฐ ์ฌ์ฉํ๋ ๋ถ๊ธฐ ๋ก์ง ์ ๋ฌธ ์คํฌ. ๋ถ๊ธฐ ๊ตฌ์กฐ ํจํด, ํ๋๊ทธ ์์คํ ์ค๊ณ, ์๋ฉ ์ํคํ ์ฒ, ์ํ ๊ด๋ฆฌ ๋ฐฉ๋ฒ๋ก ์ ์ ๊ณตํ๋ค. '๋ถ๊ธฐ ์ค๊ณ', '๋ฉํฐ ์๋ฉ', 'ํ๋๊ทธ ์์คํ ', '๋ถ๊ธฐ ๊ตฌ์กฐ' ๋ฑ์ ํ์ฉํ๋ค.
ํ์คํธ๋์์ด๋(quest-designer)๊ฐ ์ฌ์ฉํ๋ ํ์คํธ ์ค๊ณ ํจํด ์ ๋ฌธ ์คํฌ. ํ์คํธ ์ํคํ์ , ๋ณด์ ์ฌ๋ฆฌํ, ๋์ด๋ ๊ณก์ , ํ๋ ์ด์ด ๋๊ธฐ ๋ถ์ฌ ํ๋ ์์ํฌ๋ฅผ ์ ๊ณตํ๋ค. 'ํ์คํธ ์ค๊ณ', '๋ณด์ ์ฒด๊ณ', '๋ฏธ์ ๊ตฌ์กฐ', 'ํ์คํธ ํจํด' ๋ฑ์ ํ์ฉํ๋ค.
๋ ๊ฑฐ์ ์์คํ ์ ์ ์ง์ ์ผ๋ก ๊ต์ฒดํ๋ Strangler Fig ํจํด๊ณผ ๊ด๋ จ ๋ง์ด๊ทธ๋ ์ด์ ํจํด์ ์์ธ ๊ตฌํ ๊ฐ์ด๋. 'strangler fig', '์ ์ง์ ๋ง์ด๊ทธ๋ ์ด์ ', '๋ฆฌํฉํ ๋ง ํจํด', 'branch by abstraction', 'parallel run', '์ ์ง์ ๊ต์ฒด', '๋ง์ด๊ทธ๋ ์ด์ ํจํด ์ ํ' ๋ฑ ๋ ๊ฑฐ์ ์ ํ ํจํด ์ ์ฉ ์ ์ด ์คํฌ์ ์ฌ์ฉํ๋ค. refactoring-strategist์ migration-engineer์ ํจํด ์ ํยท๊ตฌํ์ ๊ฐํํ๋ค. ๋จ, ์ ์ฒด ํ ์ค์ผ์คํธ๋ ์ด์ ์ด๋ ํ๋ก์ ํธ ๊ด๋ฆฌ๋ ์ด ์คํฌ์ ๋ฒ์๊ฐ ์๋๋ค.
๋ถ์ฐ ์์คํ ํต์ฌ ํจํด(Saga, CQRS, Circuit Breaker, ์ด๋ฒคํธ ์์ฑ ๋ฑ)์ ๊ตฌํ ๊ฐ์ด๋์ ์ ํ ๋งคํธ๋ฆญ์ค. '๋ถ์ฐ ํธ๋์ญ์ ', 'Saga ํจํด', 'CQRS', '์ํท ๋ธ๋ ์ด์ปค', '์ด๋ฒคํธ ์์ฑ', '๋ถ์ฐ ํจํด', '๋ณด์ ํธ๋์ญ์ ', '์ต์ข ์ผ๊ด์ฑ' ๋ฑ ๋ถ์ฐ ์์คํ ํจํด ์ ์ฉ ์ ์ด ์คํฌ์ ์ฌ์ฉํ๋ค. communication-designer์ service-architect์ ๋ถ์ฐ ์์คํ ์ค๊ณ ์ญ๋์ ๊ฐํํ๋ค. ๋จ, ์ธํ๋ผ ๊ตฌ์ถ์ด๋ ๋ชจ๋ํฐ๋ง ์ค์ ์ ์ด ์คํฌ์ ๋ฒ์๊ฐ ์๋๋ค.
๋ง์ดํฌ๋ก์๋น์ค ์ํคํ ์ฒ๋ฅผ ์ค๊ณยท๋ถํดยทํต์ ยท๋ชจ๋ํฐ๋งํ๋ ํ ํ์ดํ๋ผ์ธ. ๋๋ฉ์ธ ๋ถ์, ์๋น์ค ์ค๊ณ, ํต์ ํจํด, ๊ด์ธก์ฑ์ ์์ด์ ํธ ํ์ด ํ์ ํ์ฌ ์ํํ๋ค. '๋ง์ดํฌ๋ก์๋น์ค ์ํคํ ์ฒ ์ค๊ณํด์ค', '์๋น์ค ๋ถํดํด์ค', 'MSA ์ค๊ณ', '๋๋ฉ์ธ ๋ถ์ํด์ค', '์ด๋ฒคํธ ๊ธฐ๋ฐ ์ํคํ ์ฒ', '์๋น์ค ๊ฐ ํต์ ์ค๊ณ', '๋ถ์ฐ ์์คํ ์ค๊ณ', 'API ๊ฒ์ดํธ์จ์ด ์ค๊ณ' ๋ฑ ๋ง์ดํฌ๋ก์๋น์ค ์ค๊ณ ์ ๋ฐ์ ์ด ์คํฌ์ ์ฌ์ฉํ๋ค. ๊ธฐ์กด ๋ชจ๋๋ฆฌ์ค์์ MSA๋ก ์ ํํ๋ ๊ฒฝ์ฐ์๋ ์ง์ํ๋ค. ๋จ, ์ค์ ์ธํ๋ผ ๊ตฌ์ถ, Kubernetes ๋ฐฐํฌ, ์ฝ๋ ๊ตฌํ์ ์ด ์คํฌ์ ๋ฒ์๊ฐ ์๋๋ค.
Terraform ๋ชจ๋ ์ค๊ณ ํจํด, ๋๋ ํ ๋ฆฌ ๊ตฌ์กฐ, ์ํ ๊ด๋ฆฌ, ํ๊ฒฝ ๋ถ๋ฆฌ ์ ๋ต์ ์์ธ ๊ฐ์ด๋. 'Terraform ๋ชจ๋', '๋ชจ๋ ๊ตฌ์กฐ', '์ํ ๊ด๋ฆฌ', 'remote state', 'ํ๊ฒฝ ๋ถ๋ฆฌ', 'workspace', 'terragrunt', '๋ชจ๋ ํจํด' ๋ฑ Terraform ๋ชจ๋ ์ค๊ณ ์ ์ด ์คํฌ์ ์ฌ์ฉํ๋ค. infra-architect์ drift-detector์ IaC ์ค๊ณ ์ญ๋์ ๊ฐํํ๋ค. ๋จ, ์ค์ terraform apply๋ ์ธํ๋ผ ํ๋ก๋น์ ๋ ์คํ์ ์ด ์คํฌ์ ๋ฒ์๊ฐ ์๋๋ค.
SDK/API ํด๋ผ์ด์ธํธ ์ค๊ณ ํจํด: ๋น๋ ํจํด, ์ธํฐ์ ํฐ ์ฒด์ธ, ์ฌ์๋ ์ ๋ต, ํ์ ์์ ์ค๊ณ, ์๋ฌ ํธ๋ค๋ง, ํ์ด์ง๋ค์ด์ ๋ํผ ๊ฐ์ด๋. 'SDK ์ค๊ณ', 'ํด๋ผ์ด์ธํธ ํจํด', '์ฌ์๋ ์ ๋ต', '์ธํฐ์ ํฐ', '๋น๋ ํจํด', 'SDK ์๋ฌ ์ฒ๋ฆฌ', 'ํ์ ์์ ', 'SDK ์ํคํ ์ฒ' ๋ฑ SDK ๊ตฌ์กฐ ์ค๊ณ ์ ์ด ์คํฌ์ ์ฌ์ฉํ๋ค. sdk-developer์ SDK ์ค๊ณ ์ญ๋์ ๊ฐํํ๋ค. ๋จ, API ์คํ ํ์ฑ์ด๋ ํ ์คํธ/๋ฌธ์ ์์ฑ์ ์ด ์คํฌ์ ๋ฒ์๊ฐ ์๋๋ค.
์ง์๋ฒ ์ด์ค์ ์ ๋ณด ๊ตฌ์กฐ(IA)๋ฅผ ์ค๊ณํ๋ ์ ๋ฌธ ์คํฌ. taxonomy-designer ์์ด์ ํธ๊ฐ ๋ถ๋ฅ ์ฒด๊ณ, ๋ค๋น๊ฒ์ด์ , ๋ ์ด๋ธ๋ง ์์คํ ์ ์ค๊ณํ ๋ ํ์ฉํ๋ค. '์ ๋ณด ๊ตฌ์กฐ', 'IA ์ค๊ณ', '์นดํ ๊ณ ๋ฆฌ ์ค๊ณ', '๋ค๋น๊ฒ์ด์ ', '์ฌ์ดํธ๋งต', '์นด๋ ์ํ ' ๋ฑ์ ๋งฅ๋ฝ์์ ์๋ ์ ์ฉํ๋ค. ๋จ, UX ๋ฆฌ์์น ์คํ์ด๋ UI ํ๋กํ ํ์ดํ์ ์ด ์คํฌ์ ๋ฒ์๊ฐ ์๋๋ค.
๋ด๋ถํต์ ํ๋ ์์ํฌ ๊ฐ์ด๋. scope-designer์ checklist-builder ์์ด์ ํธ๊ฐ ๊ฐ์ฌ ๋ฒ์์ ํต์ ํญ๋ชฉ์ ์ค๊ณํ ๋ ์ฐธ์กฐ. 'COSO', '๋ด๋ถํต์ ', 'ํต์ ํ ์คํธ' ์์ฒญ ์ ์ฌ์ฉ. ๋จ, ์ธ๋ถ ๊ฐ์ฌ ๋ํ์ด๋ ๋ฒ์ ์๊ฒฌ์ ์์ฑ์ ๋ฒ์ ๋ฐ.
Applies behavior-driven development principles including Gherkin scenarios and test-driven development. This skill should be used when the user asks to implement features, fix bugs, or when writing executable specifications and tests before writing production code.
Structures Flutter apps using layered architecture (UI / Logic / Data) with feature-first file organization. Use when creating new features, designing the project structure, adding repositories/services/view models (or cubits/providers/notifiers), or wiring dependency injection. State management agnostic.
Provides best practices for Flutter app architecture, including layered architecture, data flow, state management patterns, and extensibility guidelines.
Structure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters", "hexagonal architecture", "use case boundary", "onion architecture", "screaming architecture", or "framework independence". Also trigger when decoupling business logic from databases or frameworks, defining module boundaries, or debating where to put business rules. Covers component principles, boundaries, and SOLID. For code quality, see clean-code. For domain modeling, see domain-driven-design.
Design data systems by understanding storage engines, replication, partitioning, transactions, and consistency models. Use when the user mentions "database choice", "replication lag", "partitioning strategy", "consistency vs availability", "stream processing", "ACID transactions", "eventual consistency", or "LSM tree vs B-tree". Also trigger when choosing between SQL and NoSQL, designing data pipelines, or debugging distributed system consistency issues. Covers data models, batch/stream processing, and distributed consensus. For system design, see system-design. For resilience, see release-it.
Model software around the business domain using bounded contexts, aggregates, and ubiquitous language. Use when the user mentions "domain modeling", "bounded context", "aggregate root", "ubiquitous language", "anti-corruption layer", "context mapping", "domain events", or "strategic design". Also trigger when splitting a monolith into services, defining microservice boundaries, or aligning code structure with business processes. Covers entities vs value objects, domain events, and context mapping strategies. For architecture layers, see clean-architecture. For complexity, see software-design-philosophy.
Diagnose and fix retention problems using behavior design (B=MAP). Use when the user mentions "users drop off", "activation rate", "onboarding friction", "retention metrics", "why users dont complete", "churn analysis", "user activation", or "aha moment". Also trigger when analyzing cohort retention curves, designing activation milestones, reducing time-to-value for new users, or investigating why users stop after their first session. Covers the Ability Chain, prompt design, and tiny behaviors that compound. For habit loops and variable rewards, see hooked-ux. For intrinsic motivation, see drive-motivation.
Apply meta-principles of software craftsmanship: DRY, orthogonality, tracer bullets, and design by contract. Use when the user mentions "best practices", "pragmatic approach", "broken windows", "tracer bullet", "software craftsmanship", "technical debt prevention", "prototype vs tracer bullet", or "code ownership". Also trigger when evaluating build-vs-buy decisions, designing estimation approaches, or choosing between reversible and irreversible architectural decisions. Covers estimation, domain languages, and reversibility. For code-level quality, see clean-code. For refactoring techniques, see refactoring-patterns.
Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "timeout strategy", "deployment pipeline", "chaos engineering", "bulkhead pattern", "retry with backoff", or "health checks". Also trigger when designing resilient microservices, planning zero-downtime deployments, or investigating cascading failure scenarios. Covers capacity planning, health checks, and anti-fragility patterns. For data systems, see ddia-systems. For system architecture, see system-design.
Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues. Use when the user mentions "system design", "scale this", "high availability", "rate limiter", "design a URL shortener", "system design interview", "capacity planning", or "distributed architecture". Also trigger when estimating infrastructure requirements, choosing between microservices and monoliths, or designing for millions of concurrent users. Covers common system designs and back-of-the-envelope estimation. For data fundamentals, see ddia-systems. For resilience, see release-it.
Build resilient, long-running, multi-step applications with AWS Lambda durable functions with automatic state persistence, retry logic, and orchestration for long-running executions. Covers the critical replay model, step operations, wait/callback patterns, error handling with saga pattern, testing with LocalDurableTestRunner. Triggers on phrases like: lambda durable functions, workflow orchestration, state machines, retry/checkpoint patterns, long-running stateful Lambda functions, saga pattern, human-in-the-loop callbacks, and reliable serverless applications.
Generates a Jupyter notebook that deploys fine-tuned models from SageMaker Serverless Model Customization to SageMaker endpoints or Bedrock. Use when the user says "deploy my model", "create an endpoint", "make it available", or asks about deployment options. Identifies the correct deployment pathway (Nova vs OSS), generates deployment code, and handles endpoint configuration.
Build a new read model following project conventions (event handlers, tests, migration, configuration)
