菜单
WordPress Plugin/Theme 測試統一參考——涵蓋 E2E（Playwright）與 Integration Test（PHPUnit + WP_UnitTestCase + wp-env）兩大策略。 依測試目的載入對應 reference： - 端到端用戶流程 / 跨頁面互動 → references/e2e-playwright.md - 單元邏輯 + plugin hooks + DB 操作 → references/integration-phpunit.md 共用測試準則（繁中、命名規範、wp-env 共用設定）見主檔下方。
用 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 | wp-testing |
| description | WordPress Plugin/Theme 測試統一參考——涵蓋 E2E（Playwright）與 Integration Test（PHPUnit + WP_UnitTestCase + wp-env）兩大策略。 依測試目的載入對應 reference： - 端到端用戶流程 / 跨頁面互動 → references/e2e-playwright.md - 單元邏輯 + plugin hooks + DB 操作 → references/integration-phpunit.md 共用測試準則（繁中、命名規範、wp-env 共用設定）見主檔下方。 |
從測試目的決定走哪條路，再 Read 對應 reference 載入詳細範例與環境設定。
| 測試層級 | 關注點 | 對應 Reference |
|---|---|---|
| E2E（Playwright） | 核心業務流程 — 使用者最關鍵的操作路徑（購買、註冊、登入、發布） | references/e2e-playwright.md |
| Integration（PHPUnit + WP_UnitTestCase） | Hooks / Filters / REST API / 權限矩陣 / DB 約束 / Service 異常 / 邊緣案例 | references/integration-phpunit.md |
| Static Analysis | 型別安全、邏輯一致性 | （PHPStan，本 skill 不涵蓋） |
E2E 收錄（任一即可）：收入相關（購買 / 訂閱 / 退款）、認證授權主流程、產品核心價值交付（觀看課程 / 發布內容）、跨系統整合 happy path。
E2E 排除（一律改寫 Integration）：權限矩陣、資料 / 狀態邊界、API 參數驗證（401 / 404 / SQLi / XSS）、Hook / Filter 交互邏輯、並發 / race condition。
判準：若這個情境失敗時，不會直接讓使用者拿不到產品價值或公司收不到錢，那它就不是 E2E 該測的。
describe / it / test / public function test_* 的描述、註解、錯誤訊息一律使用繁體中文。英文僅保留技術識別碼、函式名稱、程式碼本身。
// ✅ test('@smoke 使用者可以完成課程購買並進入教室', ...)
// ❌ test('user can purchase course and access classroom', ...)
PHP 端可採函式名繁中（test_管理員可以新增課程）或保留英文函式名 + 繁中 docblock / 註解。
.wp-env.json 放專案根目錄，"plugins": ["."] 掛載當前目錄為 plugin。cd 進子目錄會找不到 .wp-env.json。WP_TESTS_DIR 指向 WP test suite，bootstrap 與 CI 皆需設定。tests/e2e/{group}/{flow}.spec.ts（group = smoke / happy）tests/integration/{Feature}Test.php（PSR-4 命名 + Test.php 結尾）[E2E] / [IT] 便於識別與清除。若此次變更未產出測試檔，必須說明原因（純樣式 / 文案、已有既存測試覆蓋、不屬於對應策略職責等）。
| 需要 | 檔案 |
|---|---|
| Playwright E2E 範本（冒煙 / 快樂路徑）+ wp-env Global Setup + REST API Client + LC Bypass | references/e2e-playwright.md |
| PHPUnit 9 配置 + WP_UnitTestCase API + 13 種測試 pattern + GitHub Actions CI YAML | references/integration-phpunit.md |
references/e2e-playwright.md（E2E）與 references/integration-phpunit.md（Integration Test）。