🪟 scrumia-material3

What it is responsible for

Eight rules that shape an Android or Kotlin Multiplatform Mobile surface so the UI stays Material 3 and does not reinvent it. Compose is the default toolkit; Views is an explicit choice with a stated justification. Tokens come from MaterialTheme.colorScheme, Typography, Shapes, elevation, and the state-layer system — never from hex literals. Components come from androidx.compose.material3.* (or its View-side equivalent) — never built from primitives. Dynamic color is the default on Android 12+; a static brand palette requires a stated justification. Touch targets clear 48dp × 48dp. Body text hits 4.5:1 contrast, large text 3:1. Every icon-only control carries a contentDescription. Ships a scrumia-material3 reference skill and a material3-audit skill that measures a project against the eight.

What it refuses

A View-based widget without a stated justification. A hardcoded color, typography step, shape corner, elevation or state-layer value. A custom Button, Card, AppBar, NavigationBar, ListItem, Dialog or Snackbar built from primitives. A static brand palette on Android 12+ without a stated justification. An interactive control below 48dp. Body text below 4.5:1 or large text below 3:1. An IconButton without a TalkBack label. A Material 3 lane reaching for a CSS custom property, or a scrumia-design lane reaching for a Material 3 token — the two are not interchangeable.

The assumption it makes

Assumes Material 3 is the UI system, not a recommendation, and states every rule in the system's terms. Tokens and components are pulled from the Material 3 source, not reinvented per project. Costs the friction of MaterialTheme.colorScheme over a hardcoded hex on a one-screen project, pays back in a UI that ships with system-level consistency across devices and theming.

Its skills

• material3-audit

Tags

• scrumia
• material3
• material-design
• android
• compose
• kotlin-multiplatform
• ui
• accessibility

What it plugs into

Install it

Read the source on GitHub