design-system-contribution
Contribute to the WordPress Design System
In a Gutenberg checkout, read the relative links below from the checked-out revision. Outside a checkout, resolve them from .agents/skills/design-system-contribution/ in Gutenberg on GitHub.
Read the affected package's AGENTS.md and the relevant package contribution guidance.
Choose the smallest change
Start from the consumer's need. For a bug fix, reproduce the failure and identify the behavior to restore. For a refactor, identify the behavior to preserve. A new capability needs a concrete use case and an explanation of why existing public composition is insufficient.
When choosing a component or token, use the Design System MCP server's get_components, get_component_details, and get_design_tokens as appropriate when available. Without MCP, use the guide's recommendation sources and the token reference. Check the current source before adding an API that appears to be missing.
Keep product-specific behavior in the consuming package and use design-system-ui-composition for that work. For unresolved public design decisions, follow Contributing to the Design System before implementation; continue work that does not depend on that decision.