1,291 件 ・ 関連度順
概要と使いどころ
Capture and develop a reusable skill, tool repair, or behavior improvement noticed while completing a task. Use when instructions are stale, a recurring workflow deserves a skill, or a tool contract fails in practice.
日本語の概要は準備中です。原文の説明を表示しています。
End-to-end playbook for creating a new NV oOS Pro toolkit under addons/pro/includes/tools/<toolkit> — folder layout, service layer, tool class conventions (canonical envelope, two-gate sanitisation, capability flags), ALL seven registration surfaces (central registry, admin Tools section, settings status map, both WP-CLI commands, schedule presets, workflow presets, SA Toolkit Manager), fixture/oracle testing with a standalone smoke harness, and the phpcs gotcha checklist. Use when asked to build a new Pro toolkit, add a toolkit to the plugin, scaffold toolkit tools, register toolkit presets/toggles, or debug why a new toolkit's tools or presets don't appear. First case study: food-beverage (F&B Management, 21 tools, 2026-10-08, 20/20 Check-totals oracle verified). Complements mcp-ai-wpoos-toolkit-audit (hardening existing toolkits) and mcp-ai-wpoos-test-suite (repair).
日本語の概要は準備中です。原文の説明を表示しています。
Register a custom WooCommerce shipping provider — extend AbstractShippingProvider and add it via the woocommerce_fulfillment_shipping_providers filter (WC 10.1+). Distinct from shipping methods (rate at checkout) — a provider is a carrier identity (UPS, FedEx, DHL, your custom carrier) used by the Fulfillments system for tracking URLs, tracking-number pattern detection, country-pair support, and the orders-list filter. Required methods get_key / get_name / get_icon / get_tracking_url, with optional shipping-from / shipping-to / try_parse_tracking_number. Registration accepts class names (resolved via the DI container) or pre-built instances, keyed by get_key. Use when integrating a private carrier, fulfillment service, or any tracking-aware shipping identity. Triggers on AbstractShippingProvider, woocommerce_fulfillment_shipping_providers, FulfillmentUtils::get_shipping_providers, "shipping provider" in WooCommerce context, or carrier tracking integration.
日本語の概要は準備中です。原文の説明を表示しています。
AI-powered design intelligence with 67 UI styles, 161 color palettes, 57 font pairings, 99 UX guidelines, and 25 chart types across 15+ tech stacks. Generates complete design systems for any product type with industry-specific reasoning rules.
日本語の概要は準備中です。原文の説明を表示しています。
Design and implement typography systems for web and brand projects. Covers font pairing, type scales, variable fonts, web font loading strategies (font-display, subsetting), CSS typography best practices, and WordPress theme typography integration. Use when selecting fonts, building type scales, loading web fonts, configuring theme.json typography, or fixing font performance issues.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "implement LLM-as-judge", "compare model outputs", "create evaluation rubrics", "mitigate evaluation bias", or mentions direct scoring, pairwise compari
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "analyze competitors" or "竞品分析"; benchmarks competitor keywords, content, backlinks, AI citations, and traffic share into strengths, weaknesses, and an action plan. Not for a pairwise topic-coverage gap map — use content-gap-analysis. 竞品分析/竞争对手
日本語の概要は準備中です。原文の説明を表示しています。
Build document analysis applications with Azure Document Intelligence (Form Recognizer) SDK for Java. Use when extracting text, tables, key-value pairs from documents, receipts, invoices, or buildi...
日本語の概要は準備中です。原文の説明を表示しています。
Context-aware remapping of stale parent shard references to new sub-shard targets after shard split operations
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate operational workspace setup before implementation slices across scaffold, CI/CD, hosting, and data provisioning shards
日本語の概要は準備中です。原文の説明を表示しています。
Create new CFSA Antigravity skills following the kit's skill format. Handles brainstorming, SKILL.md generation, references, and MANIFEST.md registration.
日本語の概要は準備中です。原文の説明を表示しています。
Axis-by-axis interview methodology for establishing engineering performance budgets during architecture PRD compilation. Use when conducting the Step 10.5 performance budget interview in /create-prd-compile.
日本語の概要は準備中です。原文の説明を表示しています。
Validate sequencing and cross-layer readiness before phase slicing, including coverage and consistency hard gates
日本語の概要は準備中です。原文の説明を表示しています。
Architect durable, event-driven workflows using step functions, retry strategies, idempotency, fan-out patterns, and the critical differences between orchestration approaches.
日本語の概要は準備中です。原文の説明を表示しています。
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
日本語の概要は準備中です。原文の説明を表示しています。
Per-surface tech stack decision tables and development tooling options. Use during /create-prd-stack to present constraint-filtered options to the user.
日本語の概要は準備中です。原文の説明を表示しています。
Run iterative IA deepening, finalize shard, update indexes/tracker, and enforce ambiguity gates before handoff
日本語の概要は準備中です。原文の説明を表示しています。
Generate or refresh docs/ARCHITECTURE.md from current codebase state with evidence-backed component and data-flow mapping
日本語の概要は準備中です。原文の説明を表示しています。
Classify target IA shard for BE extraction, load stack skills, and produce a complete referenced-material inventory
日本語の概要は準備中です。原文の説明を表示しています。
Create clear, comprehensive technical documentation for any audience
日本語の概要は準備中です。原文の説明を表示しています。
Design and implement comprehensive testing strategies. Use when setting up tests, choosing test types, implementing TDD, or improving code quality. Covers unit tests, integration tests, E2E tests, test-driven development, and testing best practices.
日本語の概要は準備中です。原文の説明を表示しています。
Execute code-quality gates for a completed phase including tests, coverage, lint, types, build, CI/CD, staging, migrations, and spec coverage
日本語の概要は準備中です。原文の説明を表示しています。
Transforms user prompts into optimized prompts using established frameworks (RTF, RISEN, Chain of Thought, RODES). Analyzes intent, selects framework, and produces structured, ready-to-use prompts.
日本語の概要は準備中です。原文の説明を表示しています。
Methodology for writing complete, unambiguous IA, BE, and FE specification documents in the CFSA pipeline. Covers completeness testing, progressive section writing, cross-reference checking, and ambiguity gate application.
日本語の概要は準備中です。原文の説明を表示しています。