cmp-design-ruleslisted
Install: claude install-skill whinstudio/skills
# Design rules
A generated app starts black and white, on the system font, with no motion. These rules are for
the choices that replace that. A provided design always wins (`cmp-design-to-code`). Code rules
are in `cmp-code-rules`.
Paths are under `core/designsystem/src/commonMain/kotlin/<package>/core/designsystem/`. What exists
depends on how the app was generated:
- `theme/KtTheme.kt` exists: `shared/.../AppTheme.kt` only wraps it. Change the theme in `KtTheme` and
the palette.
- No `KtTheme.kt` (Theming off): `shared/.../AppTheme.kt` is a plain `MaterialTheme`. Put the scheme,
typography and shapes there and read only `MaterialTheme` (`cmp-design-to-code`, section 4).
- Blank app (no `component/` folder): there is no `KtText`, `KtIcon`, `ErrorContent` or
`ColorSchemeForTest`, and no `errorMessage` or `retry`. Use `Text` and `Icon`, add the strings you
need, and skip the rules and greps that name those.
## 1. State the read first
Before picking a value, write one line:
`Reading this as: <kind of app>, <audience>, <one or two mood words>, <brand inputs or none>.`
Colours, logo and type the app already has are input. With none, choose the accent's hue from the
kind of app and the mood, and say why in the read. If the read is truly ambiguous, ask one
question; in a headless run pick one and list it under `Assumptions`. A colour with no reason
behind it is the default you are trying to avoid.
What makes an app look generated: Material's stock lilac showing thro