메뉴
Java/TS emitter parity review for exeris-tooling. Use when DomainMetadata shape changes, when a new generator surface is added on one side, or when one side starts consuming a field the other does not emit.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Angular v22 emission discipline for exeris-codegen-ts. Use whenever authoring or modifying a TS generator (*-gen.ts) or the emitted app scaffold — keeps emitted Angular idioms on the v22 canon (Signal Forms, httpResource, dropped deprecations) and gates the phased A→B→C migration.
Decision-document shape gate for exeris-tooling. Use BEFORE drafting an ADR, RFC, or research note — picks the right shape (Research vs RFC vs ADR) for the question, enforces number reservation in the central adr-index.md, and blocks refactor-only or measurement-missing material from becoming an ADR. Invoke whenever someone asks to "write an ADR", "document this decision", or capture a design choice.
Generated-output lifecycle discipline for exeris-tooling. Use whenever a change touches how code is emitted to or pruned from src/main/generated, proposes "always regenerate" semantics, or affects the L1-committed / L2-detach story (OutputWriter, the codegen Maven plugin generate/detach mojos, the generated-output pruner, mvn clean interactions). Guards hard-constraint
After triage (see exeris-tooling-task-classifier), use to turn a classified exeris-tooling task into an execution plan — primary agent, ordered secondary handoffs, validation gates tied to the risk surface, and the minimal next action. Invoke when a build-time task spans modules or needs an explicit agent sequence and gate list before implementation starts.
Strict-mode completeness-audit review for exeris-tooling. Use whenever a generator (Java or TS) starts or stops consuming an annotation attribute or a whole annotation, when an SDK annotation surface changes, or when the INERT_ATTRIBUTES / INERT_ANNOTATIONS registries in ExerisDomainProcessor are touched. Catches stale registry entries that produce false "no effect" warnings under -Aexeris.strict.
Use FIRST, before starting any exeris-tooling build-time change, to triage it — classifies task type (processor / codegen-java / codegen-ts / e2e / docs), scope, severity, and primary risk against the pipeline contract, then recommends the primary agent. Invoke whenever a request lands in exeris-tooling and the owning module or risk surface is not yet obvious. Chain into exeris-tooling-routing-planner for the execution plan.
| name | exeris-tooling-emitter-parity-review |
| description | Java/TS emitter parity review for exeris-tooling. Use when DomainMetadata shape changes, when a new generator surface is added on one side, or when one side starts consuming a field the other does not emit. |
Enforce: DomainMetadata is the sole contract between processor and generators; shared surfaces stay aligned across exeris-codegen-java and exeris-codegen-ts.
The TS package is intentionally outside the Maven reactor — coordination is manual and explicit. This skill is the manual gate.
DomainMetadata field.MetadataLoader or GeneratorRegistry.mvn install AND cd exeris-codegen-ts && npm test?JAVA_ONLY, TS_ONLY, SHARED. Most DomainMetadata fields are SHARED by default.docs/MIGRATION-0.x-to-1.0.md (or future MIGRATION) need an entry? Downstream user apps regenerate; user-visible field renames are a migration story.mvn install AND npm test run? If only one, flag.APPROVE, CONDITIONAL, REJECT.JAVA_ONLY / TS_ONLY / SHARED)mvn install, npm test — present / missing)APPROVE / CONDITIONAL / REJECT)CLAUDE.md.mvn install and npm test evidence.