一键在 Manus 中运行任何 Skill

exeris-tooling-kernel-target-discipline

星标0

分支0

更新时间2026年5月20日 08:49

Single-target discipline for exeris-tooling. Use whenever a PR proposes a new generator shape, a backend-strategy parameter, or anything that could reintroduce the Spring/Quarkus/Micronaut/Vanilla multi-backend abstraction removed in 0.1.0.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

exeris-systems

exeris-systems/exeris-tooling

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Exeris Tooling Kernel-Target Discipline

Purpose

The 0.1.0 release deliberately removed Spring/Quarkus/Micronaut/Vanilla generators and deleted the multi-backend abstraction. This skill is the gate that keeps the single-target story intact under PR pressure.

When to Use

Any PR adding a new *Generator class.
Any PR adding a backend-selection parameter, registry key, or feature flag in exeris-codegen-core.
Any PR whose stated motivation is "support framework X" or "host on runtime Y".
Any PR that touches the GeneratorRegistry discovery / strategy surface.

Required Inputs

PR diff and stated motivation.
Target downstream user (if motivation is "user X needs Spring hosting").
Current GeneratorRegistry shape.

Review Procedure

Detect backend-specific output — scan emitted text for Spring @RestController, Quarkus @Path, Micronaut @Controller, plain HttpServlet, JAX-RS @Path. Any match is a hard signal of multi-backend regression.
Detect backend-specific imports — emitted Java imports should target eu.exeris.kernel.* (and supporting JDK / Jackson). Imports targeting org.springframework.*, io.quarkus.*, io.micronaut.*, jakarta.ws.rs.*, javax.ws.rs.* are a hard signal.
Detect strategy reintroduction — search for BackendStrategy, BackendType (re-added), if (backend == ...) branching, multiple parallel Kernel*Generator / Spring*Generator shapes.
Check the motivation — if the user need is "Spring hosting", the right answer is "use exeris-spring-runtime for migration", not "regenerate Spring code here". Cite the cross-repo split.
ADR check — multi-target reintroduction requires a NEW ADR (single-target was the 0.1.0 decision). Don't allow it through a *Generator PR.
Decision and report — produce one of: APPROVE, CONDITIONAL, REJECT.

Decision Logic

APPROVE: Output targets eu.exeris.kernel.* only; no backend-strategy parameter; motivation is kernel-aligned.
CONDITIONAL: Motivation is a downstream need that has a non-codegen answer (e.g. point at exeris-spring-runtime); recommend redirecting the PR.
REJECT: Backend-specific output / imports / strategy reintroduction without a new ADR; assume rollback intent.

Completion Criteria

Output scanned for backend-specific shape.
Imports scanned for framework targeting.
Strategy / registry shape audited.
Cross-repo redirect proposed when motivation is a different repo's job.
Verdict and ADR requirement recorded.

Review Output Template

Scope analysed (generators / registry / core touched)
Backend-shape findings (annotations, imports, strategy)
Motivation audit (kernel-aligned vs cross-repo redirect)
ADR requirement (none / new ADR required)
Verdict (APPROVE / CONDITIONAL / REJECT)
Required actions (precise and minimal)

Non-Negotiable Rules

Never approve a Spring*Generator / Quarkus*Generator / Micronaut*Generator / Vanilla*Generator without a new ADR overriding the 0.1.0 single-target decision.
Never approve a BackendStrategy reintroduction.
Always redirect Spring-hosting motivation to exeris-spring-runtime.

同仓库更多 Skills

同仓库

exeris-tooling-angular-v22-emission

exeris-systems/exeris-tooling

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.

2026-06-180

exeris-tooling-adr-shape-gate

exeris-systems/exeris-tooling

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.

2026-06-180

exeris-tooling-detach-output-discipline

exeris-systems/exeris-tooling

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

2026-06-180

exeris-tooling-routing-planner

exeris-systems/exeris-tooling

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.

2026-06-180

exeris-tooling-strict-audit-review

exeris-systems/exeris-tooling

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.

2026-06-180

exeris-tooling-task-classifier

exeris-systems/exeris-tooling

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.

2026-06-180

name	exeris-tooling-kernel-target-discipline
description	Single-target discipline for exeris-tooling. Use whenever a PR proposes a new generator shape, a backend-strategy parameter, or anything that could reintroduce the Spring/Quarkus/Micronaut/Vanilla multi-backend abstraction removed in 0.1.0.

Exeris Tooling Kernel-Target Discipline

Purpose

When to Use

Any PR adding a new *Generator class.
Any PR adding a backend-selection parameter, registry key, or feature flag in exeris-codegen-core.
Any PR whose stated motivation is "support framework X" or "host on runtime Y".
Any PR that touches the GeneratorRegistry discovery / strategy surface.

Required Inputs

PR diff and stated motivation.
Target downstream user (if motivation is "user X needs Spring hosting").
Current GeneratorRegistry shape.

Review Procedure

Detect backend-specific output — scan emitted text for Spring @RestController, Quarkus @Path, Micronaut @Controller, plain HttpServlet, JAX-RS @Path. Any match is a hard signal of multi-backend regression.
Detect backend-specific imports — emitted Java imports should target eu.exeris.kernel.* (and supporting JDK / Jackson). Imports targeting org.springframework.*, io.quarkus.*, io.micronaut.*, jakarta.ws.rs.*, javax.ws.rs.* are a hard signal.
Detect strategy reintroduction — search for BackendStrategy, BackendType (re-added), if (backend == ...) branching, multiple parallel Kernel*Generator / Spring*Generator shapes.
Check the motivation — if the user need is "Spring hosting", the right answer is "use exeris-spring-runtime for migration", not "regenerate Spring code here". Cite the cross-repo split.
ADR check — multi-target reintroduction requires a NEW ADR (single-target was the 0.1.0 decision). Don't allow it through a *Generator PR.
Decision and report — produce one of: APPROVE, CONDITIONAL, REJECT.

Decision Logic

APPROVE: Output targets eu.exeris.kernel.* only; no backend-strategy parameter; motivation is kernel-aligned.
CONDITIONAL: Motivation is a downstream need that has a non-codegen answer (e.g. point at exeris-spring-runtime); recommend redirecting the PR.
REJECT: Backend-specific output / imports / strategy reintroduction without a new ADR; assume rollback intent.

Completion Criteria

Output scanned for backend-specific shape.
Imports scanned for framework targeting.
Strategy / registry shape audited.
Cross-repo redirect proposed when motivation is a different repo's job.
Verdict and ADR requirement recorded.

Review Output Template

Scope analysed (generators / registry / core touched)
Backend-shape findings (annotations, imports, strategy)
Motivation audit (kernel-aligned vs cross-repo redirect)
ADR requirement (none / new ADR required)
Verdict (APPROVE / CONDITIONAL / REJECT)
Required actions (precise and minimal)

Non-Negotiable Rules

Never approve a Spring*Generator / Quarkus*Generator / Micronaut*Generator / Vanilla*Generator without a new ADR overriding the 0.1.0 single-target decision.
Never approve a BackendStrategy reintroduction.
Always redirect Spring-hosting motivation to exeris-spring-runtime.