compose-component-design · git:20260818.ded78ab · 2026-08-18 · sha256 7ada42bf996d4edc
compose-component-design git:20260818.ded78abA
Immutable. This exact content never changes and is served at /api/v1/blob/7ada42bf996d4edc.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_jozq4b34vxk74h7t/7ada42bf996d4edcd225e5b5aa2dfda8d1126a0d8de999857750290935c0e649.json
Then /plugin install compose-component-design@markdownregistry-jozq4b34vxk74h7t in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
--- name: compose-component-design description: Use when designing or reviewing reusable Jetpack Compose component APIs with modifier parameters, root layout placement, caller-provided variable content, primitive content parameters, optional content, or boolean shape flags. --- # Compose component design ## Core principle Make reusable components caller-placeable and caller-composable: the component owns its invariant structure while callers retain placement, content, and policy choices that vary by use. ## Procedure 1. State the requested API concern and keep the edit within it. A focused slot review does not authorize unrelated modifier, naming, or cleanup changes. 2. State the component's invariant visual structure and identify every varying region, placement concern, and policy choice. 3. When root placement is part of the requested work or a broad component API design, accept and apply a caller modifier at the component root unless a concrete API boundary makes another placement correct. 4. Represent caller-controlled, unconstrained visual regions with slots rather than proliferating primitive content parameters or Boolean shape flags. Keep semantic and design-system constraints as primitive parameters. 5. Keep simple conditional structure inline; extract only a coherent reusable contract. 6. Read the relevant focused reference below before editing public signatures. 7. Finish with no edit when the existing API already satisfies the requested concern. Otherwise finish when callers can position the component, supply variable content, and understand ownership without hidden switches. ## Topic router | Signal | Read | |---|---| | Modifier parameter, root layout placement, modifier ordering, or conditional layout wrappers | [Modifier and layout](references/modifier-layout.md) | | Caller-controlled variable visual regions, optional content, primitive content parameters, or Boolean shape flags | [Slot APIs](references/slot-apis.md) | | Animation belongs to the public component contract | [Compose animations](../compose-animations/SKILL.md) | | State ownership changes while designing the component | [Compose state and effects](../compose-state-and-effects/SKILL.md) | | Semantics or screenshot coverage is needed | [Compose UI testing patterns](../compose-ui-testing-patterns/SKILL.md) | ## RED/GREEN agent scenarios 1. RED exposes `title: String`, `icon: ImageVector?`, and several display flags for a reusable card. GREEN keeps invariant chrome and gives callers the variable regions as named slots. 2. Novel case: a component needs both a root modifier and caller-supplied trailing content. GREEN applies the modifier at the root and supplies a trailing slot without leaking the component's `RowScope`; reserve a scope receiver for a region whose child layout is deliberately caller-controlled. 3. Counterexample: a private screen helper has one fixed child and no callers. GREEN keeps it simple instead of inventing slots for hypothetical reuse. 4. Focused counterexample: a status label intentionally maps a semantic enum to fixed copy, and the task asks only whether it needs slots. GREEN leaves the workspace unchanged instead of adding an unrelated root modifier.