From 06cfaabd3b5c44861dfd555b37256c3be22ebb83 Mon Sep 17 00:00:00 2001 From: Qun Cheng Date: Wed, 9 Sep 2026 14:47:58 -0700 Subject: [PATCH] Add Material 3 Expressive migration skill --- .agents/skills/README.md | 2 +- .../material-3-expressive-migration/SKILL.md | 20 +++++++++++++++++++ 2 files changed, 21 insertions(+), 1 deletion(-) create mode 100644 .agents/skills/material-3-expressive-migration/SKILL.md diff --git a/.agents/skills/README.md b/.agents/skills/README.md index 38e778826a20..9dc72b634a14 100644 --- a/.agents/skills/README.md +++ b/.agents/skills/README.md @@ -9,4 +9,4 @@ https://github.com/flutter/flutter/blob/master/.agents/skills/README.md ## Packages specific guidance -When there is specific guidance for packages it will go here. +- [Material 3 Expressive migration](material-3-expressive-migration/SKILL.md): guidance for migrating `packages/material_ui` components to Material 3 Expressive. diff --git a/.agents/skills/material-3-expressive-migration/SKILL.md b/.agents/skills/material-3-expressive-migration/SKILL.md new file mode 100644 index 000000000000..7c35e727da98 --- /dev/null +++ b/.agents/skills/material-3-expressive-migration/SKILL.md @@ -0,0 +1,20 @@ +--- +name: material-3-expressive-migration +description: Use when migrating packages/material_ui components to Material 3 Expressive, including generated defaults, component theme opt-ins, tests, examples, and release notes. +--- + +# Material 3 Expressive Migration + +Use this skill for Material 3 Expressive component migration work in `packages/material_ui`. + +Before planning or implementing a component migration, read the canonical checklist: +https://github.com/flutter/flutter/blob/master/docs/ecosystem/material_ui/Material-3-Expressive-component-migration-checklist.md + +Keep these migration invariants in mind: + +- Keep Material 3 as the default behavior. +- Add Material 3 Expressive behind an explicit component-level opt-in. +- Use token templates and generated defaults whenever possible. +- Keep public APIs consistent with existing Flutter style and related components. +- Add focused tests for the Expressive opt-in, generated defaults, and any new public APIs. +- Add the required pending changelog or release information for user-facing changes.