「rd」の検索結果

Nexscope keyword expansion tool that expands a seed keyword into a list of related keywords with search volume, trends, PPC bids, ranking difficulty, and other metrics, covering 10 Amazon marketplaces including US, UK, DE, JP, etc. Trigger when the user mentions keyword expansion, keyword mining, long-tail keyword mining, related keywords, keyword suggestions, keyword discovery, PPC bid research, keyword competition, keyword discovery, Nexscope keywords, keyword expansion, keyword discovery, keyword scout, related keywords, long-tail keywords, keyword suggestions, PPC bid research, keyword competition, seed keyword expansion, keyword mining. Even if the user does not explicitly mention "Nexscope", if their need involves finding more related keywords and their search volume, competition, and other metrics starting from a seed keyword, this skill should also be triggered.

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

Write, review, discover, lint, format, and validate BIRD 2/3 routing-daemon projects with the @birdcc toolchain. Use for bird.conf, bird2.conf, bird3.conf, bird6.conf, .bird/.bird2/.bird3 files, bird.config.json, birdcc.config.json, include graphs, BIRD filters and protocols, birdcc init/lint/fmt/lsp, or bird -p checks. Treat BIRD 1 as legacy and verify it with the actual BIRD 1 binary. Route editor and CLI installation to birdcc-installer, GitHub Actions to birdcc-cicd, runtime incidents to bird-troubleshooting, and implementation archaeology to bird-source-explorer.

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

🇺🇸 Hardware + SaaS GTM Playbook — End-to-end go-to-market for consumer hardware products with software subscription models. Covers crowdfunding engineering (Kickstarter/Indiegogo/Makuake), KOL matrix for physical products, hardware PMF validation metrics, device-as-funnel subscription design, localization entry timing, and community flywheel mechanics. Built from verified Plaud, Insta360, and DJI case data. 🇨🇳 硬件+软件订阅 GTM 实操手册 — 面向消费硬件产品的完整出海及增长打法。覆盖众筹超额工程（KS/IGG/Makuake）、硬件 KOL 矩阵策略、硬件 PMF 验证、设备即漏斗订阅设计、本地化进入时机判断、社区飞轮构建。基于 Plaud/Insta360/大疆真实案例数据撰写。 🇯🇵 ハードウェア＋SaaS GTMプレイブック — クラウドファンディング（Kickstarter/IGG/Makuake）を起点とした消費者向けハードウェア製品のGTM戦略。KOLマトリクス、PMF検証、デバイスをファネルとするサブスクリプション設計、ローカライゼーション進入タイミング、コミュニティフライホイールまで網羅。Plaud・Insta360・DJIの実例データに基づく。 🇰🇷 하드웨어+SaaS GTM 플레이북 — 크라우드펀딩(Kickstarter/IGG/Makuake) 기반 소비자 하드웨어 제품의 엔드투엔드 GTM 전략. KOL 매트릭스, PMF 검증, 디바이스-as-퍼널 구독 설계, 현지화 진입 타이밍, 커뮤니티 플라이휠 포함. Plaud·Insta360·DJI 실제 사례 데이터 기반. Triggers: "hardware GTM" | "crowdfunding strategy" | "hardware+SaaS" | "Kickstarter launch" | "hardware KOL" | "hardware PMF" | "device subscription" | "hardware product launch" | "consumer hardware growth" | "Makuake" | "众筹策略" | "硬件出海" | "硬件+订阅" | "硬件GTM" | "KS众筹" | "硬件PMF" | "设备订阅" | "硬件冷启动" | "ハードウェアGTM" | "クラファン" | "하드웨어 GTM" | "크라우드펀딩"

Specify a FlexCard before a developer opens Card Designer: the card-state set and the condition that selects each state, the data source type behind each card (DataRaptor, Integration Procedure, Apex remote, SOQL), the action menu users get (navigate, launch OmniScript, Apex, DataRaptor), and every embedded child FlexCard or custom LWC. Produces the artifacts a BA hands to the builder. Trigger keywords: FlexCard requirements, FlexCard BA, FlexCard layout design, FlexCard data sources, FlexCard actions, FlexCard card states, OmniStudio FlexCard scoping. NOT for building the card in Card Designer, NOT for OmniScript step and branching requirements (use admin/omniscript-flow-design-requirements), NOT for standard Lightning record-page component requirements.

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

