UI/UX、ロゴ、スライド、画像生成（7,518 件）
概要と使いどころ
Use when a web project needs business goals, audience, information architecture, conversion priorities, content hierarchy, constraints, or design CTQs clarified before visual design begins.
日本語の概要は準備中です。原文の説明を表示しています。
Use for a focused high-craft polish pass after structure and art direction are stable; improves typography metrics, spacing rhythm, imagery crop, surfaces, optical alignment, micro-interactions, and restrained detail without redesigning the whole page.
日本語の概要は準備中です。原文の説明を表示しています。
Use when screenshots, websites, moodboards, competitors, or visual examples are provided and the task needs design DNA extraction, comparison, remixing, or translation into an original design direction.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a timestamped rainfall CSV (design storm, gauge record, climate-scenario series) into a MIKE+ rainfall .dfs0 via the mike-plus MCP server, verified by read-back, ready to drive a model's rainfall boundary or to sit on top of a hydrograph figure. Use when the user brings rain as CSV or asks to run a model with a different storm. No license required (writing the file); wiring it into the model needs one.
日本語の概要は準備中です。原文の説明を表示しています。
当用户在设计故事营销、内容营销或品牌叙事时，需要确保品牌信息随故事一起被传播时调用此 skill。核心信号：用户在构思"品牌故事""病毒视频""内容营销"，希望故事不仅被传播还能带动品牌。不适用于：纯品牌曝光（如Logo植入）、纯娱乐内容（不承载商业信息）、新闻公关事件（非叙事驱动）。关键触发：涉及"讲品牌故事""做病毒视频""内容怎么植入品牌"的场景。
日本語の概要は準備中です。原文の説明を表示しています。
当用户在想"怎么让别人看到我的产品""怎么让用户使用产品的行为被更多人注意到""产品是私密的怎么推广"时激活此 skill。 典型触发信号：用户的产品是私下使用的（如软件、药品、内衣），或在问"为什么好产品没人知道"。 不适用于：纯广告投放策略、内容营销、或与"可见性"无关的品牌问题。 核心判断：用户是否在试图解决"产品使用行为不可被观察"的传播瓶颈。
日本語の概要は準備中です。原文の説明を表示しています。
UI stack, build, and test conventions for NV oOS React SPA addons (toolkit-shell, chat-spa, schedule-anything-spa, saas-controller) — three sanctioned build patterns plus the standalone Pro SPA Vite app (examples/nvoos-pro-spa-vite), dual-React guard, headless component rules, NDS tokens, Tailwind v4, @xyflow/react v12, vitest/jsdom gotchas, the full-JS-rebuild map, and the TS-shadows-JS webpack gotcha. Use when building or modifying SPA addon UI, writing SPA JS tests, upgrading SPA deps, or rebuilding JS for packaging.
日本語の概要は準備中です。原文の説明を表示しています。
Manage AI assistant configurations and peer-to-peer mesh network connections in the NV oOS Pro Toolkit. Covers assistant creation, model configuration, provider setup, peer discovery, mesh networking, and cross-assistant communication. Use when creating or editing AI assistants, configuring model providers, setting up peer connections, managing mesh network topology, or debugging assistant behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Author and validate nvoos-chart fenced-JSON chart blocks for NV oOS chat surfaces — 29 chart types across distribution, part-to-whole, ranking, change, special and grid families. Covers type selection, the v2 schema (values/series/data.items, mode, sort, direction, unit, animate, table, target), data-shape rules, the create_chart_fence server validator, the a11y checklist, and copy-paste JSON templates. Use when writing chart fences in assistant responses, choosing a chart type for data, validating chart JSON, or deciding between nvoos-chart, create_chart, generate_chart and generate_mermaid.
日本語の概要は準備中です。原文の説明を表示しています。
Agentic design-to-build pipeline that turns a Figma design into a built WordPress site using the Figma MCP server (read side) and the Elementor MCP server (write side) attached as MCP Apps on an NV oOS assistant. Covers the 7-stage pipeline (Scope → Read → Plan → Tokenize → Build → Verify → Handoff), the normative stage rules (get_design_context first, tokenize before build, drafts only, never publish, Figma read-only), the build-manifest contract (schema + example in reference/build-manifest.md), the design-file contract (frame/section/variable naming in reference/design-file-contract.md), assistant wiring (figma + elementor MCP Apps, OAuth + application passwords, host allowlist), safety rules, and troubleshooting. Use when asked to build or create a site, page, or landing page from a Figma design, to wire Figma MCP or Elementor MCP for design-to-build work, to approve or produce a build manifest, or to debug a failed design-to-build run.
日本語の概要は準備中です。原文の説明を表示しています。
Use when migrating a CopilotKit v1 application to v2 -- updating package imports, replacing deprecated hooks and components, switching from GraphQL runtime to AG-UI protocol runtime, and resolving breaking API changes.
日本語の概要は準備中です。原文の説明を表示しています。
Use when building custom agent backends, implementing the AG-UI protocol, debugging streaming issues, or understanding how agents communicate with frontends. Covers event types, SSE transport, AbstractAgent/HttpAgent patterns, state synchronization, tool calls, and human-in-the-loop flows.
日本語の概要は準備中です。原文の説明を表示しています。
Use when wiring an external agent framework (LangGraph, CrewAI, PydanticAI, Mastra, ADK, LlamaIndex, Agno, Strands, Microsoft Agent Framework, or others) into a CopilotKit application via the AG-UI protocol.
日本語の概要は準備中です。原文の説明を表示しています。
Guide users through a 6-phase pipeline to plan a complete project — from brainstorming through project metadata to blueprint, starter-file generation, and per-milestone micro-task design with inline pedagogical choreography.
日本語の概要は準備中です。原文の説明を表示しています。
reqordデータ（Requirement, Specification, ProjectContext）の編集・改善を統合的に行う。reqのSMART品質改善、specのdesign.md技術設計書の生成・更新、contextの充実化をカバーする。
Reqordの要件・仕様の実装進捗ダッシュボードを表示する。ステータス別集計、design.md準備状況、未解決フィードバックを一覧表示する。
WooCommerce Stripe Gateway skill for the fragile My Account payment-methods and add-payment-method flows. Use when editing or replacing Woo account templates, payment-methods.php, form-add-payment-method.php, Stripe card/token UI, saved cards, SetupIntent, Payment Element/UPE, billing details, WC payment tokens, customer account payment-method endpoints, Subscriptions change-payment-method compatibility, or code contains add_payment_method, add-payment-method, form#add_payment_method, payment_method_stripe, wc-stripe-upe-element, wc-stripe-setup-intent, stripe_source, wc_stripe_create_setup_intent, wc_stripe_upe_params, wc-stripe-payment-method, or woocommerce-gateway-stripe.
日本語の概要は準備中です。原文の説明を表示しています。
Registers a custom settings tab in the JetFormBuilder admin Settings page using the official JFB API — PHP-side Base_Handler subclass for persistence, JS-side wp.hooks filter for the Vue tab component, native cx-vui field components for the UI. Use when a plugin needs its own configuration tab inside JFB Settings (API credentials, defaults, debug flags, third-party integrations) and the developer must NOT roll their own admin page. Triggers on mentions of "JetFormBuilder settings tab", "JFB settings page", "Base_Handler", "register-tabs-handlers", "jet.fb.register.settings-page.tabs", "cx-vui-input", or when a JFB-companion plugin is being scaffolded.
日本語の概要は準備中です。原文の説明を表示しています。
Curated WooCommerce Subscriptions hook and extension-point map for choosing the right action/filter around WC_Subscription creation, status transitions, date changes, renewal orders, scheduled payments, payment retries, gateway events, switching, gifting, related orders, REST/API responses, and account/admin UI. Use when the user asks for a Woo Subscriptions hook list, "where should I hook", "after renewal", "subscription status changed", or when code contains WC_Subscription, wcs_create_subscription, wcs_create_renewal_order, woocommerce_scheduled_subscription_payment, wcs_renewal_order_created, payment_retry, wcs_get_subscriptions, wcsg_, subscription_switch, _subscription_switch_data, _recipient_user, wcsg_recipient, or subscription switching.
日本語の概要は準備中です。原文の説明を表示しています。
Design and execute DAG-based automation workflows using the NV oOS Pro Workflow Builder — a ReactFlow visual builder for chaining tool calls, agent runs, and actions into repeatable pipelines. Covers the visual builder UI, 9 preset categories, 10 node types, Kahn's algorithm execution engine, scheduling via Pro Schedule Manager, template variable syntax, and best practices. Use when designing workflows, debugging DAG execution failures, choosing between a workflow schedule and raw tool chaining, or building CRM/PM automation pipelines with toolkit_cpt nodes.
日本語の概要は準備中です。原文の説明を表示しています。
Provision a client-brand AI assistant in the NV oOS Pro Toolkit — brand intake, system-prompt authoring, tool selection, an idempotent provisioning script, credentials, and end-to-end verification. Use when creating a brand manager or social media assistant for a client brand (e.g. Aerlinn), onboarding a new brand into the Design Stack, replicating an existing brand assistant, or updating a brand assistant's prompt, tools, or campaign copy.
日本語の概要は準備中です。原文の説明を表示しています。
Registers a custom WooCommerce shipping method with explicit control over which fields appear in the per-zone settings modal — extend WC_Shipping_Method, declare your fields in init_form_fields (and ONLY those fields, no unset / DOM hacks / CSS hides), set the $supports array to control whether the modal opens (omit 'instance-settings' to suppress it entirely), register via the woocommerce_shipping_methods filter, load the class on woocommerce_shipping_init. Corrects the "this is React, removing fields is hard" misconception — the zone-method modal is Backbone with a PHP-rendered settings_html string; the field list is wholly PHP-controlled. Use when scaffolding a shipping method or when you want a feature-flag-only modal without WC defaults. Triggers on WC_Shipping_Method, woocommerce_shipping_methods, woocommerce_shipping_init, init_form_fields with shipping context, $supports shipping-zones, calculate_shipping, add_rate, or "remove default fields from shipping method".
日本語の概要は準備中です。原文の説明を表示しています。
Design custom action/filter hooks emitted by a plugin: action vs filter semantics, prefixed names, docblocks, parameter stability, *_ref_array forwarding, and deprecated hook migration. Use when adding, reviewing, evolving, or deprecating a public hook surface. Triggers on do_action, apply_filters, apply_filters_deprecated, do_action_deprecated, apply_filters_ref_array, do_action_ref_array, did_action, did_filter, or hook @since docblocks.
日本語の概要は準備中です。原文の説明を表示しています。
Register and enqueue WordPress plugin scripts/styles with modern loading behavior, especially WP 6.9 fetchpriority support, script module args, footer placement, inline style limits, and removal of legacy IE conditional asset support. Covers wp_enqueue_script args strategy/in_footer/fetchpriority, wp_register_script_module / wp_enqueue_script_module args, wp_script_add_data, wp_style_add_data, dependency handles, conditional enqueueing on the right hook, and avoiding global frontend/admin asset bloat. Use when adding or reviewing plugin JS/CSS enqueue code.
日本語の概要は準備中です。原文の説明を表示しています。