gradle-expert

Optimize Gradle builds and dependency resolution for Kotlin Multiplatform modules.

1.6k|218|Updated Jan 11, 2023

Search Tags:#troubleshooting #gradle #multiplatform #build-optimization #version-catalog #dependency-resolution

Ready to run

npx skills add https://github.com/vitorpamplona/amethyst --skill gradle-expert-vitorpamplona

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gradle-expert
Source: https://github.com/vitorpamplona/amethyst/tree/main/.claude/skills/gradle-expert
Command: npx skills add https://github.com/vitorpamplona/amethyst --skill gradle-expert-vitorpamplona

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build system optimization, troubleshooting, and dependency management for AmethystMultiplatform's four-module Kotlin Multiplatform architecture, consolidating best practices and actionable guidance.

Core Features & Use Cases

Centralized version catalog and dependency governance across modules (quartz, commons, amethyst, desktopApp)
Platform-specific dependency handling (Android vs Desktop) for JNI, JNA, and Compose variants
Structured troubleshooting workflows, build profiling, and performance improvements

Quick Start

Run the analyze-build-time.sh script from the repository root to generate a build performance report.

Frequently Asked Questions about gradle-expert

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

FAQPage Schema

How do I optimize Gradle builds for Kotlin Multiplatform projects?▼

Gradle build optimization for Kotlin Multiplatform involves profiling build times, enforcing consistent Kotlin and Compose versions across modules, and applying centralized version catalog governance to reduce configuration conflicts and improve build speeds.

How do I resolve platform-specific dependency variant conflicts in Gradle?▼

Resolving platform-specific dependency variant conflicts in Gradle requires selecting correct variants like jni-jvm for desktop and jni-android for Android, ensuring modules pull appropriate artifacts for their target architecture.

What is a Gradle version catalog and when do I need it for multi-module architectures?▼

A Gradle version catalog centralizes dependency governance across multi-module architectures, ensuring consistent library versions and platform-specific dependency handling across Android, desktop, and shared commons modules.

Can I use a single Gradle configuration for both Android and desktop JNI dependencies?▼

You cannot use a single configuration for both Android and desktop JNI dependencies; you must enforce correct dependency variant usage, separating jni-jvm and jni-android artifacts to match platform targets.

What's the best way to troubleshoot multi-module Gradle dependency resolution failures?▼

The best way to troubleshoot multi-module Gradle dependency resolution failures is to run the analyze-build-time script to generate a performance report, then verify platform-specific variant selection and version catalog consistency.

Why does my Gradle build fail when switching between Android and desktop Compose variants?▼

Gradle builds fail when switching Compose variants due to inconsistent Kotlin and Compose versions across modules; enforcing a centralized version catalog and correct dependency variant usage resolves these configuration mismatches.