ScalarDB Cluster および ScalarDB Analytics のアーキテクチャ、サイジング、構成を見積もるスキル。 性能要件、可用性要件、クラウド環境からScalarDB Cluster Pod数、Kubernetes構成、 バックエンドDB、API Gateway、監視システム等の全体構成を見積もる。 ScalarDB Analyticsを使用する場合はEMR/Databricksのサイジングも含む。 使用タイミング: - 「ScalarDBのサイジングを見積もりたい」「ScalarDB環境を構築したい」 - 「ScalarDB Clusterの構成を決めたい」「ScalarDBの費用を算出したい」 - 「開発/テスト/ステージング/本番環境のScalarDB構成」 - CI/CD、Blue/Green、Canary Deploymentを含む本番環境設計 - 「ScalarDB Analyticsを使いたい」「分析クエリ環境を構築したい」 - 「EMR/Databricksのサイジングを見積もりたい」 出力: Markdown形式の見積もり結果 + HTML形式のレポート 費用: USD/JPY両建て（為替レート明記）

taskboard を使わずに動いていたセッションを taskboard のタスクに移す。今の作業（作業ディレクトリ・ブランチ・PR・メモリディレクトリの計画）を確かめ、紐づくタスクを探すか起票してこのセッションを結び、列の説明つきの案内を読み、手元の計画を作業項目に写す。/taskboard-adopt 実行時、「taskboard に移して」「このセッションをタスクに結んで」「taskboard 仕様にして」等の依頼時、taskboard より前から動いているセッション・普段使いの herdr やターミナルで起こしたセッション・古い会話を再開したセッションで SessionStart の taskboard の案内が無いときに使用。境界: 結んだ後の列・作業項目・文書の日々の扱いは /taskboard、pane・agent の操作は /herdr。

[BETA] Expert assistance for the Adobe I/O CLI plugin `@adobe/aio-cli-plugin-aem-rde` — the `aio aem rde` / `aio aem:rde` command tree used to deploy, inspect, log-tail, snapshot, and troubleshoot AEM Rapid Development Environments (RDEs). Activate ONLY when the user explicitly references RDE concepts: 'AEM RDE', 'Rapid Development Environment', `aio aem rde`, `aio aem:rde`, `aem-rde`, RDE snapshots, RDE deploy/install, `rde install`, `rde inspect`, `rde status`, `rde history`, `rde reset`, the `@adobe/aio-cli-plugin-aem-rde` package, or Cloud Manager program/environment configuration that is specifically for an RDE environment. Do NOT activate on generic AEMaaCS phrases like 'deploy to AEM Cloud', 'push my bundle', 'tail the publish log', 'cloud sandbox', or unqualified 'dispatcher-config / frontend / env-config deployments' — those belong to Cloud Manager pipelines, not RDE. This skill is in beta. Verify all outputs before applying them to production projects.

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

Use this skill when building analytics dashboards with nuxt-ui-tools as a package consumer. Covers schema and view functions (defineDashboardSchema, defineDashboardView) that take their context as typed params, useDashboard with a getter that rebuilds on input change, typed injection (useDashboardView, injectDashboard, InferDashboard, InferDashboardView), filters declared inline with the f builder and synced with the URL, memory, or an external store (one value per key across views), headless filters, filter controls and the shipped UI (UiDashboardPage, UiDashboardFilters, UiDashboardFilter, UiDashboardViewTabs) with slot overrides, remote paginated pickers and remoteTableOptions, staged queries (essential / background / deferred) with select and dependent requires, lazy enabled conditions on views, queries, and filters (blocks of disabled queries hidden, grids closing up), derived values, views (tabs), query-scoped filters, number formats (presets, Intl options, useDashboardFormat), and the dashboard blocks (stats with trends, goals, and comparisons, stat groups, gauges, unovis charts with highlights, value labels, and totals, lists with progress rings, bars, funnel, alerts, activity feeds, sortable tables, custom widgets) with their automatic loading, error, empty, and refresh states, card menus, header and footer actions, row actions, drill-down and selected state, card tabs, split cards, comparison periods, auto-refresh, and data freshness.

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

