Skip to content

Commit df4d712

Browse files
authored
[material_ui] Add Material 3 Expressive migration skill (flutter#12818)
This PR is to add an agent skill for Material 3 Expressive component migration work in `packages/material_ui`. Related to https://github.com/orgs/flutter/projects/250. Will wait until flutter#192519 lands. Once this PR is landed, use prompts like * /material-3-expressive-migration Migrate `<component name>` in `packages/material_ui`. * Use the `material-3-expressive-migration` skill to migrate `<component name>` in `packages/material_ui`. to invoke the skill. ## Pre-Review Checklist
1 parent e18a541 commit df4d712

2 files changed

Lines changed: 21 additions & 1 deletion

File tree

‎.agents/skills/README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,4 +9,4 @@ https://github.com/flutter/flutter/blob/master/.agents/skills/README.md
99

1010
## Packages specific guidance
1111

12-
When there is specific guidance for packages it will go here.
12+
- [Material 3 Expressive migration](material-3-expressive-migration/SKILL.md): guidance for migrating `packages/material_ui` components to Material 3 Expressive.
Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
name: material-3-expressive-migration
3+
description: Use when migrating packages/material_ui components to Material 3 Expressive, including generated defaults, component theme opt-ins, tests, examples, and release notes.
4+
---
5+
6+
# Material 3 Expressive Migration
7+
8+
Use this skill for Material 3 Expressive component migration work in `packages/material_ui`.
9+
10+
Before planning or implementing a component migration, read the canonical checklist:
11+
https://github.com/flutter/flutter/blob/master/docs/ecosystem/material_ui/Material-3-Expressive-component-migration-checklist.md
12+
13+
Keep these migration invariants in mind:
14+
15+
- Keep Material 3 as the default behavior.
16+
- Add Material 3 Expressive behind an explicit component-level opt-in.
17+
- Use token templates and generated defaults whenever possible.
18+
- Keep public APIs consistent with existing Flutter style and related components.
19+
- Add focused tests for the Expressive opt-in, generated defaults, and any new public APIs.
20+
- Add the required pending changelog or release information for user-facing changes.

0 commit comments

Comments
 (0)