android-setup

Bootstrap Android projects with Gradle Kotlin DSL and version catalogs.

14|Updated Mar 14, 2026

Search Tags:#android #gradle #project-setup #build-automation #version-catalog #kotlin-dsl #module-structure

Ready to run

npx skills add https://github.com/piyushverma0/android-agent-skills --skill android-setup

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: android-setup
Source: https://github.com/piyushverma0/android-agent-skills/tree/main/skills/android-setup
Command: npx skills add https://github.com/piyushverma0/android-agent-skills --skill android-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Android project initialization and environment setup for AI agents ensures consistent builds and reduces setup time by enforcing Kotlin DSL, version catalogs, and standardized SDKs across new projects and multi-module setups.

Core Features & Use Cases

Enforces Kotlin DSL build files (build.gradle.kts) and Kotlin 2.0+.
Uses a single source of truth via libs.versions.toml for versions; namespace declaration for every module; KSP instead of kapt.
Use Case: When starting a new Android project or adding a new feature module, agent can auto-generate consistent scaffolding, Gradle configs, and module structure.

Quick Start

Create a new Android project skeleton with Kotlin DSL build files, libs.versions.toml, minSdk 24, targetSdk 35, compileSdk 35, and a declared namespace for each module.

Frequently Asked Questions about android-setup

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

FAQPage Schema

How do I set up an Android project with Kotlin DSL and version catalogs?▼

To set up an Android project with Kotlin DSL, you bootstrap standardized build.gradle.kts files and enforce a single libs.versions.toml file for dependencies. This ensures consistent module namespaces and SDK configurations across app, core, and feature layers.

What is the best way to structure a multi-module Android project?▼

The best way to structure a multi-module Android project is by enforcing standardized Gradle Kotlin DSL across app, core, and feature layers. This approach declares a namespace for every module and uses a central version catalog to reduce misconfigurations.

Does Android project setup require KSP instead of kapt for Kotlin 2.0?▼

Yes, modern Android project setup requires KSP instead of kapt when targeting Kotlin 2.0+. Enforcing KSP over kapt ensures better build performance and compatibility with the standardized Gradle Kotlin DSL configuration.

Can I use this Gradle Kotlin DSL setup for existing Android apps?▼

Yes, you can use this Gradle setup for existing apps when adding new feature modules. It auto-generates consistent scaffolding, Gradle configs, and module structures that meet minSdk 24, targetSdk 35, and AGP 8.5.0+ requirements.

Why does my Android build fail without a libs.versions.toml file?▼

Your Android build requires a libs.versions.toml file because this setup enforces a single source of truth for version management. Using this version catalog alongside Kotlin DSL prevents dependency misconfigurations across multi-module architectures.

What SDK versions are enforced when bootstrapping Android projects?▼

Bootstrapping Android projects enforces minSdk 24, targetSdk 35, and compileSdk 35. These standardized SDK configurations are applied automatically across all modules to ensure consistent build environments.