[BETA] Expert assistance for the Adobe I/O CLI plugin `@adobe/aio-cli-plugin-aem-rde` — the `aio aem rde` / `aio aem:rde` command tree used to deploy, inspect, log-tail, snapshot, and troubleshoot AEM Rapid Development Environments (RDEs). Activate ONLY when the user explicitly references RDE concepts: 'AEM RDE', 'Rapid Development Environment', `aio aem rde`, `aio aem:rde`, `aem-rde`, RDE snapshots, RDE deploy/install, `rde install`, `rde inspect`, `rde status`, `rde history`, `rde reset`, the `@adobe/aio-cli-plugin-aem-rde` package, or Cloud Manager program/environment configuration that is specifically for an RDE environment. Do NOT activate on generic AEMaaCS phrases like 'deploy to AEM Cloud', 'push my bundle', 'tail the publish log', 'cloud sandbox', or unqualified 'dispatcher-config / frontend / env-config deployments' — those belong to Cloud Manager pipelines, not RDE. This skill is in beta. Verify all outputs before applying them to production projects.

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

Discover, configure, and connect to Arduino boards from MATLAB using the Arduino Support Package. Use this skill when the user wants to set up an Arduino board, connect to Arduino hardware, find connected boards, scan serial ports, configure Arduino libraries, or any task that requires an Arduino connection as a prerequisite (e.g., blink LED, read sensor, read digital pin, read analog pin, write pin, plot sensor data, scan I2C, use ultrasonic sensor, control servo, read temperature, read voltage, data logging from hardware). Triggers on: arduino, board setup, COM port, serial port, hardware connection, Arduino Nano, Arduino Uno, Arduino Mega, Arduino Micro, Grove, sensor setup, I2C scan, ultrasonic, servo, readDigitalPin, writeDigitalPin, readVoltage, writePWMVoltage, temperature sensor, air pressure, pin read, pin write, analog input.

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

Create iMandalArt 2.2 pure-text 3x3 Mandala index cards with a five-character center axis, eight orthogonal surrounding angles labeled Ⓐ-Ⓗ, compact title cells such as Ⓐ健康復節, hard-line CJK layout, optional の字型 ordering, and 井字號 compass ordering. Use when the user asks for iMandalArt, iMandalart, I MandalArt, の字型, ◊字型, 井字號, 中國城市方位, 64＋8＋1, 手機方形曼陀羅, 正方形九宮索引卡, 五字定格, ◎中心, Ⓐ-Ⓗ 九宮卡, TheBrain/Cerebro preview-safe hard-line cards, or a square 3x3 card that is not a Markdown table, visible-border PE2 card, or 81-cell Mandala.

Nexscope Ozon keyword mining: mines Ozon (and Wildberries) related keywords around a seed keyword with multi-dimensional filtering by search volume, growth, product count, seller count, competitor count, price, relevancy, title density, cart-add conversion, etc. Each mined keyword carries a full market profile (monthly search volume, growth, market space, competitor/seller counts, average price, cart-add conversion, top products). Use for Ozon keyword expansion, long-tail keyword mining, and seed keyword opportunity analysis. Trigger when the user mentions Ozon keyword mining, Ozon keyword expansion, Ozon long-tail keyword mining, find related keywords around a term, Ozon blue-ocean keyword mining, Nexscope Ozon, Ozon keyword mining, Ozon keyword expansion, Ozon related keywords, mine Ozon keywords. Also trigger when the intent is to mine Ozon related keywords around a seed term and view market profiles, even without explicitly mentioning Nexscope.

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

