AgentSkillsCN

app-port-generator

按照package-info规范与事务规则（仅限Spring-TX），生成应用层用例（命令/处理器/组装器/DTO）。

SKILL.md
--- frontmatter
name: app-port-generator
description: "Generates app-layer ports (out ports/stores/gateways) with clear retry/error semantics and minimal coupling."

App Port Generator

Follow .codex/skills/GENERATOR_SKILL_STRUCTURE.md.

Use For

  • •{{basePackage}}.app.biz.port.* and app-common ports

Inputs Required

  • •Capability required (read model? store? external call?)
  • •Error/retry semantics required by callers
  • •Idempotency contract if used in at-least-once flows

Outputs

  • •{{appModuleDir}}/src/main/java/{{basePackagePath}}/.../<Port>.java
  • •Optional unit tests for contract helpers (if any)

Naming & Packaging

  • •*Store for persistence-like ports used by app-common (outbox/inbox/workflow).
  • •*Transport for broker publishers.
  • •*Gateway for external systems (system-first infra implementations).

Implementation Rules

  • •Prefer small, capability-focused interfaces.
  • •Define error semantics:
    • •retryable vs non-retryable (when relevant)
    • •idempotency expectations
  • •Avoid leaking infra exceptions across the boundary; translate to app exceptions or result types.

Reference Implementations

  • •{{appModuleDir}}/src/main/java/{{basePackagePath}}/app/common/outbox/port/OutboxStore.java
  • •{{appModuleDir}}/src/main/java/{{basePackagePath}}/app/common/event/port/InboxStore.java
  • •{{appModuleDir}}/src/main/java/{{basePackagePath}}/app/common/workflow/port/WorkflowStore.java

Tests

  • •Unit tests for any default implementations or policies (e.g., retry policies).

Pitfalls

  • •Making ports too large (hard to mock, hard to implement).

Output checklist

  • • Interface has clear contract docs (short, pragmatic)
  • • Unit tests validate boundary behavior if non-trivial