AImitSK/wpds
.claude/skills/wpds/SKILL.md
Use when building UIs leveraging the WordPress Design System (WPDS) and its components, tokens, patterns, etc.
development
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add AImitSK/resa-wp wpdsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 12:47 PM4.7s1 file scanned
SKILL.md
- name:
- wpds
- description:
- Use when building UIs leveraging the WordPress Design System (WPDS) and its components, tokens, patterns, etc.
- compatibility:
- Requires WPDS MCP server configured and running. Targets WordPress 6.9+ (PHP 7.2.24+).
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)
- reference site (
- 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
Related Skills
AImitSK/wp-wpcli-and-ops
tools
VerifiedTrustedCommunity
Use when working with WP-CLI (wp) for WordPress operations: safe search-replace, db export/import, plugin/theme/user/content management, cron, cache flushing, multisite, and scripting/automation with wp-cli.yml.
SKILL.mdUpdated Apr 16, 2026
AImitSK/wp-security
tools
VerifiedTrustedCommunity
WordPress Security Patterns für Plugin-Entwicklung. Automatisch anwenden: Sanitization, Escaping, Nonces, Capability Checks, $wpdb->prepare(), REST API Permission Callbacks.
SKILL.mdUpdated Apr 16, 2026
AImitSK/wp-rest-api
development
VerifiedTrustedCommunity
Use when building, extending, or debugging WordPress REST API endpoints/routes: register_rest_route, WP_REST_Controller/controller classes, schema/argument validation, permission_callback/authentication, response shaping, register_rest_field/register_meta, or exposing CPTs/taxonomies via show_in_rest.
SKILL.mdUpdated Apr 16, 2026
AImitSK/wp-project-triage
tools
VerifiedTrustedCommunity
Use when you need a deterministic inspection of a WordPress repository (plugin/theme/block theme/WP core/Gutenberg/full site) including tooling/tests/version hints, and a structured JSON report to guide workflows and guardrails.
SKILL.mdUpdated Apr 16, 2026