android-gradle-logic

Manage Android Gradle build logic with convention plugins and version catalogs.

119|14|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/rcosteira79/android-skills --skill android-gradle-logic-rcosteira79
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: android-gradle-logic
Source: https://github.com/rcosteira79/android-skills/tree/main/skills/android-gradle-logic
Command: npx skills add https://github.com/rcosteira79/android-skills --skill android-gradle-logic-rcosteira79

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill centralizes and standardizes Android Gradle build logic, eliminating repetitive configuration across modules and improving maintainability.

Core Features & Use Cases

  • Convention Plugins: Encapsulate common build configurations (e.g., Android app/library settings, Compose setup) into reusable Kotlin plugins.
  • Composite Builds: Integrate the build-logic directory as a separate composite build for cleaner separation and management.
  • Version Catalogs: Define and manage dependencies and plugins centrally in libs.versions.toml.
  • Use Case: Refactor a project with multiple modules to use convention plugins for applying compileSdk, minSdk, and Compose features, reducing boilerplate in each module's build.gradle.kts.

Quick Start

Apply the myapp.android.application plugin to your app module's build.gradle.kts file.

Frequently Asked Questions about android-gradle-logic

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

FAQPage Schema
How do I centralize Android Gradle build logic across multiple modules?

Centralize Android Gradle build logic by using convention plugins to encapsulate common configurations like compileSdk and minSdk into reusable Kotlin plugins, eliminating repetitive module setup across your project.

What are Gradle convention plugins and how do they work with Kotlin DSL?

Gradle convention plugins are custom Kotlin plugins that encapsulate shared build configurations. They work with Kotlin DSL by allowing you to define and apply standardized Android application and library settings across modules.

How do I manage dependencies centrally using a Gradle version catalog?

Manage dependencies centrally by defining and configuring them in a `libs.versions.toml` version catalog file. This approach standardizes dependency versions and plugin management across your entire Android project.

Does this Android build logic approach require Kotlin DSL and composite builds?

Yes, this approach requires Kotlin DSL to define custom Gradle plugins and uses composite builds to integrate the `build-logic` directory as a separate build for cleaner project separation.

What is the best way to standardize Jetpack Compose integration in a multi-module project?

The best way to standardize Jetpack Compose integration is to encapsulate the Compose setup within a reusable convention plugin, which then applies the necessary configuration to your Android modules consistently.

Can I use composite builds to separate my Android build-logic directory?

Yes, you can integrate the `build-logic` directory as a separate composite build. This provides a cleaner separation of build logic from your application code and improves overall project maintainability.