Android M3 Design Study

Agent workflow

1. Confirm level — Intermediate = comfortable with layouts/themes/Fragments; focus on roles, states, a11y, not “what is a TextView.”
2. Point to reference.md — Full 2-week outline, resources, habits, terminology.
3. Assign one concrete deliverable per request (e.g. “color role map for one screen,” “type scale audit,” “a11y pass on one fragment”).
4. Respect project policy — No unwarranted UI edits; study outputs are notes, diagrams, or proposals unless the user approves changes.

Quick spine (detail in reference.md)

Output expectations

For study sessions, prefer:

• A short checklist the user can reuse.
• One prioritized “next experiment” (e.g. audit themes.xml roles only).
• Links to official Android / Material docs—not unvetted blogs.

Guardrails

• Do not conflate web CSS patterns with Android theme attributes without mapping to theme, attr, or Compose MaterialTheme if relevant.
• Do not recommend UI file edits in OutOfRouteBuddy without explicit user approval for production screens.