Agent Skills › chrisbanes/skills › compose-component-design

compose-component-design

GitHub

用于设计或审查可复用的 Jetpack Compose 组件 API，涵盖修饰符参数、根布局放置、调用者提供的变量内容、布尔标志及可选内容等场景。

skills/compose-component-design/SKILL.md chrisbanes/skills

触发场景

设计可复用 Compose 组件 API 审查组件修饰符与布局策略处理调用者控制的视觉区域

安装

npx skills add chrisbanes/skills --skill compose-component-design -g -y

更多选项

不安装直接使用

npx skills use chrisbanes/skills@compose-component-design

指定 Agent (Claude Code)

npx skills add chrisbanes/skills --skill compose-component-design -a claude-code -g -y

安装 repo 全部 skill

npx skills add chrisbanes/skills --all -g -y

预览 repo 内 skill

npx skills add chrisbanes/skills --list

SKILL.md

Frontmatter

{
    "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

State the requested API concern and keep the edit within it. A focused slot review does not authorize unrelated modifier, naming, or cleanup changes.
State the component's invariant visual structure and identify every varying region, placement concern, and policy choice.
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.
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.
Keep simple conditional structure inline; extract only a coherent reusable contract.
Read the relevant focused reference below before editing public signatures.
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
Caller-controlled variable visual regions, optional content, primitive content parameters, or Boolean shape flags	Slot APIs
Animation belongs to the public component contract	Compose animations
State ownership changes while designing the component	Compose state and effects
Semantics or screenshot coverage is needed	Compose UI testing patterns

RED/GREEN agent scenarios

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.
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.
Counterexample: a private screen helper has one fixed child and no callers. GREEN keeps it simple instead of inventing slots for hypothetical reuse.
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.