Slash Command

/add-screen

From cc-mobile-android

Add a single Compose screen with its ViewModel, UiState, and preview — no backend plumbing.

Invocation

How this command is triggered — by the user, by Claude, or both

Slash command

/cc-mobile-android:add-screen <ScreenName> [feature-package]

Model invocable

No pre-commands

Tool Access

This command is limited to the following tools:

ReadWriteEditGrepGlobBashTask

Context Preview

The summary Claude sees in its command listing — used to decide when to auto-load this command

Add a new Compose screen named **$ARGUMENTS**. This command is for presentation-layer-only work — no new repository, use case, or API.

Steps:

1. Read `.claude/skills/compose-ui/SKILL.md` and the nearest existing screen in the project for structural reference.
2. Figure out where the screen belongs. If the user named a feature package, put it there; otherwise ask.
3. Create these files:

   

4. Wire it into the NavGraph (update `MainNavGraph.kt` or equivalent). If the navigation API uses typed routes, define the route.
5. At least one `@Preview` with a representative state — use `PreviewP...

Command Content

29 lines · ~373 tokens

Stats

LanguageShell

Parent stars0

MaintenanceGood

Last CommitApr 24, 2026

Actions

View Source View Plugin View on GitHub View README

Stats

Actions

Tags

Add a new Compose screen named $ARGUMENTS. This command is for presentation-layer-only work — no new repository, use case, or API.

Steps:

Read .claude/skills/compose-ui/SKILL.md and the nearest existing screen in the project for structural reference.
Figure out where the screen belongs. If the user named a feature package, put it there; otherwise ask.

Create these files:

<feature>/presentation/<screen>/
├── <Screen>UiState.kt       # sealed interface with Loading/Error/Success at minimum
├── <Screen>Action.kt        # user actions
├── <Screen>ViewModel.kt     # @HiltViewModel, StateFlow<UiState>
├── <Screen>Screen.kt        # Route + stateless Screen + Preview(s)

Wire it into the NavGraph (update MainNavGraph.kt or equivalent). If the navigation API uses typed routes, define the route.
At least one @Preview with a representative state — use PreviewParameterProvider if there are multiple distinct states worth seeing.
Verify: ./gradlew :app:assembleDebug.
Report the files you created, the route you added, and any next steps (e.g. "hook up the real repository call").

Consider delegating the UI work to the android-ui-engineer subagent via the Task tool, especially for non-trivial screens.