Compose a WordPress Design System interface

Classify before searching

1. State the user-visible behaviour, minimum runtime and package versions, rendering owner, runtime document, and whether each Design System dependency is bundled or externalized.
2. Inspect the changed surface and its nearest same-surface precedent once.
3. Choose the narrowest path:
   • Lightweight: keep an existing supported component when behaviour, styling, and document setup do not change.
   • Standard: select or compose a public component or token.
   • Deep: handle custom UI, a package migration, or another rendering document such as an iframe, popup, or portal.

Do not reopen component selection on the lightweight path. Verify the existing contract, make the narrow change, and stop.

Select for the behaviour