Skip to content

[material_ui] Add Material 3 Expressive migration skill #12818

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
QuncCccccc wants to merge 1 commit into
base: main
Choose a base branch
from
+21 −1
Open

[material_ui] Add Material 3 Expressive migration skill #12818

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .agents/skills/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Comment thread
Piinks marked this conversation as resolved.
20 changes: 20 additions & 0 deletions .agents/skills/material-3-expressive-migration/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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.
Comment thread
Piinks marked this conversation as resolved.
---

# Material 3 Expressive Migration

Use this skill for Material 3 Expressive component migration work in `packages/material_ui`.
Comment thread
Piinks marked this conversation as resolved.

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

@Piinks Piinks Sep 11, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Needs flutter/flutter#192519 to land first

@QuncCccccc QuncCccccc Sep 14, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For the PR description, can you show an example of how contributors should use/prompt for this skill?

Updated! Thanks!


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.
Loading