Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

wp-project-triage

Sterne1

Forks0

Aktualisiert4. Juni 2026 um 11:09

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.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

zenbuapps

zenbuapps/wp-power-checkout

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

Datei-Explorer

3 Dateien

SKILL.md

readonly

name	wp-project-triage
description	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.

WP Project Triage

Compatibility: Targets WordPress 6.9+ (PHP 7.2.24+). Filesystem-based agent with bash + node. Some workflows require WP-CLI.

When to use

Use this skill to quickly understand what kind of WordPress repo you’re in and what commands/conventions to follow before making changes.

Inputs required

Repo root (current working directory).

Procedure

Run the detector (prints JSON to stdout):
- node skills/wp-project-triage/scripts/detect_wp_project.mjs
If you need the exact output contract, read:
- skills/wp-project-triage/references/triage.schema.json
Use the report to select workflow guardrails:
- project kind(s)
- PHP/Node tooling present
- tests present
- version hints and sources
If the report is missing signals you need, update the detector rather than guessing.

Verification

The JSON should parse and include: project.kind, signals, and tooling.
Re-run after changes that affect structure/tooling (adding theme.json, block.json, build config).

Failure modes / debugging

If it reports unknown, check whether the repo root is correct.
If scanning is slow, add/extend ignore directories in the script.

Mehr aus diesem Repository

gleiches Repository

antd-v5

zenbuapps/wp-power-checkout

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

2026-06-041

antd-v6

zenbuapps/wp-power-checkout

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 /

2026-06-041

blocknote-v0-30

zenbuapps/wp-power-checkout

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.

2026-06-041

jotai-v2

zenbuapps/wp-power-checkout

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.

2026-06-041

vite-for-wp-v0-12

zenbuapps/wp-power-checkout

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.

2026-06-041

woocommerce-hpos

zenbuapps/wp-power-checkout

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.

2026-06-041

name	wp-project-triage
description	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.

WP Project Triage

Compatibility: Targets WordPress 6.9+ (PHP 7.2.24+). Filesystem-based agent with bash + node. Some workflows require WP-CLI.

When to use

Use this skill to quickly understand what kind of WordPress repo you’re in and what commands/conventions to follow before making changes.

Inputs required

Repo root (current working directory).

Procedure

Run the detector (prints JSON to stdout):
- node skills/wp-project-triage/scripts/detect_wp_project.mjs
If you need the exact output contract, read:
- skills/wp-project-triage/references/triage.schema.json
Use the report to select workflow guardrails:
- project kind(s)
- PHP/Node tooling present
- tests present
- version hints and sources
If the report is missing signals you need, update the detector rather than guessing.

Verification

The JSON should parse and include: project.kind, signals, and tooling.
Re-run after changes that affect structure/tooling (adding theme.json, block.json, build config).

Failure modes / debugging

If it reports unknown, check whether the repo root is correct.
If scanning is slow, add/extend ignore directories in the script.