getdokan

Build, scaffold, and run the Dokan Lite/Pro Playwright suite. Use when the user asks to add tests for a feature, scaffold from test-cases.md, or run the automation suite (Lite Only / PR / Full). Knows the folderized format, tag system, Docker / wp-env preconditions, and the .env / license-key requirements for Pro runs.

Execute the Dokan Playwright test suite (E2E + API), locally or via GitHub Actions. Invoke when the user asks to run, kick off, trigger, re-run, debug, or inspect the automated test runs. Phrases such as "run the suite", "run e2e tests", "trigger CI", "execute the QA suite", or "check the failed run" should activate this skill.

Build new vendor dashboard DataViews list pages from scratch OR migrate legacy Filter/StatusFilter/DataViewTable components to the unified @wedevs/plugin-ui DataViews component. Covers fresh builds (types, hook, list, route, PHP nav) and legacy migration (Scenario A status tabs, Scenario B multi-list merge).

Review Dokan code changes and pull requests for coding standards, security, and architectural compliance. Use when reviewing PRs, performing code audits, or checking code quality.

Add or modify Dokan backend PHP code following project conventions. Use when creating new classes, methods, hooks, REST controllers, or modifying existing backend code. Invoke before writing PHP unit tests.

Run tests, linting, and quality checks for Dokan development. Use when running tests, fixing code style, building assets, or following the development workflow.

Add or modify Dokan frontend code (React, TypeScript, Vue, Tailwind). Use when creating components, hooks, stores, or modifying webpack configuration.

Guidelines for git and GitHub operations in the Dokan repository. Use when creating branches, commits, or pull requests.

Write, run, and extend the StoreGrowth (Sales Booster) Playwright E2E + API test suite in tests/e2e. Use when adding or modifying browser/UI tests, REST/API tests, fixtures, helpers, or test data; debugging failing tests; setting up the wp-env test environment; or wiring CI. Read before touching anything under tests/e2e.

Add or modify StoreGrowth (Sales Booster) backend PHP code following project conventions. Use when creating classes, services, hooks, REST controllers, ajax handlers, or modifying existing backend PHP. Read before writing backend PHP in this plugin.

Review StoreGrowth (Sales Booster) code changes and pull requests for conventions, security, and architecture compliance. Use when reviewing PRs, auditing code, or checking quality before merge.

Add or modify StoreGrowth (Sales Booster) frontend code — React, Ant Design, @wordpress/data stores, the admin settings SPA, and the Lerna/wp-scripts build. Use when creating components, stores, admin routes, or touching asset builds.

StoreGrowth (Sales Booster) git, build, versioning, and release workflow — branching, commits/PRs, the SPSG_VERSION placeholder, makepot, and the WordPress.org deploy. Use when committing, opening PRs, bumping the version, or cutting a release.

Scaffold or modify a StoreGrowth (Sales Booster) feature module — the activatable units under modules/ (BOGO, fly-cart, etc.). Use when adding a new module or changing a module's registration, activation, providers, or assets.

MUST invoke before reading or writing any Texty end-to-end (Playwright) test. Encodes this suite's auth model (cached admin storage state + the WP email-verification interstitial), the `helpers/texty.ts` client API, the REST-contract + idempotency patterns, and the plugin-ui/base-ui selector gotchas that have already cost real debugging time. Load it first so the very first spec follows the conventions, not the third one. TRIGGER (any of these = invoke immediately, before tools): - File path matches `tests/e2e/**`, `**/*.spec.ts`, `tests/e2e/helpers/**`, `tests/e2e/global.setup.ts`, `playwright.config.ts`, or `tests/tsconfig.json` - Task involves: e2e test, end-to-end, Playwright, Playwright MCP, `@playwright/test`, spec file, `test.describe`, REST contract test, API contract test, auth/storage state, test coverage, COVERAGE matrix, `npm run test:e2e`, flaky test, selector/locator for the admin SPA under test - User says: "write an e2e test", "add a spec", "test this page/endpoint", "give full test coverage"

MUST invoke before any read or edit that touches Texty PHP code under `includes/**`. Encodes the project's namespace, registry, REST, send-pipeline, notification, and gateway conventions plus the WordPress Coding Standards rules `phpcs.xml` enforces. TRIGGER (any of these = invoke immediately, before tools): - File path matches `includes/**`, `texty.php`, or `**/*.php` - Task involves: PHP class, REST endpoint, hook (action/filter), gateway, notification, integration, dispatcher, install/uninstall, DataLayer, SmsStat, dbDelta, wp_options, user_meta, post_meta, Mozart, WPCS, phpcs, composer - User says: "add a gateway", "add a notification", "add a REST endpoint", "register a hook", "add a setting", "add an integration", "create a PHP class", "fix this PHPCS warning", "wire up `texty_*` hook", "add a column to `wp_texty_sms_stat`" SKIP (do NOT invoke): - Frontend-only edits in `src/**` (use `frontend-dev`) - Pure docs (`README.md`, `CLAUDE.md`, `readme.txt`) - Build / release tasks (`bin/build.sh`, version b

THIS IS THE PR REVIEW + CODE REVIEW SKILL. Invoke for any review intent — single file, diff, branch, or full pull request — against Texty's standards (WordPress Coding Standards on PHP, the 5 frontend rules in `frontend-dev`). Covers line-level violations, backward-compatibility breaks, fatal-error risks, and PR-level merge readiness. TRIGGER — invoke immediately when the user says ANY of these (case-insensitive, with or without a leading slash): - "pr review", "PR review", "review pr", "review PR", "review this pr", "review the pr" - "code review", "review this code", "review the code", "code review this" - "review #123", "review pr #123", "review PR-123", "review my changes", "review my branch", "review this branch", "review this diff" - "check this pr", "audit this pr", "audit this code", "audit this file", "audit this diff", "audit this branch" - "is this ready to merge", "is this safe to merge", "approve this pr", "approve this", "ship review" - "find issues in this branch", "what's wrong with X", "any

MUST invoke before any read or edit that touches the Texty frontend. The 5 coding rules in this skill (text-domain `texty`, arrow functions, try/catch, full types, Tailwind utilities) apply to every line of frontend code — load them first so the very first edit follows them, not the third one. TRIGGER (any of these = invoke immediately, before tools): - File path matches `src/**` or `src/**/*.{ts,tsx,js,jsx,css,scss}` - File path matches `**/*.tsx`, `**/*.ts`, `package.json`, `tsconfig.json`, `webpack.config.js`, `postcss.config.js`, `tailwind.config.*`, `.prettierrc` - Task involves: React, JSX, TypeScript, Tailwind, plugin-ui, recharts, react-router, hash routing, admin SPA, dashboard, settings page, notifications page, tools page, toast, chart, REST call, apiFetch, useEffect, useState, custom hook, route, withRouter, menu sync, i18n string, .pot regen - User says: "add a page", "build a component", "wire up an endpoint", "fetch from texty/v1/...", "add a chart", "add a toast", "convert .js to .tsx", "refa