Lean bullet-form standards with no concept-explanation padding; assumes Claude's competence and lets every token earn its place. Not below 3 because nothing reads as verbose or padded.

Names exact APIs and concrete patterns (setContent, collectAsStateWithLifecycle, StateFlow<UiState>, :feature:home, @Stable/@Immutable) plus a runnable check (./gradlew build); for an instruction-only standards skill the guidance is specific and actionable.

Sections are logically sequenced (layers -> modules -> UDF -> Compose -> anti-patterns) and capped by a verification checklist with a ./gradlew build checkpoint serving as the validation gate.

Body is a concise overview with detailed code split into clearly signaled, one-level-deep references (references/implementation.md, references/compose-standards.md), both confirmed to exist as real files.

Lists multiple concrete actions — "layering", "modularization", "Unidirectional Data Flow", plus "setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns" — matching the multi-action anchor.

Explicitly states both what ("Apply Clean Architecture layering, modularization, and Unidirectional Data Flow") and when ("Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns").

Covers natural terms a user would say for this domain ("Clean Architecture", "layers", "feature/core modules", "UDF"); technical but appropriate to the niche, not below the good-coverage anchor.

Android-specific Clean Architecture niche with distinct triggers (feature/core modules, UDF) makes it unlikely to fire for unrelated skills.