Index of every page on this site: llms.txt
All skills
wordpress avatar

/wpds

@7374e6f official
by wordpresswordpress/agent-skills2.4k stars
351
Run it yourself

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

Use this Skill: https://skilld.dev/gh/wordpress/agent-skills/wpds

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈29 tokens for metadata: the name and description. ≈641 when used: this file.

Description uses 1.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈117 characters, or 1.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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 access WPDS-related documentation

  • 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

Required documentation

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

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning2mo5 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill provides instructions for utilizing the WordPress Design System (WPDS) via an MCP server. It contains no malicious code, obfuscation, or unauthorized data access patterns, and is focused on legitimate UI development workflows within the WordPress ecosystem.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • Runlayer9mo

    1/1 file flagged

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 7374e6f. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 5 months ago
Other metadata
compatibility
Requires WPDS MCP server configured and running. Targets WordPress 7.0+ (PHP 7.4.0+).

README badge

README badge for wordpress/agent-skills/wpds

Provides instruction for building WordPress UIs with the WordPress Design System (WPDS), including components, design tokens, and patterns. Use when working with Gutenberg, WooCommerce, or other WordPress interfaces that require WPDS-compliant React components and styling.

Generated from the current SKILL.md.

Does this skill require the WPDS MCP server to be installed?
Yes. The skill works best with the WPDS MCP server configured and running, which provides access to WordPress Design System documentation, components, and design tokens.
What WordPress versions does this skill target?
The skill targets WordPress 6.9 and later, with PHP 7.2.24 or higher.
What tech stack does this skill assume?
Unless otherwise specified in your local context, the skill assumes TypeScript, React, and CSS.
Can I use this skill for non-UI tasks in WordPress projects?
No. The skill focuses exclusively on UI building and excludes non-UI aspects like data fetching from stores or string localization.
Should I use web search for WordPress Design System documentation?
No. The skill prioritizes the WPDS MCP server as the canonical source for all Design System documentation and will push back on web searches for WPDS information.

Generated from the current SKILL.md. These answers refresh after source changes.