kta-module

Scaffold new Gradle modules in Kotlin Android projects using project conventions.

4|Updated May 7, 2026
One-click install
npx skills add https://github.com/dantech0xff/dreams --skill kta-module
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kta-module
Source: https://github.com/dantech0xff/dreams/tree/main/.agents/skills/kta-module
Command: npx skills add https://github.com/dantech0xff/dreams --skill kta-module

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bootstrap a new Gradle module in any Kotlin Android project by guiding the user through choosing one of three module types — library module, feature module, or dynamic feature module — and by discovering the project's existing conventions before scaffolding, avoiding hardcoded patterns.

Core Features & Use Cases

  • Discovers project conventions (plugins, namespaces, sibling modules, version catalogs) to tailor scaffolding.
  • Presents a decision matrix and intake questions to determine the appropriate module type (library, feature, or dynamic feature).
  • Generates a scaffold with the selected Gradle setup, Android manifest defaults, and minimal wiring notes, stopping before app-level wiring.
  • Supports reuse across multi-project Android codebases and aligns with existing module patterns.

Quick Start

Answer the intake questions to scaffold a new module in your Kotlin Android project.

Frequently Asked Questions about kta-module

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

FAQPage Schema
How do I scaffold a new Gradle module in an Android project?

To scaffold a new Gradle module in an Android project, you answer intake questions about its purpose, consumers, navigation ownership, delivery, and rough size. The tool then generates skeleton files with the appropriate Gradle setup and Android manifest defaults based on your inputs.

What is the difference between a library, feature, and dynamic feature module in Android?

A library module contains shared code, a feature module encapsulates a distinct app functionality with navigation ownership, and a dynamic feature module enables on-demand delivery. A decision matrix and intake questions help determine the appropriate module type for your specific use case.

How do I ensure a new Android module follows existing project conventions?

To ensure a new Android module follows existing project conventions, the scaffolding process discovers your project's current plugins, namespaces, sibling modules, and version catalogs before generating files. This tailors the new module to match established patterns rather than applying hardcoded templates.

Can I use this scaffolding tool for multi-project Android codebases?

Yes, you can use this scaffolding tool for multi-project Android codebases. It explicitly supports reuse across multiple Android projects by discovering and aligning with each specific codebase's existing conventions and module patterns during the generation process.

Does the module scaffolding handle app-level wiring for navigation?

No, the module scaffolding does not handle app-level wiring for navigation. It generates the module scaffold with Gradle setup and manifest defaults, providing minimal wiring notes but intentionally stopping before completing the app-level integration.

What inputs do I need to provide to create a dynamic feature module?

To create a dynamic feature module, you need to provide intake information including the module's purpose, its consumers, navigation ownership, delivery method, and rough size. This data guides the validation and generation of the appropriate module skeleton.