메뉴
Use when deciding whether a Yogieat prompt should stay on the main thread or consider repo-local agents. Classifies prompts, maps them to `feature_mapper`, `architecture_guard`, `validation_triager`, or `harness_curator`, and keeps delegation intentionally minimal.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when deciding where new Yogieat code belongs or when reviewing architecture drift. Focuses on Service vs Facade boundaries, validator extraction, processor naming, transaction placement, dependency minimization, and preserving the existing multi-module structure.
Use when adding or extending a Yogieat feature in the Java 25 multi-module Spring Boot architecture. Maps the request to the smallest consistent slice across `apps:api/admin`, `apps:domain`, `storage`, `external`, and `support` while preserving the current Service, Facade, Processor, and Validator conventions.
Use when repeated Yogieat prompts, review comments, or misunderstandings should be translated into harness candidates or stable rules. Classifies new observations, applies the candidate-to-promotion policy, and keeps harness updates intentional rather than noisy.
Use when validating Yogieat changes or choosing the smallest Java 25 Gradle proof command. Applies Spotless first, then compile, then module-local or full tests based on repo-specific escalation rules.
Use when writing, refactoring, or reviewing Yogieat tests. Focuses on behavior-first assertions, boundary-only mocking, test layer choice, and smell detection for spy-heavy or verify-heavy tests.
yogieat-server 멀티모듈 클린 아키텍처의 구현 가이드. 새 도메인이나 기능을 추가할 때 어떤 모듈에 어떤 파일을 어떤 패턴으로 만들어야 하는지 안내한다. Spring Boot 멀티모듈, 클린 아키텍처, domain Record, Entity 매핑, Repository 인터페이스 패턴 등을 다룬다.
| name | yogieat-agent-router |
| description | Use when deciding whether a Yogieat prompt should stay on the main thread or consider repo-local agents. Classifies prompts, maps them to `feature_mapper`, `architecture_guard`, `validation_triager`, or `harness_curator`, and keeps delegation intentionally minimal. |
Use this skill before substantial work when you need to decide whether the task stays local or should consider repo-local agents.
./AGENTS.md and .codex/rules/agent-routing.md.feature_mapper for impact mapping before new feature implementation.architecture_guard when the main ambiguity is service, facade, validator, processor, or transaction placement.architecture_guard when the ambiguity is resource-oriented URI design, response shape ownership, or POST creation semantics.validation_triager when the main ambiguity is Java 25 Gradle validation scope or CI parity.yogieat-testing-guard before writing, refactoring, or reviewing tests.harness_curator when the task involves repeated prompts, repeated review comments, or harness rule promotion.