agentleFS
flutterflutter/packages/.agents/skills/material-3-expressive-migration/SKILL.md

material-3-expressive-migration

Skill5.3k starsChanged 45 days agoBSD-3-ClauseView on GitHub

Use when migrating packages/material_ui components to Material 3 Expressive, including generated defaults, component theme opt-ins, tests, examples, and release notes.

Trending

Quiet this year.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the flutter/packages repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about flutter/packages

The biggest 5 of 35 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 35

Talked about on Stack Overflow and GitHub (35 times).

On Stack Overflow · 30

25 more on Stack Overflow

On GitHub · 5

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill for Material 3 Expressive component migration work in packages/material_ui.

    line 8
  2. Distinctive:

    Before planning or implementing a component migration, read the canonical checklist: …

    line 10
  3. Distinctive:

    Keep these migration invariants in mind:

    line 13
  4. Distinctive:

    Keep Material 3 as the default behavior.

    line 15
  5. Distinctive:

    Add Material 3 Expressive behind an explicit component-level opt-in.

    line 16
  6. Distinctive:

    Use token templates and generated defaults whenever possible.

    line 17
  7. Distinctive:

    Keep public APIs consistent with existing Flutter style and related components.

    line 18
  8. Distinctive:

    Add focused tests for the Expressive opt-in, generated defaults, and any new public APIs.

    line 19
  9. Distinctive:

    Add the required pending changelog or release information for user-facing changes.

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.