kmp-forge

Add a new :feature-<name> module (Compose screen + Orbit ViewModel + state + Koin module + Nav 3 destination + commonTest skeleton).

Search klibs.io for a KMP library, present matches, and add the chosen one to gradle/libs.versions.toml plus a target module.

Add a platform (desktop, web, or ios) to an existing kmp-forge project.

Add a new screen (Composable + Orbit ViewModel + state + Nav 3 destination) inside an existing :feature-<name> module.

Adopt the kmp-forge locked stack into an EXISTING Kotlin Multiplatform project — overlay docs/CI/conventions, then drive a reviewer-led refactor of code to the locked patterns.

Use this agent to generate a complete :feature-<name> module on the kmp-forge locked stack — Compose screen + Orbit ViewModel + state + Koin module + Nav 3 destination + commonTest skeleton. Trigger whenever a new feature module needs scaffolding in a kmp-forge project, whether invoked explicitly via /kmp-forge-add-feature or when the user asks for a new feature by name. <example> Context: User runs the add-feature command. user: "/kmp-forge-add-feature gallery" assistant: "I'll use the kmp-feature-builder agent to scaffold the :feature-gallery module." <commentary>Explicit command invocation — delegate module generation to kmp-feature-builder.</commentary> </example> <example> Context: User asks for a new feature in natural language. user: "Add a photo-detail screen as its own feature module" assistant: "I'll use the kmp-feature-builder agent to create the :feature-photo-detail module (Compose screen, Orbit ViewModel, Koin module, Nav 3 route)." <commentary>New feature module requested — kmp-feature-builder owns generation on the locked stack.</commentary> </example>

Use this agent to migrate an EXISTING Kotlin Multiplatform project's code onto the kmp-forge locked patterns, one layer at a time (DispatcherProvider, Result+DomainError, one-repo-per-type, Koin DI, Orbit state-only events, typed Nav 3, module deps, restrictive visibility, fakes-not-mocks, a11y/i18n). Write-capable; incremental; builds + re-greps to verify each layer. Trigger when refactoring an existing project onto the locked stack — invoked by /kmp-forge-adopt Phase B, or directly for a single layer. <example> Context: /kmp-forge-adopt Phase B drives the guided refactor layer by layer. user: "Phase B: migrate the dispatchers layer" assistant: "I'll use the kmp-migrator agent with layer=dispatchers to inject DispatcherProvider across :domain/:data/:feature-*." <commentary>Adopt Phase B — kmp-migrator executes exactly one layer, then builds + re-greps.</commentary> </example> <example> Context: User wants one layer migrated for a specific feature. user: "Convert feature-gallery to Orbit state-only events" assistant: "I'll use the kmp-migrator agent with layer=orbit target=feature-gallery to remove postSideEffect and switch to consumable state slots." <commentary>Scoped single-layer migration — kmp-migrator owns the detect/transform/verify recipe.</commentary> </example>

Use this agent to review a diff, branch, or file in a kmp-forge-scaffolded project for locked-stack violations. Enforces Orbit state-only events, Koin constructor injection, typed Nav 3, Result+DomainError, DispatcherProvider, one-repo-per-type, fakes-not-mocks, secrets, and a11y/RTL rules. One line per finding, severity-tagged, no praise, no scope creep. <example> Context: Developer finished changes and wants a convention check before committing. user: "review my changes" assistant: "I'll use the kmp-reviewer agent to audit your diff against the locked stack." <commentary>Review request on the working diff — delegate to kmp-reviewer.</commentary> </example> <example> Context: A feature branch is ready to merge. user: "is this branch good to merge?" assistant: "Let me run the kmp-reviewer agent on the branch diff (git diff origin/main...HEAD)." <commentary>Branch-readiness check — kmp-reviewer enforces the locked-stack gates.</commentary> </example>

Author Architecture Decision Records (ADRs) for kmp-forge projects following the Michael Nygard format. Use when documenting a stack or architecture decision, adopting an opt-in library, superseding a prior decision, or when /kmp-forge-init asks about adding a non-default lib.

Author Conventional Commits in a kmp-forge-scaffolded project, where git-cliff generates the changelog and GitHub Release notes from commit prefixes. Use when committing changes in such a repo and deciding the correct type/scope and semver impact so the release notes categorize correctly, or when reviewing commit-message style against the project's git-cliff config.

Configure and run git-cliff to generate CHANGELOG.md and GitHub Release bodies from Conventional Commits in kmp-forge-scaffolded projects. Use when setting up changelog automation, releasing a new version, or troubleshooting changelog output.

Configure and ship release artifacts (APK/AAB, .ipa, desktop installers, web bundle) via GitHub Releases on v* tag push for kmp-forge projects. Use when setting up release CI, debugging release uploads, or planning artifact naming.

Author docs/MVP_SPEC.md for a kmp-forge project — interactive interview structure, section templates, and what makes a spec good vs vague. Used by the /kmp-forge-spec command.