kmp-gradle

Standardize Kotlin Multiplatform Gradle configuration with convention plugins.

1|Updated Nov 26, 2025
One-click install
npx skills add https://github.com/niltsiar/kotlin_multiplatform_pokedex --skill kmp-gradle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kmp-gradle
Source: https://github.com/niltsiar/kotlin_multiplatform_pokedex/tree/main/.agents/kmp-gradle
Command: npx skills add https://github.com/niltsiar/kotlin_multiplatform_pokedex --skill kmp-gradle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Gradle configuration for Kotlin Multiplatform projects can be verbose and repetitive; this skill provides a set of convention plugins to standardize module setup, targets, and build workflows.

Core Features & Use Cases

  • Centralized conventions for KMP module structure and target configuration.
  • Auto-configuration of targets (Android, JVM, iOS) and standard testing.
  • Clear workflows for creating feature modules, managing dependencies, and troubleshooting builds.

Quick Start

Create a new feature module and apply the standard convention plugins to enable KMP targets and build logic.

Frequently Asked Questions about kmp-gradle

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize Kotlin Multiplatform Gradle configuration across modules?

Standardize Kotlin Multiplatform Gradle configuration by applying convention plugins that enforce a 5-module structure, auto-configure targets like Android and iOS, and manage dependencies via version catalogs for repeatable project setups.

What is the best way to create a new feature module in a Kotlin Multiplatform project?

Create a new feature module by applying the standard convention plugins, which automatically enable Kotlin Multiplatform targets and apply the centralized build logic for consistent module structure and testing workflows.

How do I manage Android, JVM, and iOS targets in a Kotlin Multiplatform build?

Manage Android, JVM, and iOS targets through centralized convention plugins that auto-configure platform-specific settings and standard testing, ensuring consistent target management across the multiplatform project.

Why does my Kotlin Multiplatform Gradle build fail with inconsistent dependencies?

Kotlin Multiplatform Gradle builds often fail due to inconsistent dependencies; this is resolved by enforcing version catalog discipline and applying convention plugins to standardize module setup and dependency declarations.

Does this Kotlin Multiplatform setup support custom Gradle build logic?

Yes, the setup supports custom Gradle build logic through convention plugins that standardize module creation and target management while maintaining version catalog discipline for the 5-module structure.

When do I need convention plugins for Kotlin Multiplatform projects?

Use convention plugins for Kotlin Multiplatform projects when you need to eliminate verbose, repetitive Gradle configuration and enforce a standardized 5-module structure across Android, JVM, and iOS targets.