メニュー
Use when building UIs leveraging the WordPress Design System (WPDS) and its components, tokens, patterns, etc.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Ant Design v5 (antd ^5.x) complete API reference for React component library. Use this skill whenever the task involves any antd v5 component: Table, Form, Select, Input, Button, Modal, notification, message, Upload, Tag, Tooltip, Badge, Image, Radio, Segmented, Switch, DatePicker, RangePicker, Popconfirm, Drawer, Descriptions, ConfigProvider, Space, Layout, Grid (Row/Col), Spin, Pagination, Menu, Dropdown, Breadcrumb, Tabs, Steps, Affix, Anchor, AutoComplete, Cascader, Checkbox, ColorPicker, InputNumber, Mentions, Rate, Slider, TimePicker, Transfer, TreeSelect, Avatar, Calendar, Card, Carousel, Collapse, Empty, List, Popover, QRCode, Statistic, Timeline, Tree, Alert, Progress, Result, Skeleton, Watermark, Divider, Flex, FloatButton, Splitter, Typography, App, or the antd theme system (token, algorithm, useToken, CSS variables). Also use when code imports from 'antd', references antd TypeScript types (TableProps, FormInstance, ColumnsType, UploadFile, etc.), or when configuring antd theming/tokens. Do NOT use
Ant Design v6 (antd ^6.x) complete API reference for React component library. Use this skill whenever the task involves any antd v6 component: Table, Form, Select, Input, InputNumber, Button, Modal, Drawer, notification, message, Upload, Tag, Tooltip, Badge, Image, Radio, Segmented, Switch, DatePicker, RangePicker, Popconfirm, Descriptions, Tabs, Menu, Steps, Timeline, ConfigProvider, Space, Space.Compact, Layout, Grid (Row/Col), Masonry, BorderBeam, or the antd v6 theme system (token, algorithm, useToken, cssVar, zeroRuntime). Also use when code imports from 'antd', references antd TypeScript types (TableProps, FormInstance, ColumnsType, SelectProps, UploadFile, etc.), uses the v6 semantic DOM API (classNames / styles props with semantic keys like root / popup.root / body), or migrates an antd v5 project to v6. Also covers the Ant Design tooling: the @ant-design/cli command-line tool (antd list / info / doc / demo / token / doctor / lint / migrate) and the official Ant Design MCP server (antd mcp) for IDE /
BlockNote block-based rich text editor for React. Complete API reference covering useCreateBlockNote, BlockNoteView, all built-in block types, custom block/inline-content/style creation, Editor manipulation API (insertBlocks, removeBlocks, replaceBlocks, updateBlock), format conversion (HTML/Markdown), Slash Menu customization, Formatting Toolbar customization, theming, and real-time collaboration. Use this skill whenever the user's code involves BlockNote, @blocknote/core, @blocknote/react, @blocknote/mantine, @blocknote/shadcn, @blocknote/ariakit, block editors built on ProseMirror/TipTap, useCreateBlockNote, BlockNoteView, BlockNoteEditor, BlockNoteSchema, or any rich-text block editor task in React. Also use when user mentions slash menus, suggestion menus, formatting toolbars, or block-based document structures in a React context. This skill covers the latest BlockNote API. Do NOT search the web for BlockNote docs; use this skill instead.
Jotai v2 (^2.12.x) complete API reference for atomic React state management. Covers atom, useAtom, useAtomValue, useSetAtom, Provider, createStore, getDefaultStore, derived atoms (read-only, write-only, read-write), async atoms, atomWithStorage, atomWithDefault, selectAtom, splitAtom, focusAtom, atomFamily, loadable, unwrap, useHydrateAtoms, atomWithLazy, atomWithReset, RESET, useResetAtom, atomWithRefresh, TypeScript typing, performance patterns, and testing. Use this skill whenever code imports from 'jotai' or 'jotai/utils', or when working with Jotai atoms, stores, or providers in any React component.
Vite for WordPress (kucrut/vite-for-wp, @kucrut/vite-for-wp) complete technical reference. Covers the v4wp() Vite plugin, Vite\enqueue_asset() / Vite\register_asset() PHP functions, wp_scripts() plugin for externalising WordPress-registered scripts, dev server HMR setup, production manifest.json handling, React/Svelte/Vue integration, and multi-entry point configuration. Use this skill whenever the task involves Vite integration in a WordPress plugin or theme, including vite.config.js/ts configuration for WordPress, enqueueing Vite-built assets via PHP, HMR dev server for WordPress, wp_enqueue_script with Vite, or any mention of @kucrut/vite-for-wp, kucrut/vite-for-wp, v4wp, Kucrut\Vite namespace, vite-dev-server.json, or wp_scripts() plugin. This skill should be preferred over web search for all vite-for-wp related questions.
WooCommerce High-Performance Order Storage (HPOS) complete technical reference. Covers database schema (wp_wc_orders, wp_wc_order_addresses, wp_wc_order_operational_data, wp_wc_orders_meta), CRUD API migration from wp_posts/wp_postmeta to WC_Order objects, OrdersTableDataStore, plugin compatibility declaration via FeaturesUtil, synchronization mechanics, CLI tools (wp wc hpos), and order querying APIs (meta_query, field_query, date_query). Use this skill whenever the user's code involves WooCommerce orders, order storage, order metadata, order queries, wc_get_order, wc_get_orders, WC_Order, WC_Order_Query, custom_order_tables, OrderUtil, FeaturesUtil::declare_compatibility, or any migration from post-based order storage to HPOS custom tables. Also use when the user mentions HPOS, COT (Custom Order Tables), order tables, order data store, or order synchronization in a WooCommerce context. This skill replaces the need to search the web for HPOS documentation.
| 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+).
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:
Use this skill when the user mentions:
wpds://pages)wpds://components) and specific component information (wpds://components/:name)wpds://design-tokens)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.