Nexscope Ozon keyword reverse lookup: reverse-looks up Ozon (and Wildberries) search keywords by a list of product SKUs (up to 20), returning which search terms those products appear under (organic/ad search terms), with multi-dimensional filtering by search volume, growth, product count, seller count, competitor count, natural rank, ad rank, exposure, conversion, cart-add conversion, etc. Each keyword carries monthly search volume, growth, market space, competitor/seller counts, average price, cart-add conversion, top products, and organic/ad channel, rank, exposure, and conversion (dimension) market profiles. Use for Ozon keyword reverse lookup, listing keyword optimization, competitor traffic word mining, and ad keyword analysis. Trigger when the user mentions Ozon keyword reverse lookup, Ozon reverse keyword search, Ozon SKU keyword reverse, Ozon product traffic keywords, Ozon competitor ranking keywords, Ozon organic/ad keyword reverse lookup, Nexscope Ozon, Ozon keyword back search, Ozon reverse keyword lookup, Ozon SKU keyword reverse. Also trigger when the intent is to reverse-lookup Ozon search keywords by product SKU and view market profiles, even without explicitly mentioning Nexscope.

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

Use when designing or refactoring record types across objects with many profiles, business processes, or picklist variations. Covers layout assignment explosion, Dynamic Forms migration, and record type ID portability. NOT for basic record type setup or page layout assignment — use admin/record-types-and-page-layouts. NOT for converting one page layout to Dynamic Forms — use admin/dynamic-forms-migration. Trigger keywords: record type consolidation, layout assignment matrix, recordTypeVisibilities, layoutAssignments, Master record type default, bulk RecordTypeId migration, record type audit, RecordType wildcard package.xml.

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

Use this skill for Salesforce Order Management (OMS) tasks: order lifecycle, OrderSummary creation and status, FulfillmentOrder creation and routing, returns, exchanges, cancellations, and platform event subscriptions. Trigger keywords: order management, OrderSummary, FulfillmentOrder, ReturnOrder, ensure-funds, ensure-refunds, submit-cancel, submit-return, adjust-item-submit. NOT for split-order routing or Omnichannel Inventory design — use architect/order-management-architecture. NOT for loading historical orders — use data/commerce-order-history-migration.

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

This skill should be used when the user asks to "communicate via Discord", "send a message to Discord", "check Discord for instructions", "ask a question on Discord", "notify on Discord", "share a file on Discord", "離席する", "離席モード", "Discord で待機して", "Discord待機", or when Claude Code needs to reach the user who is away from the terminal.

Helps DevOps engineers configure mirrord Operator's Kafka queue splitting feature end-to-end. Generates the MirrordSplitConfig and MirrordPropertyList Kubernetes CRD YAMLs (the current resources; MirrordKafkaTopicsConsumer + MirrordKafkaClientConfig are deprecated but still supported), the matching mirrord.json split_queues section with message_filter and jq_filter, and Helm value guidance. Use this skill whenever the user mentions Kafka splitting with mirrord, MirrordSplitConfig, MirrordPropertyList, MirrordKafkaClientConfig, MirrordKafkaTopicsConsumer, Kafka queue/topic splitting, configuring mirrord with Kafka, Kafka Streams splitting, MSK IAM auth, or troubleshooting Kafka splitting sessions. Also trigger on split_queues with queue_type Kafka, or connecting mirrord to a Kafka cluster. This is a Team/Enterprise feature of mirrord.

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

Use this skill when the user is doing hands-on DOCA RDMI (RDMA Initiator) programming — picking doca-rdmi vs doca-rdma for an accelerator-initiated one-sided RDMA flow, standing up a doca_rdmi_connection or doca_rdmi_poster, attaching a doca_dpa_completion or doca_verbs_cq before doca_ctx_start(), retrieving the DPA-side handle for a DPA kernel, auditing whether a doca_rdmi_* symbol is EXPERIMENTAL on this DOCA, or debugging DOCA_ERROR_* returns from RDMI calls. Trigger even when the user does not say "DOCA RDMI" or "initiator" — implicit phrasings include "my DPA kernel needs to post RDMA writes to a remote responder", "DPA kernel sees no completions", "function not found on doca_rdmi_* at link time", "DOCA_ERROR_BAD_STATE from completion attach", or "the DPA posted but the work request never arrived". Refuse and route elsewhere for two-sided or host-CPU RDMA, the DPA programming model, GPU-side RDMA initiation, or general RDMA/IB/RoCE concepts — those belong to other skills.

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

