thalarch-compose-uilisted
Install: claude install-skill LUC4N3X/antigravity-thalarch
# Thalarch Compose UI
A Compose screen is both a rendered product surface and a stateful runtime system. Treat both as
acceptance criteria.
## 1. Extract before inventing
Before redesigning an existing app, inspect:
- theme/color/typography tokens;
- reusable components;
- spacing/radius/divider patterns;
- navigation and top-level screen structure;
- dark/light/dynamic-color behavior;
- screenshots or supplied references;
- wording/localization conventions.
Use `thalarch-design-system` when the visual language is unclear or the redesign is substantial.
Preserve stable product identity unless the user explicitly asks to change it.
## 2. Write a compact visual contract
For a meaningful redesign, establish:
- hierarchy;
- density;
- grouping;
- primary interaction;
- one distinctive product-native visual idea;
- responsive rules;
- accessibility constraints;
- explicit anti-patterns.
Do not implement a pile of independently styled cards and call it a design system.
## 3. State and recomposition discipline
Inspect:
- state ownership and hoisting;
- stable keys in lazy content;
- `remember` / `rememberSaveable` lifetime;
- `derivedStateOf` only when derivation cost/recomposition semantics justify it;
- effects and lifecycle ownership;
- expensive mapping/sorting/parsing inside composables;
- allocation-heavy objects created during frequent recomposition.
A visually correct screenshot does not prove state correctness or performance.
## 4. Interaction quality
Control