Agent skill

Create Feature Module

by MartinStyk in MartinStyk/apk-analyzer

A skill your agent uses when creating a new feature module, screen, or feature area.

GPL-3.0Auto-check passedMobile

Install Create Feature Module

skills CLI

$ npx skills add MartinStyk/apk-analyzer --skill create-feature-module -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install MartinStyk/apk-analyzer create-feature-module --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/MartinStyk/apk-analyzer.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/create-feature-module .claude/skills/create-feature-module && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "create-feature-module" agent skill from https://github.com/MartinStyk/apk-analyzer/tree/develop/.claude/skills/create-feature-module into .claude/skills/create-feature-module/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-feature-module", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/MartinStyk/apk-analyzer/tree/develop/.claude/skills/create-feature-module

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add MartinStyk/apk-analyzer --skill create-feature-module -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install MartinStyk/apk-analyzer create-feature-module --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/MartinStyk/apk-analyzer.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/create-feature-module .agents/skills/create-feature-module && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "create-feature-module" agent skill from https://github.com/MartinStyk/apk-analyzer/tree/develop/.claude/skills/create-feature-module into .agents/skills/create-feature-module/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-feature-module", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add MartinStyk/apk-analyzer --skill create-feature-module -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install MartinStyk/apk-analyzer create-feature-module --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/MartinStyk/apk-analyzer.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/create-feature-module .cursor/skills/create-feature-module && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "create-feature-module" agent skill from https://github.com/MartinStyk/apk-analyzer/tree/develop/.claude/skills/create-feature-module into .cursor/skills/create-feature-module/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-feature-module", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/MartinStyk/apk-analyzer.git --path .claude/skills/create-feature-module

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add MartinStyk/apk-analyzer --skill create-feature-module -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install MartinStyk/apk-analyzer create-feature-module --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/MartinStyk/apk-analyzer.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/create-feature-module .gemini/skills/create-feature-module && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "create-feature-module" agent skill from https://github.com/MartinStyk/apk-analyzer/tree/develop/.claude/skills/create-feature-module into .gemini/skills/create-feature-module/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-feature-module", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install MartinStyk/apk-analyzer create-feature-module

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add MartinStyk/apk-analyzer --skill create-feature-module -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/MartinStyk/apk-analyzer.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/create-feature-module .github/skills/create-feature-module && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "create-feature-module" agent skill from https://github.com/MartinStyk/apk-analyzer/tree/develop/.claude/skills/create-feature-module into .github/skills/create-feature-module/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-feature-module", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add MartinStyk/apk-analyzer --skill create-feature-module -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install MartinStyk/apk-analyzer create-feature-module --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/MartinStyk/apk-analyzer.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/create-feature-module .opencode/skills/create-feature-module && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "create-feature-module" agent skill from https://github.com/MartinStyk/apk-analyzer/tree/develop/.claude/skills/create-feature-module into .opencode/skills/create-feature-module/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-feature-module", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: create-feature-module
GitHub stars: 368
Token cost: ~1.6k tokens
SKILL.md length: 336 words
Files: 1
Skills in repo: 18
Repo updated: Oct 5, 2026
First seen: Oct 7, 2026
Licence: GPL-3.0

At a glance

A skill your agent uses when creating a new feature module, screen, or feature area.

Works in 9 steps: Create API module → Create impl module → Create entry provider → …
Creating a new feature module
SKILL.md covers Step 1 — Create API module, Step 2 — Create impl module, Step 3 — Create entry provider and Step 4 — Create screen…, plus 6 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Create Feature Module is an agent skill from MartinStyk/apk-analyzer. Use when creating a new feature module, screen, or feature area. Triggered by phrases like "create feature", "add feature module", "new feature", "create a screen for", "add new screen".

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Mobile, covering Android development. It works with Gradle and Kotlin. The repository describes itself as: The most downloaded APK analysis app on Google Play. Detailed reports of every app on your device. No root, no ads, nothing leaves the phone. The licence is GPL-3.0.

When your agent uses it

Creating a new feature module
Tasks that involve Android development

Example prompts

“create feature”
“add feature module”
“new feature”
“/create-feature-module”

Workflow steps

9 steps, taken from the step headings in SKILL.md.

Create API module
Create impl module
Create entry provider
Create screen composable (placeholder)
Register in settings.gradle.kts
Add dependency in app/build.gradle.kts
Wire in app/src/main/kotlin/sk/styk/martin/apkanalyzer/ui/ApkAnalyzerApp.kt
If top-level destination (bottom nav tab)
Create module docs

