「facts」の検索結果

Conduct rigorous, citation-backed desk market research: quick go/no-go market scans, market sizing (TAM/SAM/SOM), competitor analysis, customer demand signals, and trend/macro (PESTEL) analysis. Use this skill whenever the user wants to research, size, validate, or enter a market — "is there a market for…", "how big is the market for…", "who are the competitors of…", "should I build/launch/sell…", "validate this business idea", "market research for…", "market entry" — in any language and for any country's market (e.g. "nghiên cứu thị trường", "étude de marché", "市場調査", "análisis de mercado"), even when the user never says the words "market research". Also use it when another skill or workflow (strategy-board, design-thinking, a product brief) needs external market facts delivered into its fact base or research folder.

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

Foundation skill for warp-route updates. Reads the current on-chain config of a warp route via `hyperlane warp read`, enumerates every artifact (router, ProxyAdmin, ISM, hook, fee contracts) per chain, classifies each artifact's owner (auto-detects Safe / ICA / EOA; asks the user for everything else — Turnkey, Privy, MPC, custom multisig, timelock, etc.), and persists a per-artifact owner table that downstream update skills consume to know which signing path each batch needs. Read-only — no signing, no on-chain mutations.

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

The low-level on-chain probes for identifying what an owner address is — cast code → EOA / EIP-7702-delegated EOA / contract, VERSION() → Gnosis Safe, read-only get-owner-ica.ts derive → ICA derivation, getAccountInfo → Sealevel account existence — with how to interpret each result. The primitive layer beneath validate-owners / resolve-artifacts / update-owners, which each apply their own per-chain or per-artifact policy on top.

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

Generates a structured initial contact summary memorandum from a potential client's first interaction with the firm. Captures case facts, liability indicators, damages, insurance details, and screening criteria. Use during client intake to support conflict checks, case evaluation, and engagement decisions.

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

Analyze latest policy analysis sweep runs (*_policy_analysis_*) by comparing episodes/summary metrics, diagnostics, and video artifacts; generate a concise markdown report and optional frame snapshots.

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

User research reconnaissance — survey existing personas, research docs, interview notes, and feedback artifacts to establish what is already known about users. Use when asked to "what research exists", "review existing personas", "what do we know about our users", or before starting new research or synthesis work.

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

Prevents private infrastructure details (node hostnames, internal project names, local usernames and personal emails, absolute home paths, private and VPN IP ranges) from leaking into public repositories through commits, PRs, docs or release artifacts. Use when working in a public or soon-to-be-public repo, before commits or releases, when writing deployment docs for an OSS project, or when the user asks to "set up the privacy guard", "install privacy-guard", "check for leaks", "protect this public repo". Bootstraps a pre-commit hook backed by a gitignored local denylist plus gitleaks.

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

Use when GSD commands are failing or .planning/ artifacts look inconsistent. Run before any GSD execute-phase or verify-work attempt to catch cross-artifact mismatches early.

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

Traces decisions and requirements through GSD artifacts. Use when user asks "why did we...", "what happened to...", or mentions decision history.

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

Use the moment a request is underspecified and you are about to act on an ASSUMED goal. Enumerate the candidate goals the request could mean, project the action or artifact each one implies, and check whether they diverge: if two or more plausible goals lead to materially different actions or artifacts, ask exactly ONE targeted clarifying question; otherwise proceed on the most-likely goal and state the assumption in one line. Clarification is an evidence-producing action, not a delay — but one question, never an interrogation. Distinct from gsd-spec-phase (GSD-phase-bound, emits a heavy SPEC.md) and intent-router (fetch strategy, not goal disambiguation). Backed by agent goal-state inference (arxiv 2606.16813v1). Triggers on acting under an assumed goal when the request admits more than one materially different reading.

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

Use when the user asks to forge, scaffold, author, or ship a new skill or agent — the skill-creator's own namesake artifacts. Drives the skill-forge loop (create → fill → validate → critique → ship → publish) via the skill-creator CLI.

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

Use when the user asks "what should I work on", mentions GSD phases, ROADMAP, or .planning/ artifacts. Routes to the correct GSD command for the current project state.

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

Composes three-part DACP bundles from skill library artifacts. Determines fidelity level, queries catalog, and records assembly rationale.

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

Generates simulation inputs across fidelity levels — OpenFOAM CFD cases, ngspice netlists, interactive React artifacts, and FreeCAD FEM setups — from verified engineering calculations.

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

Guidance for verifying documentation accuracy against running OpenStack infrastructure. Use when detecting documentation drift, validating operations procedures against live systems, or confirming that runbooks produce expected results on the deployed cloud. Implements NASA Product Verification (SP-6105 SS 5.3) applied to documentation artifacts.

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

Create, read, update, and link GitHub Issues as story artifacts throughout the story lifecycle. Use when managing issues for stories.

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

Write a Gherkin story file to docs/stories/ for a feature. The story IS the spec. No intermediate PROBLEM/SPEC/PLAN/TASKS artifacts.

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

Prisma Compute deployment and hosting guide. Use whenever the user mentions Prisma Compute, `prisma.compute.ts`, `defineComputeConfig`, deploying or hosting a Prisma app, `@prisma/cli app deploy`, `compute:deploy`, `create-prisma --deploy`, `PRISMA_SERVICE_TOKEN`, Compute auth/workspaces, apps/deployments/build logs/domains, localhost vs `0.0.0.0`, deploy port binding, or framework deploy readiness for Hono, Elysia, Next.js, TanStack Start, Astro, Nuxt, Svelte, Nest, Turborepo, or custom/prebuilt artifacts.

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

Apply brand colors and typography to artifacts. Use when brand colors, style guidelines, visual formatting, or company design standards apply. Ensures consistency across branded content.

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

Research a specific technology, library, system, protocol, or tool to answer a concrete technical question with source-traceable evidence. Use when current implementation details, version behavior, configuration, compatibility, or authoritative technical facts must be verified rather than recalled. Also use when explicitly asked to incorporate verified findings into an existing skill.

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

Relay agent results without corrupting exact counts, failure reasons, source scope or status. Use when receiving agent output or handing results to another actor; distinguish observations from attributed conclusions and reference complete artifacts.

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

Use when writing delegation instructions to subagents, authoring CLAUDE.md files, rules, skills, or agent definitions, or auditing existing AI-facing content for bloat. Activates on "write a rule for", "add to CLAUDE.md", "create an agent", "update memory", or any request to author AI-facing instruction content. Removes discoverable data, explained-away knowledge, invented constraints, and stale cached facts.

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

Quantitative cost measurement for technical research — token injection costs, payload sizes, context window consumption, and file-level counts from actual repo files. Use when a technical-researcher orchestrator needs the cost dimension of adding or changing something: how many tokens will it inject, how big are the artifacts, what is the context window impact? This is NOT blast-radius analysis (which files break) — it covers size, tokens, and performance cost only.

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

Use for architecture review, dependency graphs, coupling analysis, or circular dependency detection. Establishes project module namespaces and traces imports plus Claude plugin hook, skill, script, PEP 723, and MCP boundaries. Emits partitioned Mermaid graphs with cycle, coupling, and ownership signals; verifies contract and consequence before assigning severity. Registers diagrams as codebase-analysis artifacts.

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