Chords

Chords build and release-engineering policy. Use for root and codegen/plugins Gradle build logic, buildSrc dependency coordinates, publishing wiring, version increments, generated `pom.xml`/`dependencies.md` reports, and the config submodule relationship.

Chords CI/CD workflow guidance. Use for authoring or reviewing GitHub Actions workflows under `.github/workflows`: Ubuntu/Windows builds, license-report and version-increment guards, Gradle wrapper validation, and artifact publishing.

Reviews Chords implementation changes for correctness, regressions, public API breaks, missing tests, and cross-module contract breaks. Use to review component, codegen, or build diffs. Read-only unless explicitly asked to run checks.

Chords code generation policy. Use for the ProtoData codegen plugins project, the codegen runtime library, generated MessageField/MessageOneof/MessageDef contracts, codegen correctness tests, and Protobuf declarations with Kotlin extensions in proto-values.

Chords UI component implementation policy. Use for the class-based component model, application shell, input components, layouts, message forms, validation display, dropdown/table/entity components, and server-connected components across the core, proto, and client modules.

Reviews Chords documentation changes: KDoc comments, README.md files, .agents/project.md, AGENTS.md, skills, command examples, and architecture or module maps. Read-only unless explicitly asked to run checks.

Writes, edits, and restructures Chords documentation. Use when asked to create or update README.md files, .agents/project.md, AGENTS.md, skills, KDoc comments, or inline explanatory comments. Verifies claims against current code, tests, workflows, and build files.

Routes Chords implementation work to the area-specific engineering skill. Use for mixed component/codegen/build changes or when the owning area is unclear; otherwise prefer the narrowest specialist skill directly.

Chords security review guidance. Use for publishing-credential handling, GitHub Actions secrets, GPG-encrypted key files, dependency provenance, Gradle wrapper integrity, agent prompt/configuration safety under `.agents/**`, and accidental secret exposure in this public repository.

Chords test and verification policy. Use for test authoring and verification strategy across core, proto, proto-values, client, the codegen runtime, and codegen correctness tests, including Gradle verification commands.