create-feature-module

Generate API and implementation modules with navigation keys for Android projects.

343|68|Updated Jun 14, 2017
One-click install
npx skills add https://github.com/MartinStyk/AndroidApkAnalyzer --skill create-feature-module
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-feature-module
Source: https://github.com/MartinStyk/AndroidApkAnalyzer/tree/main/.claude/skills/create-feature-module
Command: npx skills add https://github.com/MartinStyk/AndroidApkAnalyzer --skill create-feature-module

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the manual overhead and inconsistency involved in setting up new feature modules in a multi-module Android project, ensuring all new screens follow the established architecture and navigation patterns.

Core Features & Use Cases

  • Boilerplate Generation: Automatically structures API and implementation modules with correct Gradle configurations.
  • Navigation Integration: Sets up NavKeys and EntryProviders to ensure seamless integration with the project's navigation graph.
  • Consistency Enforcement: Standardizes package naming, module structure, and documentation requirements across the codebase.

Quick Start

Use the create-feature-module skill to generate a new feature module named profile including all necessary navigation and build configuration files.

Frequently Asked Questions about create-feature-module

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

FAQPage Schema
How do I create a new feature module in a multi-module Android project?

To create a new feature module, you need to generate separate API and implementation modules with correct Gradle configurations. This standardizes package naming and module structure to ensure consistent architectural scaling across the codebase.

How do I integrate a new Jetpack Compose screen into an existing navigation graph?

Integrating a Jetpack Compose screen requires setting up specific NavKeys and EntryProviders. This ensures the new feature module connects seamlessly to the project's established navigation patterns without manual graph updates.

What is the best way to enforce consistent Gradle conventions across new Android modules?

The best way to enforce Gradle consistency is to standardize the feature module creation process itself. Automatically generating build configurations and documentation ensures all new screens adhere to project-specific architectural standards.

Does this module scaffolding approach work with Jetpack Compose and Navigation 3?

Yes, this scaffolding approach explicitly works with Jetpack Compose and Navigation 3. It generates the required navigation keys and entry providers to ensure seamless integration with the project's navigation graph.

Why do I need separate API and implementation modules for Android feature development?

Separating API and implementation modules standardizes architectural scaling and enforces boundaries within multi-module Android projects. This structure ensures features expose only necessary contracts while hiding internal logic, reducing build times and coupling.