MUI Public

Mono-repository for the MUI organization with code that can be public.
See https://github.com/mui/mui-private for code that needs to be private.

Documentation

You can read the Infra documentation here.

Applications

Frontend Public

• URL: frontend-public.mui.com
• Source: /apps/code-infra-dashboard/
• Hosting: https://dashboard.render.com/web/srv-d5fq2j0gjchc73e9st5g
• Docs

MUI Internal

• URL: mui-internal.netlify.app
• Source: /docs/
• Hosting: https://app.netlify.com/projects/mui-internal/overview
• Docs
• Website for MUI internal packages, for example, hosts docs-infra. This is equivalent to https://backoffice.mui.com/ but for public logic.

Packages

docs-infra

• Source: /packages/docs-infra/
• Docs

code-infra

• Source: /packages/code-infra/
• Docs

Agent skills

This repo ships agent skills under skills/ (for example, mui-triage). Install them into a repo's agent skills directory with the skills CLI:

npx skills add mui/mui-public --skill mui-triage

Notes:

• Omit --skill <name> to install every skill this repo ships.
• Add -g to install into the global agent directory, or --copy where symlinks aren't supported (for example, Windows). When a coding agent is detected, the install runs non-interactively.

To refresh installed skills later (npx skills add copies the content into your repo):

npx skills update

Renovate PR workflow

Use mui-renovate-triage to fetch a deterministic snapshot of open Renovate PRs and review them one at a time. For each PR, it shows a summary and link, asks whether to merge or continue when CI passes, and runs mui-renovate-fix when CI fails. Follow-up requests continue through the original snapshot without a persistent queue. Request read-only review to skip fixes.

Use mui-renovate-fix when you want to implement a dependency-related fix or migration identified during triage, such as an API adaptation, peer dependency mismatch, or reproducible failure caused by an update. It prefers a source-only draft PR when the fix works with both dependency versions. Otherwise, it updates a single-dependency Renovate PR or extracts the culprit bump and adaptation from a grouped PR into a new draft PR. You can also invoke it directly with a Renovate PR URL; it diagnoses the issue first.

For example, ask the agent to "Use mui-renovate-triage to review the open Renovate PRs", then respond with "merge" or "continue" as it presents each passing PR. Visual approval alone, external-service failures, and unrelated flaky tests do not call for a dependency fix.

Versioning

Steps:

1. Checkout latest master
2. Run pnpm release:prepare
3. Run pnpm release:version
4. Open PR with the changes

Publishing

Steps:

1. Merge versioning PR
2. Checkout release commit on master
3. Run pnpm release:prepare
4. Run pnpm release:publish