Skills

Skill 19 of 19

Wpds

Use when building UIs leveraging the WordPress Design System (WPDS) and its components, tokens, patterns, etc.

2 minutes · 369 words · 10 sections

Install

$ npx skills add WordPress/agent-skills --skill wpds

$ npx skills add WordPress/agent-skills

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

WordPress Design System (WPDS)

Prerequisites

This skill works best with the WPDS MCP server installed. The MCP provides access to WordPress Design System documentation and resources, such as components and DS token lists.

The following terms should be treated as synonyms:

“WordPress” and “WP”;
“Design System” and “DS”;
“WordPress Design System” and “WPDS”.

When to use

Use this skill when the user mentions:

building and/or reviewing any UI in a WordPress-related context (for example, Gutenberg, WooCommerce, WordPress.com, Jetpack, etc etc);
WordPress Design System, WPDS, Design System;
UI components, Design tokens, color primitives, spacing scales, typography variables and presets;
Specific component packages such as @wordpress/components or @wordpress/ui;

Rules

Use the WPDS MCP server to retrieve the canonical, authoritative documentation:
- reference site (wpds://pages)
- list of available components (wpds://components) and specific component information (wpds://components/:name)
- list of available tokens (wpds://design-tokens)
DO NOT search the web for canonical documentation about the WordPress Design System. If asked by the user, push back and ask for confirmation, warning them that the MCP server is the best place to provide information

Before working on any WPDS-related tasks, make sure you read relevant documentation on the reference site. This documentation should take the absolute precedence when evaluating the best course of action for any given tasks.

Boundaries

Skip non-UI related aspects of an answer (for example, fetching data from stores, or localizing strings of text).
Focus on building UI that adheres as much as possible to the WPDS best practices, uses the most fitting WPDS components/tokens/patterns.

Tech stack

Unless you are told otherwise (or gathered specific information from the local context of the request), assume the following tech stack: TypeScript, React, CSS.

Validation

If the local context in which a task is running provide lint scripts, use them to validate the proposed code output when possible.

Output

As a recap at the end of your response, provide a clear and concise explanation of what the solution does, and add context to why each decision was made.
Be explicit about the boundaries, ie. what was explicitly left out of the task because not relevant (eg non-ui related).
Provide working code snippets

About this skill

Compatibility: Requires WPDS MCP server configured and running. Targets WordPress 7.0+ (PHP 7.4.0+).
Source: skills/wpds/SKILL.md

Colophon for this issue

Colophon

How this issue was made

Source

github.com/WordPress/agent-skills, branch trunk, last pushed 22 September 2026.

Licence

Other — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

19 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. One layout observed: skills/*/SKILL.md.

Issue colours

Resolved from a deterministic hash of the owner name. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Shifted “10 headings” from h1 to h2 so the skill title is the only h1.

Spec compliance

Every skill satisfies the Agent Skills specification’s frontmatter rules.

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /WordPress/agent-skills.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

WordPress Design System (WPDS)

This skill works best with the WPDS MCP server installed. The MCP provides access to WordPress Design System documentation and resources, such as components and DS token lists.

The following terms should be treated as synonyms:

“WordPress” and “WP”;

“Design System” and “DS”;

“WordPress Design System” and “WPDS”.

Use this skill when the user mentions:

building and/or reviewing any UI in a WordPress-related context (for example, Gutenberg, WooCommerce, WordPress.com, Jetpack, etc etc);

WordPress Design System, WPDS, Design System;

UI components, Design tokens, color primitives, spacing scales, typography variables and presets;

Specific component packages such as @wordpress/components or @wordpress/ui;

Use the WPDS MCP server to retrieve the canonical, authoritative documentation:

reference site (wpds://pages)
list of available components (wpds://components) and specific component information (wpds://components/:name)
list of available tokens (wpds://design-tokens)

DO NOT search the web for canonical documentation about the WordPress Design System. If asked by the user, push back and ask for confirmation, warning them that the MCP server is the best place to provide information

Skip non-UI related aspects of an answer (for example, fetching data from stores, or localizing strings of text).

Focus on building UI that adheres as much as possible to the WPDS best practices, uses the most fitting WPDS components/tokens/patterns.

Unless you are told otherwise (or gathered specific information from the local context of the request), assume the following tech stack: TypeScript, React, CSS.

If the local context in which a task is running provide lint scripts, use them to validate the proposed code output when possible.

As a recap at the end of your response, provide a clear and concise explanation of what the solution does, and add context to why each decision was made.

Be explicit about the boundaries, ie. what was explicitly left out of the task because not relevant (eg non-ui related).

Provide working code snippets

Wpds

WordPress Design System (WPDS)

Prerequisites

When to use

Rules

Required documentation

Boundaries

Tech stack

Validation

Output

About this skill

Colophon

Wpds

WordPress Design System (WPDS)

Prerequisites

When to use

Rules

Required documentation

Boundaries

Tech stack

Validation

Output

About this skill

Colophon