Kotlin Engineering

Kotlin Engineering adds Kotlin and Gradle procedures to Software Engineering. Use it for domain values, public APIs, application adapters, review, and focused compiler evidence. IntelliJ plugin mechanics belong to the IntelliJ specialty.

Skills

Skill	Purpose
`kotlin-design-practices`	Own domain invariants, branches, APIs, and changes across callers.
`kotlin-application-stack`	Use serialization, Ktor, Clikt, GraalVM, and OpenTelemetry adapters.
`kotlin-review`	Find lost invariants and invalid states in a read-only review.
`negative-capability-proof`	Prove that named illegal calls fail under the compiler.
`kotlin-gradle-validation`	Run focused Gradle tasks and interpret native reports.
`gradle-performance-engineering`	Measure Gradle behavior through Build Scan evidence.

Domain proofs

Use constrained values for meaningful scalars. Use sealed hierarchies for finite alternatives. Handle closed cases with exhaustive when expressions. Keep unchecked construction under the invariant’s owner. Compiler success does not prove an external effect or concurrent behavior. Keep compiler rejection, runtime evidence, and installed host results separate.

Hooks and Kast

The plugin selects kotlin-engineering-context, gradle-check-green, gradle-wrapper-integrity, and kotlin-horizontalization-check. The host still owns hook trust and delivery. The plugin also declares its existing Kast MCP connection. Kast owns runtime installation and workspace discovery. A fresh semantic query supplies stronger evidence than plugin installation alone. The plugin manifest owns these declarations. The Kotlin instructions own the shared Kotlin rules.

Plugins

Contracts

Skills

Domain proofs

Hooks and Kast

​Skills

​Domain proofs

​Hooks and Kast

Skills

Domain proofs

Hooks and Kast