菜单
Scaffold a new Chai design-system component the right way. Triggered by "new-chai-component", "/new-chai-component", "add a Chai component", or "create a C<Name>". Ensures tokens, ChaiTheme.colors, and @ChaiPreview instead of raw Material / hardcoded values.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Write or extend tests for the Chai repo. Triggered by "write a test", "add tests", "test this", or as the follow-up when a component/util lands without coverage. Local unit tests use JUnit 6 (Jupiter); Compose/UI behaviour is tested as instrumented tests. Picks the right source set and idioms; does not invent mocking/assertion libraries the catalog does not declare.
Find design-system violations in Chai source — raw Material components, hardcoded colors, bare .dp magic numbers, @Preview instead of @ChaiPreview. Triggered by "audit-design-system-usage", "/audit", or by checks/code-reviewer. This is the check the broken chailinter is meant to do. Reports; does not edit.
Verify the Chai project assembles. Triggered by "check-build", "/check-build", "does it build", or by checks as the assemble gate. Runs `./gradlew assembleDebug` only — no mutation, no formatting.
Run Android Lint on Chai and report. Triggered by "check-lint", "/check-lint", "run lint", or by checks as the lint gate. Runs `./gradlew lintDebug` only — reports the first violation, never edits.
Umbrella pre-PR gate for Chai. Triggered by "checks", "/checks", "run the checks", or by any agent that needs a green light before committing or opening a PR. Runs the design-system audit, Android Lint, unit tests, and a debug assemble, then reports a single pass/fail.
Produce a commit subject, branch name, and PR title that match Chai's conventions. Triggered by "commit-convention", "/commit-convention", "write a commit message", or by the gitter agent before committing or opening a PR.
| name | new-chai-component |
| description | Scaffold a new Chai design-system component the right way. Triggered by "new-chai-component", "/new-chai-component", "add a Chai component", or "create a C<Name>". Ensures tokens, ChaiTheme.colors, and @ChaiPreview instead of raw Material / hardcoded values. |
You add a component to the chai library so it matches the design system. Components live in chai/src/main/java/com/droidconke/chai/components/ (or icons/, images/ as appropriate), named C<Name> in a C<Name>s.kt file when grouping a family.
Grep for the name) and isn't an empty stub already present (CCards.kt, CTabs.kt, etc. are stubs to fill, not new files to create).ChaiColors, add it there first, in both ChaiLightColorPalette and ChaiDarkColorPalette.ChaiTheme.colors / LocalChaiColorsPalette, NOT MaterialTheme.colorScheme and NOT hardcoded Color(0x…). (The current components wrongly read the Material scheme — see docs/tech/findings.md; do not copy that pattern.)Space* for Modifier.padding(...) and the Spacer*() composables (Spacer5(), Spacer15(), Spacer30()) for gaps in rows/columns. Never write a bare Space5 statement — it's a Dp, it renders nothing.CShapes. Type uses ChaiTheme.typography.onClick/state first, then modifier: Modifier = Modifier, then content. Keep parameters minimal; expose only what consumers need.private/internal.Add @ChaiPreview (not @Preview) previews for light and dark, wrapped in ChaiTheme { }, and make the preview functions private.
@ChaiPreview
@Composable
private fun C<Name>Preview() {
ChaiTheme { C<Name>( … ) }
}
audit-design-system-usage skill — confirm no raw Material / hardcoded color slipped in.checks skill — lint + tests + assemble.chaidemo so the component is actually exercised (the demo currently under-covers components).commit-convention (atomic, by layer: token change → component → demo).