「spa」の検索結果

Operational guide for the NV oOS WordPress Playground demo blueprints — the Content Graph "Project Asteria" demo, the Complete bundle × local Ollama demo, and the Docs Hub wp.org Live Preview demo. Covers blueprint authoring patterns (embedded runPHP seed snippets, generator scripts, preview-safe vs standalone split), CORS hosting gotchas, the CI Plugin Check gate (built-ZIP scan, rsync/distignore sync, ABSPATH guards), Playground worker crash modes (PHP-side localhost fetches, inline-script UTF-8, SPA SSE-hold mount bursts, crash-truncation SyntaxErrors), local Ollama integration (OLLAMA_ORIGINS, browser policy matrix, plugin settings + assistant meta keys), and the CLI validation harness (probe builder, mount quirks, server-mode 502 boot). Use when extending or debugging the demo blueprints, adding a new Playground demo, or triaging a crashing Playground instance.

日本語の概要は準備中です。原文の説明を表示しています。

Use the WooCommerce REST API v4 (namespace wc/v4, since WC 10.2) alongside or in place of v3 — verified route catalog (Customers, Orders, Refunds, Products, ShippingZones with DELETE, ShippingZoneMethod, Fulfillments, segmented Settings under /wc/v4/settings/<group>), the hook prefix pattern woocommerce_rest_api_v4_<route>_*, shared error codes, and the RestApiCache trait (WC 10.5+) for endpoint response caching. The v4 AbstractController lives under the Internal namespace and is NOT a public extension surface; plugin-defined REST routes use WP_REST_Controller directly. Use when calling WC REST endpoints, when picking v3 vs v4, or when reviewing /wc/v3/ URLs that now have v4 equivalents. Triggers on wc/v4, /wc/v4/, woocommerce_rest_api_v4_*, RestApiCache, customer-owned Woo endpoints, REST API v4 in WooCommerce context.

日本語の概要は準備中です。原文の説明を表示しています。

Given the product and the existing page inventory, identify missing blog topics and generate new blog posts that capture search/AI intent using the query-fanout pattern. Use this skill whenever the user asks to "spawn blogs", "generate blog posts", "expand the blog", "build out a content cluster", "write blog ideas", "cover more search intents", "query fanout for blogs", or wants new long-form content that supports existing pillars. Output is one new post per topic in the project's existing post format (markdown, MDX, component, or CMS migration note), with frontmatter shape mirrored from an existing post.

日本語の概要は準備中です。原文の説明を表示しています。

Given the product offering and existing page inventory, create new core landing and resource pages (homepage refresh, features, solutions, pricing, comparison, resource hubs, about) that capture core product intent using the query-fanout pattern. Use this skill whenever the user asks to "spawn pages", "generate landing pages", "create marketing pages", "build a pricing page", "add a solutions page", "build out the site", "fill in missing pages", or wants new top-level marketing/product pages. Output is one new page per route in the project's native file format (component or markdown), matching the existing page style and framework idiom.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user asks to "generate subject line variants", "pre-score my subject lines", or "will this subject get truncated / trigger spam filters"; produces a labeled subject + preheader variant set and a per-variant heuristic pre-score card — spam-trigger flags, length/truncation across desktop + mobile, emoji-count, and the inbox preview render (from-name + subject + preheader) — before any test is run. Not for the body copy or CTA — use email-creative-builder; not for the A/B test design or significance read — use send-experiment-designer; not for the profile-weighted EQS or the S1/S2/N1/D1 vetoes — use email-quality-auditor. 邮件主题行生成/主题行预打分/截断与垃圾词检查

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user asks to "track where my emails are actually landing after I send", "read my seed-list inbox vs spam vs promotions results", "trend my Gmail Postmaster / Microsoft SNDS reputation", or "did placement drop after my last send"; produces a per-provider inbox/spam/promotions placement read, a domain/IP reputation trend from Postmaster + SNDS, a send-over-send delta with named regressions, and a reusable SEND-S placement snapshot on your own exported telemetry. Not for the pre-send SPF/DKIM/DMARC auth pre-flight — use deliverability-qa; not for computing the EQS or running the vetoes — use email-quality-auditor. 邮件收件箱落点监测/收件箱vs垃圾邮件/Postmaster声誉趋势

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user asks to "build a B2B cold-outbound sequence", "design reply-triage branching", "plan a domain warmup / sending throttle", or "make my outbound CAN-SPAM / opt-in compliant"; produces a multi-step outbound sequence with reply-triage branches (positive / objection / referral / not-now / opt-out), a warmup + send-throttle ramp schedule, jurisdiction opt-in/CAN-SPAM guardrails (guidance, not legal advice), and a SEND S-dimension read. Not for B2C lifecycle flows — use email-sequence-designer; not for the consent record — use consent-registry; not for computing EQS — use email-quality-auditor. B2B冷启动外联序列/回复分流/域名预热

日本語の概要は準備中です。原文の説明を表示しています。