Foodoraの注文履歴や進行中の注文状況、到着情報を確認します。状態の継続監視や注文詳細の取得に加え、過去の注文の商品をカートに追加する操作も扱います。

• 注文状況と到着情報を確認したいとき
• 進行中の注文を継続監視したいとき
• 過去の注文詳細をJSONで取得したいとき

Nexscope Ozon market hot keyword search: filters Ozon (and Wildberries) market keywords by multi-dimensional metrics including search volume, growth, product count, seller count, competitor count, price, sales, conversion concentration, etc. Each keyword carries monthly search volume, growth, market space, competitor/seller counts, average price, cart-add conversion, top products, and market profile. Use for Ozon keyword selection, blue-ocean keyword mining, and market opportunity analysis. Trigger when the user mentions Ozon hot keywords, Ozon keyword market analysis, Ozon keyword selection, Ozon blue-ocean keywords, Ozon search volume, Wildberries keywords, Nexscope Ozon, Ozon market keyword search, Ozon keyword research, blue ocean keywords Ozon. Also trigger when the intent is to filter Ozon market keywords by metrics and view market profiles, even without explicitly mentioning Nexscope.

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

PRD 架构师 / 需求文档起草：当用户要把一个产品想法、需求草稿、脑暴结果或功能说明整理成 PRD 时使用。 可用中文唤起：“帮我写 PRD”“帮我选 PRD 模板”“把这个需求整理成 PRD”“判断该用轻量 PRD 还是标准 PRD” “补一张可编辑 Draw.io 核心流程图”“PRD 里加架构图”。 会在 PRD-lite、PRD-standard、PRD-ai-native 中选择一个模板资产按需加载，并在需要时加载 mockup handoff、 Draw.io 图示或开发 handoff 附录；页面型 PRD 默认联动生成项目 UI 对齐的 HTML、关键截图和正文证据。 不用于直接编码、单纯画 UI，或评审一份已经写好的 PRD。

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

Make a WooCommerce plugin HPOS-compatible (High-Performance Order Storage, default-on in WC 10.x) — declare via FeaturesUtil::declare_compatibility on before_woocommerce_init, replace $wpdb->postmeta / WP_Query order code with wc_get_orders + WC_Order::get_meta / update_meta_data, gate runtime branches on OrderUtil::custom_orders_table_usage_is_enabled, build admin hook names dynamically with OrderUtil::get_order_admin_screen (HPOS = woocommerce_page_wc-orders, legacy = shop_order). Use when scaffolding an order-touching plugin, auditing existing code for HPOS readiness, or fixing post-WC-10 silent breakage. Triggers on shop_order, get_post_meta with order context, FeaturesUtil, OrderUtil, custom_order_tables, before_woocommerce_init.

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

World-class expertise in TCG/CCG design, resource systems, and metagame balanceUse when "card game design, TCG design, CCG design, trading card game, collectible card game, mana curve, deck building, card templating, keyword mechanic, set design, draft format, limited format, card rarity, color pie, faction design, card balance, magic the gathering style, hearthstone style, deckbuilder, card text, rules text, card-game, tcg, ccg, trading-card, collectible-card, deck-building, mana-curve, draft, limited, constructed, set-design, card-templating, mechanics, keywords, rarity, balance" mentioned.

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

Use Nexscope data to reverse-lookup traffic keywords for any Amazon ASIN, including organic ranking, ad ranking, search volume, traffic share, organic/paid scores, ABA TOP3 click concentration, click conversion rate, year-over-year search volume changes, and weekly/monthly time windows. Trigger when the user mentions ASIN keyword analysis, ASIN reverse lookup, traffic keyword research, organic ranking query, ad ranking query, keyword position tracking, Nexscope keyword data, competitor keyword peeking, viewing which keywords drive traffic to a product, analyzing keyword performance for a specific ASIN, time windows by week/month/recent N days, ASIN reverse keyword lookup, traffic keywords, organic ranking, ad ranking, search volume, Nexscope keywords, competitor keyword reverse lookup, click concentration, click-to-purchase conversion, week-over-week search volume. Even if the user does not explicitly mention "Nexscope", if their need involves finding keywords associated with a specific Amazon product (ASIN), this skill should also be triggered.

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