android-gradle-logic

Conseils d'expert pour configurer une logique de build Gradle évolutive à l'aide de plugins de convention et de catalogues de versions.

npx skills add https://github.com/livekit/client-sdk-android --skill android-gradle-logic

Android Gradle Build Logic & Convention Plugins

This skill helps you configure a scalable, maintainable build system for Android apps using Gradle Convention Plugins and Version Catalogs, following the "Now in Android" (NiA) architecture.

Goal

Stop copy-pasting code between build.gradle.kts files. Centralize build logic (Compose setup, Kotlin options, Hilt, etc.) in reusable plugins.

Project Structure

Ensure your project has a build-logic directory included in settings.gradle.kts as a composite build.

root/
├── build-logic/
│   ├── convention/
│   │   ├── src/main/kotlin/
│   │   │   └── AndroidApplicationConventionPlugin.kt
│   │   └── build.gradle.kts
│   ├── build.gradle.kts
│   └── settings.gradle.kts
├── gradle/
│   └── libs.versions.toml
├── app/
│   └── build.gradle.kts
└── settings.gradle.kts

Step 1: Configure settings.gradle.kts

Include the build-logic as a plugin management source.

// settings.gradle.kts
pluginManagement {
    includeBuild("build-logic")
    repositories {
        google()
        mavenCentral()
        gradlePluginPortal()
    }
}
dependencyResolutionManagement {
    repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)
    repositories {
        google()
        mavenCentral()
    }
}

Step 2: Define Dependencies in libs.versions.toml

Use the Version Catalog for both libraries and plugins.

[versions]
androidGradlePlugin = "8.2.0"
kotlin = "1.9.20"

[libraries]
# ...

[plugins]
android-application = { id = "com.android.application", version.ref = "androidGradlePlugin" }
android-library = { id = "com.android.library", version.ref = "androidGradlePlugin" }
kotlin-android = { id = "org.jetbrains.kotlin.android", version.ref = "kotlin" }
# Define your own plugins here
nowinandroid-android-application = { id = "nowinandroid.android.application", version = "unspecified" }

Step 3: Create a Convention Plugin

Inside build-logic/convention/src/main/kotlin/AndroidApplicationConventionPlugin.kt:

import com.android.build.api.dsl.ApplicationExtension
import org.gradle.api.Plugin
import org.gradle.api.Project
import org.gradle.kotlin.dsl.configure

class AndroidApplicationConventionPlugin : Plugin<Project> {
    override fun apply(target: Project) {
        with(target) {
            with(pluginManager) {
                apply("com.android.application")
                apply("org.jetbrains.kotlin.android")
            }

            extensions.configure<ApplicationExtension> {
                defaultConfig.targetSdk = 34
                // Configure common options here
            }
        }
    }
}

Don't forget to register it in build-logic/convention/build.gradle.kts:

gradlePlugin {
    plugins {
        register("androidApplication") {
            id = "nowinandroid.android.application"
            implementationClass = "AndroidApplicationConventionPlugin"
        }
    }
}

Usage

Apply your custom plugin in your modules (e.g., app/build.gradle.kts):

plugins {
    alias(libs.plugins.nowinandroid.android.application)
}

This drastically cleans up module-level build files.

Plus de skills de livekit

android-coroutines
livekit
Implémenter et réviser les coroutines Kotlin sur Android : configurer les CoroutineScopes, gérer les Dispatchers, exposer StateFlow/SharedFlow depuis les ViewModels, collecter avec…
official
livekit-agents
livekit
We need to translate the given English text into French, preserving the name "livekit-agents" if it appears. The text is a description of an agent skill. The instruction says to translate only the text inside <text>, and not include the name unless it appears in the source text. The name "livekit-agents" is not in the provided text, so we don't include it. We must preserve product names, protocol names, URLs, numbers, technical terms. So "LiveKit Cloud", "LiveKit Inference", "API keys" should remain as is or translated? "LiveKit Cloud" is a product name, so keep as is. "LiveKit Inference" also product name. "API keys" is a technical term, but in French it's often "clés API" but the instruction says preserve technical terms? It says "preserve product names, protocol names, URLs, numbers, and technical terms." So we should keep "API keys" as is? Or translate? Typically "API keys" is a technical term that might be kept in English in
official
livekit-simulations
livekit
Générer des scénarios de test ciblés pour un agent vocal ou de chat LiveKit et les exécuter sous forme de simulations — localement, à partir du code propre de l'agent et de ce que l'utilisateur souhaite…
official
gradle-build-performance
livekit
Déboguer et optimiser les performances de construction Android/Gradle. À utiliser lorsque les builds sont lents, pour enquêter sur les performances CI/CD, analyser les scans de build, ou identifier…
official