Client reporting, quality assurance, and financial operations management. Handles KPI frameworks, compliance audits, budget tracking, and launch checklists. Use when: managing client dashboards, ensuring brand compliance, conducting QA reviews, tracking marketing spend, ensuring GDPR/CAN-SPAM compliance, proofreading deliverables. Also triggers on: client reporting, QA, quality assurance, brand compliance, marketing budget, financial tracking, legal compliance, GDPR, CAN-SPAM, proofreading, launch checklist

日本語の概要は準備中です。原文の説明を表示しています。

Research competitor paid-ad presence, messaging, creative, formats, landing pages, keyword and auction signals, transparent ad libraries, and strategic gaps across supported platforms. Use for competitor ads, ad libraries, ad spy, competitive PPC analysis, competitor creative, Google Ads Transparency, Meta Ad Library, or paid-media competitor research.

日本語の概要は準備中です。原文の説明を表示しています。

Scaffold project/workspaces, apply base structure and configs, and verify dev server startup gate

日本語の概要は準備中です。原文の説明を表示しています。

Orchestrate operational workspace setup before implementation slices across scaffold, CI/CD, hosting, and data provisioning shards

日本語の概要は準備中です。原文の説明を表示しています。

Bu template'in tasarim sistemi referansi — renk (colorScheme + AppThemeColors semantic token'lari), tipografi (textTheme slotlari, Poppins/Inter), spacing/radius/golge/sure token'lari (AppPaddings, AppRadius, AppShadows, AppDurations, AppIconSizes), paylasilan widget katalogu (AppPrimaryButton, dort-durum widget'lari, AppTextField, sheet'ler), 8 varyantli light/dark tema ve easy_localization. Kullanici UI yazarken/duzenlerken "renkleri projeye gore kullan", "bu butonu projeye gore yaz", "hangi spacing/radius", "tasarim sistemine uydur", "style guide", "tema token'lari" dediginde kullan.

日本語の概要は準備中です。原文の説明を表示しています。

Unified workspace maintenance skill. Covers: (1) backing up the workspace to GitHub git repo, and (2) updating OpenClaw and skills. Use when: asked to backup, push to git, update openclaw, update skills, or run maintenance.

日本語の概要は準備中です。原文の説明を表示しています。

Explain how email and Google Calendar work for OpenClaw agents, including the distinction between agent email and owner email, how gog and the Google Workspace skill are used, where related credentials/config live, and how to troubleshoot common setup or access issues. Use when someone asks how an OpenClaw agent accesses Gmail/Google Workspace/Calendar, where credentials are stored, how to use the agent inbox, how to give the agent write access to the owner's calendar, or how to guide another agent/user through the email or calendar setup model.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Contentful — contentful headless CMS management covering space and environment inventory, content type analysis, entry and asset monitoring, locale configuration, webhook tracking, API key auditing, and usage quota monitoring. Use when reviewing content models, investigating publishing issues, monitoring API usage, or auditing space access.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Cursor — cursor AI-powered editor management and team analytics. Covers team seat management, usage tracking, model configuration, rules file analysis, project settings review, and workspace configuration. Use when managing Cursor team licenses, reviewing AI feature adoption, or analyzing Cursor workspace and rules configurations.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Cargo — cargo Rust build and package management. Covers build configuration, workspace management, feature flags, build profiles, cross-compilation, and build script analysis. Use when managing Cargo workspaces, configuring build profiles, debugging compilation issues, or optimizing build performance.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Bitbucket Deep — bitbucket deep platform management covering repository inventory, Pipelines CI/CD monitoring, pull request analysis, branch permission auditing, deployment environment tracking, and workspace member management. Use when auditing repository configurations, investigating pipeline failures, reviewing branch restrictions, or managing workspace access.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Coda — coda document management covering docs, pages, tables, formulas, and workspace analytics. Use when auditing Coda workspace usage, managing documents and tables, querying structured data, or analyzing collaboration patterns across a Coda organization.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Baserow — baserow open-source database platform management covering workspace organization, database and table inventory, field configuration analysis, view management, webhook monitoring, and user access auditing. Use when reviewing database structures, investigating API integration issues, monitoring webhook deliveries, or auditing workspace permissions.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Appsmith — appsmith low-code platform management covering application inventory, workspace organization, datasource health, page and widget analysis, and user access auditing. Use when reviewing internal tool configurations, investigating datasource connectivity, monitoring application deployments, or auditing workspace permissions.

日本語の概要は準備中です。原文の説明を表示しています。

Use Hugging Face Hub via MCP server tools. Search models, datasets, Spaces, papers. Get repo details, fetch documentation, run compute jobs, and use Gradio Spaces as AI tools. Available when connected to the HF MCP server.

日本語の概要は準備中です。原文の説明を表示しています。

Use multiple Claude agents to investigate and fix independent problems concurrently

日本語の概要は準備中です。原文の説明を表示しています。

Expert GitHub Copilot (Copilot Chat, Workspace, CLI, suggestions, enterprise)

日本語の概要は準備中です。原文の説明を表示しています。