agentleFS
Sign inStart free
wpgauravwpgaurav/WordPress-skills/skills/wordpress/wpds/SKILL.md

wpds

Skill19 starsChanged 20 days agoMITView on GitHub

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

7 other projects use a version of this, 3 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 5 are common, 0 are distinctive, and 0 are very specific to this project.

  • 5

    Common

    Most of the 3 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Use this skill when the user mentions:

    line 23
  2. Common:

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

    line 34
  3. Common:

    DO NOT search the web for canonical documentation about the WordPress Design System.

    line 38
  4. Common:

    Before working on any WPDS-related tasks, make sure you read relevant documentation on the reference site.

    line 42
  5. Common:

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

    line 55

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

From Agent Skills for WordPress. Copyright (C) 2026 WordPress Contributors, licensed under GPL-2.0-or-later. Changed from upstream: the compatibility: frontmatter line was dropped when this copy was made in March 2026, and license frontmatter plus this notice were added on 2026-10-24. See NOTICE.md.

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free