5,499 件 ・ 関連度順
概要と使いどころ
Query Walmart US category market research through the Nexscope research proxy. Use when the user requests this public marketplace or patent data; do not use for seller-console or store-authorized operations.
日本語の概要は準備中です。原文の説明を表示しています。
Query Walmart US keyword research through the Nexscope research proxy. Use when the user requests this public marketplace or patent data; do not use for seller-console or store-authorized operations.
日本語の概要は準備中です。原文の説明を表示しています。
Query TikTok public video rankings from Nexscope through the Nexscope research proxy. Use when the user requests this public marketplace or patent data; do not use for seller-console or store-authorized operations.
日本語の概要は準備中です。原文の説明を表示しています。
Query Mercado Libre public market intelligence through the Nexscope research proxy. Use when the user requests this public marketplace or patent data; do not use for seller-console or store-authorized operations.
日本語の概要は準備中です。原文の説明を表示しています。
Query Google Patents public search through the Nexscope research proxy. Use when the user requests this public marketplace or patent data; do not use for seller-console or store-authorized operations.
日本語の概要は準備中です。原文の説明を表示しています。
Query Etsy public listing details through the Nexscope research proxy. Use when the user requests this public marketplace or patent data; do not use for seller-console or store-authorized operations.
日本語の概要は準備中です。原文の説明を表示しています。
Query 1688 public product details through the Nexscope research proxy. Use when the user requests this public marketplace or patent data; do not use for seller-console or store-authorized operations.
日本語の概要は準備中です。原文の説明を表示しています。
Authorize Amazon Ads accounts, manage SP, SB, and SD entities, and retrieve advertising reports.
日本語の概要は準備中です。原文の説明を表示しています。
Authorize Amazon Ads accounts and inspect safe connection and profile metadata.
日本語の概要は準備中です。原文の説明を表示しています。
Authoring Storybook stories, component catalogs, and Visual Regression integration (CSF 3.0/Factories, Storybook 10 ESM-only, React Cosmos). Use when building a component catalog.
日本語の概要は準備中です。原文の説明を表示しています。
Authoring standalone and cross-team specifications: PRD/SRS/HLD/LLD, staged L0-L4 unified packages, BDD acceptance criteria, and traceability. Use for technical or multi-audience documentation; not implementation or architecture decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Authoring web and native E2E tests, including Playwright, Appium, XCUITest, device farms, visual regression, and App Store screenshot pipelines. Not for unit/load tests.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzing dependencies, circular references, and God Classes; authoring ADRs/RFCs. Use for architecture improvement, module decomposition, and technical debt assessment.
日本語の概要は準備中です。原文の説明を表示しています。
Converting a supplied prompt into an executable specification: detects vague quality/quantity/explanation/style/design/technical/judgment wording, role and persona theater, and self-contradiction, then replaces each with a numeric bound, an observable behavior, or a scorable criterion — with a per-term ledger of what changed and what stayed open. Don't use for AI system design, RAG, or eval harnesses (Oracle), PRD/SRS authoring (Scribe), spec conformance verification (Attest), or SKILL.md normalization (Gauge).
日本語の概要は準備中です。原文の説明を表示しています。
Builds a talk as a beatdeck - a fixed 1920x1080 React stage where one click is one beat, with authored motion, presenter view, overview, and an offline self-contained build. Covers turning source material (PPTX, Keynote/PDF export, Markdown, notes) into a content audit and a scene/beat map, choosing or applying a theme, writing scene layers, automatic beats, and verifying every beat with npm run verify. Use whenever the task is creating, porting, restyling, rehearsing or fixing a presentation, talk, keynote, slide deck or conference session that should feel like a live system rather than slides, or whenever the repo contains src/beatdeck/.
日本語の概要は準備中です。原文の説明を表示しています。
Run before writing or changing code for any feature, bug fix or refactor that touches data, jobs, money, outside services or user-facing behaviour. Finds where the change will break before it is built, by walking ten named failure classes (twice, halfway, outside call, failure-is-not-empty, neighbors, endings, money, hostile user, words, scale and time) against the code, and writes the answers into the plan. Use when planning a change, when asked to "think it through", "cover the gaps", "make sure it's bug free", or before any edit to payment, publishing, deletion, auth or background-job code.
日本語の概要は準備中です。原文の説明を表示しています。
Govern mini-program release readiness and evidence across source branches, semantic versions, build artifacts, test flags, debug paths, sensitive data, permissions, privacy declarations, platform uploads, review submissions, staged versions, production releases, and rollback plans. Use when users ask for a release checklist, packaging, export, version bump, upload readiness, submission readiness, launch status, rollback preparation, or a precise judgment of what has and has not shipped. Defaults to read-only preflight, requires separate explicit authorization for every external state change, and never treats a Git push, successful build, platform upload, review submission, approval, or production publication as interchangeable.
日本語の概要は準備中です。原文の説明を表示しています。
The learner teaches the concept to the AI, which plays a curious novice peer and identifies gaps through authentic questions. Use when the learner wants to test their understanding — teaching forces a different kind of organisation than studying.
日本語の概要は準備中です。原文の説明を表示しています。
Design a project-based learning brief with a driving question, milestones, and assessment criteria. Use when planning PBL units, inquiry projects, or extended investigations.
日本語の概要は準備中です。原文の説明を表示しています。
Map curriculum connections across multiple subjects for a real-world problem or authentic context. Use when planning cross-curricular projects or connecting content to real issues.
日本語の概要は準備中です。原文の説明を表示しています。
Write or fix a profile.yml — pick the right resource kind for each file, bind operating references, and verify the install layout before publishing. Use when creating a ForgeCat profile, adding a skill/agent/rule/hook to one, or when `forgecat validate` or `plan` reports something unexpected.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to plan, build, or optimize SMS or MMS marketing — including welcome flows, abandoned cart texts, post-purchase, win-back, promotional sends, or transactional/auth SMS. Also use when the user mentions "SMS marketing," "text message campaigns," "SMS sequence," "SMS automation," "abandoned cart text," "post-purchase SMS," "Klaviyo SMS," "Postscript," "Attentive," "Twilio," "A2P 10DLC," "TCPA," "SMS compliance," "short code," "toll-free SMS," "MMS campaign," "should I do SMS," or "SMS vs email." For email sequences, see emails. For SMS copy framing, see copywriting. For opt-in popups that capture phone numbers, see popups.
日本語の概要は準備中です。原文の説明を表示しています。
Hardens code against vulnerabilities. Use when auditing an input handler for vulnerabilities, when handling user input, authentication, data storage, or external integrations, or when checking a login flow is safe against the OWASP Top Ten. Use when building any feature that accepts untrusted data, manages user sessions, or interacts with third-party services. Use when auditing dependencies for known vulnerabilities, triaging package-manager audit findings, or assessing supply-chain risk in a new package. Use when personal data or privacy compliance (GDPR, CCPA) is involved.
日本語の概要は準備中です。原文の説明を表示しています。
Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when you want every assumption cross-examined before proceeding, when stress-testing a plan for hidden failure modes, when correctness matters more than speed, when working in unfamiliar code, when stakes are high (production auth, security-sensitive logic, a high-stakes migration, irreversible operations), or any time a confident output would be cheaper to verify now than to debug later.
日本語の概要は準備中です。原文の説明を表示しています。