How do I install the Mui To Bui Migration skill?

Run npx skillmds@latest add paulasilvatech/mui-to-bui-migration in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Mui To Bui Migration safe to use?

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Mui To Bui Migration?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Mui To Bui Migration free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Mui To Bui Migration?

paulasilvatech (@paulasilvatech) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Mui To Bui Migration by paulasilvatech

Name: Mui To Bui Migration
Author: paulasilvatech

Mui To Bui Migration

Migrate Backstage app or plugin UI from Material-UI to Backstage UI with version-checked component mappings, CSS setup, accessibility, analytics, styling, and visual validation. Use when replacing @material-ui imports, MUI icons, makeStyles, or adopting BUI.

File contents

MUI to Backstage UI migration

Migrate in reviewable slices and verify each component mapping against the target Backstage UI version.

When to invoke

"Replace MUI with @backstage/ui."
"Migrate makeStyles and MUI icons."
"Adopt BUI components in this Backstage plugin."
"Fix accessibility or analytics after a BUI migration."

Procedure

Confirm target Backstage and @backstage/ui versions, frontend mode, and visual-test capability.
Read the pinned upstream procedure.
Verify component availability and props against the installed BUI package.
Inventory MUI packages, components, icons, styling APIs, theme assumptions, and tests.
Add the required BUI package and global CSS import through repository-approved dependency workflow.
Migrate one coherent component group at a time, preserving semantics and accessibility.
Prefer BUI navigation and interactive components so built-in analytics remain intact.
Replace styling with supported BUI tokens or CSS without copying incompatible MUI props.
Run typecheck, unit tests, accessibility checks, and visual review at supported viewports.
Remove MUI dependencies only when no remaining consumers require them.

Output template

## BUI migration result

**Package:** <package>
**BUI version:** <version>

| MUI surface | BUI replacement | Accessibility | Visual validation |
| --- | --- | --- | --- |

Quality gate

Component mappings match the installed BUI version.
CSS, tokens, icons, and interaction semantics are migrated.
Built-in analytics are not duplicated.
Keyboard, focus, labels, contrast, and responsive behavior are reviewed.
Typecheck, tests, and visual validation pass.
MUI dependencies remain until all consumers are migrated.

---name: mui-to-bui-migrationdescription: Migrate Backstage app or plugin UI from Material-UI to Backstage UI with version-checked component mappings, CSS setup, accessibility, analytics, styling, and visual validation. Use when replacing @material-ui imports, MUI icons, makeStyles, or adopting BUI.license: Apache-2.0---# MUI to Backstage UI migrationMigrate in reviewable slices and verify each component mapping against the target Backstage UIversion.## When to invoke- "Replace MUI with @backstage/ui."- "Migrate makeStyles and MUI icons."- "Adopt BUI components in this Backstage plugin."- "Fix accessibility or analytics after a BUI migration."## Procedure1. Confirm target Backstage and `@backstage/ui` versions, frontend mode, and visual-test capability.2. Read [the pinned upstream procedure](references/upstream/SKILL.md).3. Verify component availability and props against the installed BUI package.4. Inventory MUI packages, components, icons, styling APIs, theme assumptions, and tests.5. Add the required BUI package and global CSS import through repository-approved dependency workflow.6. Migrate one coherent component group at a time, preserving semantics and accessibility.7. Prefer BUI navigation and interactive components so built-in analytics remain intact.8. Replace styling with supported BUI tokens or CSS without copying incompatible MUI props.9. Run typecheck, unit tests, accessibility checks, and visual review at supported viewports.10. Remove MUI dependencies only when no remaining consumers require them.## Output template```markdown## BUI migration result**Package:** <package>**BUI version:** <version>| MUI surface | BUI replacement | Accessibility | Visual validation || --- | --- | --- | --- |```## Quality gate- [ ] Component mappings match the installed BUI version.- [ ] CSS, tokens, icons, and interaction semantics are migrated.- [ ] Built-in analytics are not duplicated.- [ ] Keyboard, focus, labels, contrast, and responsive behavior are reviewed.- [ ] Typecheck, tests, and visual validation pass.- [ ] MUI dependencies remain until all consumers are migrated.

Frequently asked questions