Design System Governance Rules

This skill ensures that any AI agent or developer modifying the UI adheres to the professional standards defined for the project, following the Official Compose Component API Guidelines.

1. Architectural Principles & Boundaries

• Statelessness: Every MM* component MUST be stateless. No internal remember { mutableStateOf(...) }.
• API Parameter Order: Following the official Android standards, parameters MUST follow this order:
  1. Required parameters: Those without default values (e.g., onClick, text).
  2. Modifier: modifier: Modifier = Modifier MUST be the first optional parameter.
  3. Optional parameters: Other parameters with default values.
  4. Trailing Lambda: If the component accepts content, the Composable lambda MUST be the last parameter.
• Typographic Boundary: Use MMText exclusively for typography in feature screens.

2. Accessibility (A11y), Adaptive & Scaling

• Universal RTL: Use start/end exclusively. No left/right. Directional icons MUST be mirrored.
• Scaling: Support 200% font scaling via sp. Use wrapContentHeight() or minHeight in containers.
• Touch Targets: Minimum 48x48dp via Modifier.minimumInteractiveComponentSize().
• Adaptive Navigation: Use NavigationSuiteScaffold to handle Bar/Rail transitions based on Window Size Classes.
• Scaling SSOT: User visual scale (DataStore) must be applied via MMDensityProvider, separating font scaling from structural density.