amichne

Design OpenAPI component schemas with discriminated variants, constrained primitives, subtype/composition choices, nullability, examples, and invalid-state prevention.

Set up a repository for marketplace-driven AI tooling. Use when onboarding a new repo, refreshing a checked-in marketplace reference, installing core marketplace plugins, or documenting which configured marketplaces should be available by default.

Use when validation, authorization, normalization, or state checks produce facts later code must retain. Replace primitive contracts, flags, sentinel states, string protocols, and call-order conventions with proof-carrying values in any language.

Use when Kotlin work needs type-driven modeling, parse-dont-validate boundaries, semantic package layout, explicit failures, API review, or package cohesion checks.

Pkl engineering for typed configuration contracts, expressions, amendments, evaluation, formatting, tests, projects, dependencies, rendering, and packages. Use when a repository contains `.pkl` modules or `PklProject`, or when configuration behavior should be modeled and enforced with Apple Pkl.

Use when creating or validating referential plugin manifests, marketplace entries, primitive references, or payload-to-reference plugin conversions.

Use when a behavior, invariant, bug fix, contract, or refactor should be developed red-green-refactor and any shell-invokable check can provide focused executable proof.

Use when Kotlin work needs typed design discipline, invariant-oriented Kotlin standards, filesystem-backed evidence, Kast semantic tooling, Gradle validation, TDD, or PR-ready proof.

Use this skill when integrating Konditional into a codebase — whether you are a new user defining your first typed namespace or an enterprise team migrating from string-key flag systems. Covers namespace declaration, context modeling, evaluation, remote config loading, gradual rollout, shadow migration, and OpenFeature interoperability.

Produce type-driven, deterministic, test-proven Kotlin with strict boundary discipline. Use when writing code that handles untrusted input, domain modeling, data transformation, concurrent state, or API boundaries where correctness and compile-time safety are critical. Prefer over kotlin-architect when parse-don't-validate, determinism invariants, or typed error ADTs are the primary concern.

Provide in-depth technical review of Kotlin codebases and OpenAPI specifications with focus on system architecture, API design, type safety, maintainability, scalability, and enterprise concerns. Use when the user requests architectural review, API surface analysis, code critique, design assessment, or asks to identify weaknesses, complexity reduction opportunities, or improvement areas. Trigger on requests like "review my architecture", "assess my API design", "find weaknesses in this code", "critique this implementation", or "analyze this for enterprise readiness". Particularly valuable for library/framework design, public API review, and production system architecture validation.

Standardize editor-agnostic Kotlin/JVM development workflows using Language Server Protocol, Gradle wrapper commands, and JVM debugging. Use when setting up or troubleshooting Kotlin tooling in LSP-capable editors, validating Gradle build/test/run loops, or attaching debuggers to JVM app and test processes.

Route Kotlin and Gradle semantic work through Kast's fixed, typed CLI surface. Use when Codex needs to discover Kotlin .kt or .kts files, resolve symbol identity, inspect relationships or impact, collect diagnostics, perform plan-first semantic edits, or recover a typed Kast operation.

Kotlin semantic work in Gradle repositories. Use when an agent needs compiler-backed Kotlin `.kt` or `.kts` discovery, symbol identity, references, callers, diagnostics, source-index impact, semantic rename, typed scope mutation, or focused Gradle validation.

Applies the Diataxis framework to create or improve technical documentation. Use when being asked to write high quality tutorials, how-to guides, reference docs, or explanations, when reviewing documentation quality, or when deciding what type of documentation to create. Helps identify documentation types using the action/cognition and acquisition/application dimensions.