What it can do on your machine

Read from SKILL.md and the folder at commit d807559. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are kotlin).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Create Feature Module loads about 1.6k tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 336 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~52
When it runs · the whole SKILL.md, loaded when a task matches: ~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from MartinStyk/apk-analyzer at commit d807559, republished under its GPL-3.0 licence (© MartinStyk). 336 words, ~1,609 tokens.

Download SKILL.mdSave it as .claude/skills/create-feature-module/SKILL.md (or your agent's skills folder).

name: create-feature-module
description: Use when creating a new feature module, screen, or feature area. Triggered by phrases like "create feature", "add feature module", "new feature", "create a screen for", "add new screen".

Create Feature Module

Given a feature name <name> (e.g., about):

Step 1 — Create API module

feature/<name>/api/build.gradle.kts

kotlin

plugins {
    alias(libs.plugins.apkanalyzer.feature.api)
}

android {
    namespace = "sk.styk.martin.apkanalyzer.feature.<name>.api"

    androidResources.enable = false
}

Drop the androidResources.enable line once this module gets its own res/ — most commonly in Step 8, when a top-level destination needs its tab-label string in feature/<name>/api/src/main/res/values/strings.xml.

feature/<name>/api/src/main/kotlin/sk/styk/martin/apkanalyzer/feature/<name>/api/<Name>NavKey.kt

kotlin

package sk.styk.martin.apkanalyzer.feature.<name>.api

import androidx.navigation3.runtime.NavKey
import kotlinx.serialization.Serializable

@Serializable
object <Name>NavKey : NavKey

If the NavKey needs parameters, use data class instead:

kotlin

@Serializable
data class <Name>NavKey(val id: String) : NavKey

Step 2 — Create impl module

feature/<name>/impl/build.gradle.kts

kotlin

plugins {
    alias(libs.plugins.apkanalyzer.feature.impl)
}

android {
    namespace = "sk.styk.martin.apkanalyzer.feature.<name>.impl"

    androidResources.enable = false
}

dependencies {
    api(projects.feature.<name>.api)
    // Add core module dependencies as needed:
    // implementation(projects.core.apps)
    // implementation(libs.coil.compose)
}

Drop the androidResources.enable line as soon as the screen has real UI copy and gets its own res/values/strings.xml — every user-facing string in this module's Composables must come from stringResource, so this almost always happens by the time Step 4's placeholder is replaced.

Step 3 — Create entry provider

feature/<name>/impl/src/main/kotlin/sk/styk/martin/apkanalyzer/feature/<name>/impl/navigation/<Name>EntryProvider.kt

Without navigation (self-contained screen):

kotlin

package sk.styk.martin.apkanalyzer.feature.<name>.impl.navigation

import androidx.navigation3.runtime.EntryProviderScope
import androidx.navigation3.runtime.NavKey
import sk.styk.martin.apkanalyzer.feature.<name>.api.<Name>NavKey
import sk.styk.martin.apkanalyzer.feature.<name>.impl.<Name>Screen

fun EntryProviderScope<NavKey>.<name>Entries() {
    entry<<Name>NavKey> {
        <Name>Screen()
    }
}

With navigation (back or to other screens):

kotlin

package sk.styk.martin.apkanalyzer.feature.<name>.impl.navigation

import androidx.navigation3.runtime.EntryProviderScope
import androidx.navigation3.runtime.NavKey
import sk.styk.martin.apkanalyzer.core.navigation.Navigator
import sk.styk.martin.apkanalyzer.feature.<name>.api.<Name>NavKey
import sk.styk.martin.apkanalyzer.feature.<name>.impl.<Name>Screen

fun EntryProviderScope<NavKey>.<name>Entries(navigator: Navigator) {
    entry<<Name>NavKey> {
        <Name>Screen(
            onBack = { navigator.goBack() },
        )
    }
}

Step 4 — Create screen composable (placeholder)

feature/<name>/impl/src/main/kotlin/sk/styk/martin/apkanalyzer/feature/<name>/impl/<Name>Screen.kt

kotlin

package sk.styk.martin.apkanalyzer.feature.<name>.impl

import androidx.compose.foundation.layout.Box
import androidx.compose.foundation.layout.fillMaxSize
import androidx.compose.runtime.Composable
import androidx.compose.ui.Alignment
import androidx.compose.ui.Modifier
import androidx.compose.ui.tooling.preview.Preview
import sk.styk.martin.apkanalyzer.core.uilibrary.components.Text
import sk.styk.martin.apkanalyzer.core.uilibrary.theme.ApkAnalyzerTheme

@Composable
internal fun <Name>Screen() {
    Box(
        modifier = Modifier.fillMaxSize(),
        contentAlignment = Alignment.Center,
    ) {
        Text(text = "<Name>")
    }
}

@Preview
@Composable
private fun <Name>ScreenPreview() {
    ApkAnalyzerTheme {
        <Name>Screen()
    }
}

Step 5 — Register in `settings.gradle.kts`

Add inside include(...):

kotlin

":feature:<name>:api",
":feature:<name>:impl",

Step 6 — Add dependency in `app/build.gradle.kts`

kotlin

implementation(projects.feature.<name>.impl)

Step 7 — Wire in `app/src/main/kotlin/sk/styk/martin/apkanalyzer/ui/ApkAnalyzerApp.kt`

Add import:

kotlin

import sk.styk.martin.apkanalyzer.feature.<name>.impl.navigation.<name>Entries

Add inside entryProvider { } block:

kotlin

<name>Entries()          // or <name>Entries(navigator) if Navigator is needed

Step 8 — If top-level destination (bottom nav tab)

Add to app/src/main/kotlin/sk/styk/martin/apkanalyzer/ui/navigation/TopLevelDestinations.kt:

Import the NavKey and add a NavigationBarItem to TOP_LEVEL_DESTINATIONS
Choose icons from ApkAnalyzerIcons
Add string resource in the api module: feature/<name>/api/src/main/res/values/strings.xml

Step 9 — Create module docs

Every feature carries one AGENTS.md at feature/<name>/AGENTS.md covering both its api and impl submodules (not two separate files — see feature/settings/AGENTS.md or feature/app-detail/AGENTS.md for the exact format: Purpose, Sub-modules, API module key types, Impl Structure, Key Patterns, Dependencies), plus a one-line CLAUDE.md pointer at the same level:

feature/<name>/CLAUDE.md

@AGENTS.md

If the feature starts as a placeholder screen (Step 4's stub), say so explicitly in the AGENTS.md purpose line — e.g. "Status: stub/placeholder — not yet implemented" (see feature/browse/AGENTS.md) — so a future agent doesn't assume real behavior exists. Update it once the feature is actually built out.

The root AGENTS.md does not list individual modules, so there is nothing to update there. Run ./gradlew validateAgentContext to confirm the new module has the AGENTS/CLAUDE pair it requires.

Naming Reference

Thing	Convention	Example
Module directory	kebab-case	`app-detail`
Gradle accessor	camelCase	`projects.feature.appDetail.impl`
Package segment	concatenated lowercase	`feature.appdetail.impl`
NavKey class	PascalCase + `NavKey`	`AppDetailNavKey`
Entry provider function	camelCase + `Entries`	`appDetailEntries`

Files

Just SKILL.md in .claude/skills/create-feature-module of MartinStyk/apk-analyzer.

Open the folder on GitHubat commit d807559

Compare with similar skills

Create Feature Module next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Create Feature Module compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Create Feature Module this skillMartinStyk/apk-analyzer	368	—	~1.6k	Automated safety check: Pass	GPL-3.0	2 days ago
Android Developmentdpconde/claude-android-skill	336	—	~1.7k	Automated safety check: Pass	MIT	10 mo ago
Diagnosing Compose StabilityrosuH/EasyWatermark	1.9k	1 repos	~3.3k	Automated safety check: Pass	Apache-2.0	yesterday
Claude Android NinjaDrjacky/claude-android-ninja	124	—	~5.2k	Automated safety check: Pass	Apache-2.0	8 days ago
Expo Brownfield Integrationmweinbach/agent-coworker	156	2 repos	~900	Automated safety check: Notes	Custom licence	yesterday
Build Foremannekomangaorg/Neko	2.8k	—	~807	Automated safety check: Pass	Apache-2.0	yesterday

Similar skills

Android Development
dpconde/claude-android-skill
Create production-quality Android applications following Google's official architecture guidance and NowInAndroid best practices.
336 GitHub stars~1.7k tokensUpdated 10 mo ago
MobileAuto-check passed
Diagnosing Compose Stability
rosuH/EasyWatermark
A skill your agent uses to diagnose Jetpack Compose stability problems by enabling and reading the Compose Compiler Reports (classes.txt, composables.txt, composables.csv, module.json).
1.9k GitHub starsUsed in 1 repo~3.3k tokens
MobileAuto-check passed
Claude Android Ninja
Drjacky/claude-android-ninja
Build and migrate Android apps with Kotlin, Jetpack Compose, MVVM, Hilt, Room 3 (KSP, SQLiteDriver, Flow/suspend DAOs), Navigation3, and multi-module Gradle.
124 GitHub stars~5.2k tokensUpdated 8 days ago
MobileAuto-check passed
Expo Brownfield Integration
mweinbach/agent-coworker
Helps add Expo and React Native to an existing native iOS or Android app, and choose between a prebuilt AAR or XCFramework and a fully integrated build.
156 GitHub starsUsed in 2 repos~900 tokens
MobileAuto-check: notes
Build Foreman
nekomangaorg/Neko
Optimizes Gradle build scripts, compilation times, and Android Studio sync performance.
2.8k GitHub stars~807 tokensUpdated yesterday
MobileAuto-check passed
Desktop And Build Footguns
maxrave-dev/kotlin-footguns
Desktop JVM and build traps: JNA natives, bundling, memory, packaging, code signing, R8, deep links, Gradle and CI releases.
1k GitHub stars~3.8k tokensUpdated 12 days ago
MobileAuto-check passed

Questions about Create Feature Module

What does Create Feature Module do?

A skill your agent uses when creating a new feature module, screen, or feature area. Create Feature Module is an agent skill from MartinStyk/apk-analyzer. Use when creating a new feature module, screen, or feature area.

When should I use Create Feature Module?

Create Feature Module fits situations like: creating a new feature module; tasks that involve Android development.

How do I install Create Feature Module in Claude Code?

Run `npx skills add MartinStyk/apk-analyzer --skill create-feature-module -a claude-code`. Or copy the skill folder (.claude/skills/create-feature-module in MartinStyk/apk-analyzer) into .claude/skills/create-feature-module in your project. Claude Code loads it when a task matches its description.

How do I install Create Feature Module in Codex?

Run `npx skills add MartinStyk/apk-analyzer --skill create-feature-module -a codex`. Or copy the skill folder (.claude/skills/create-feature-module in MartinStyk/apk-analyzer) into .agents/skills/create-feature-module in your project. Codex loads it when a task matches its description.

Can I use Create Feature Module in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add MartinStyk/apk-analyzer --skill create-feature-module -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/create-feature-module, .gemini/skills/create-feature-module, .github/skills/create-feature-module and .opencode/skills/create-feature-module in your project.

What does Create Feature Module need to run?

SKILL.md names no scripts, command-line tools or credentials: Create Feature Module is instructions for the agent only.

Does Create Feature Module access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Create Feature Module safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Create Feature Module use?

Create Feature Module is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Create Feature Module use?

About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Create Feature Module?

Skills that share tags, products or a category with Create Feature Module: Android Development (dpconde/claude-android-skill, 336 stars), Diagnosing Compose Stability (rosuH/EasyWatermark, 1.9k stars), Claude Android Ninja (Drjacky/claude-android-ninja, 124 stars) and Expo Brownfield Integration (mweinbach/agent-coworker, 156 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Create Feature Module?

MartinStyk (a GitHub user) maintains it in MartinStyk/apk-analyzer, which has 368 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 5, 2026.

Source: MartinStyk/apk-analyzer on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Create Feature Module

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Create Feature Module

Step 1 — Create API module

Step 2 — Create impl module

Step 3 — Create entry provider

Step 4 — Create screen composable (placeholder)

Step 5 — Register in settings.gradle.kts

Step 6 — Add dependency in app/build.gradle.kts

Step 7 — Wire in app/src/main/kotlin/sk/styk/martin/apkanalyzer/ui/ApkAnalyzerApp.kt

Step 8 — If top-level destination (bottom nav tab)

Step 9 — Create module docs

Naming Reference

Files

Compare with similar skills

Similar skills

More from MartinStyk/apk-analyzer

Related

Questions about Create Feature Module

Step 5 — Register in `settings.gradle.kts`

Step 6 — Add dependency in `app/build.gradle.kts`

Step 7 — Wire in `app/src/main/kotlin/sk/styk/martin/apkanalyzer/ui/ApkAnalyzerApp.kt`