「rd」の検索結果

Turn a rough ask into a clear work order. Use when the ask is rough, unspoken, or double-readable — before planning or building.

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

Freeze outside-the-repo state into one snapshot. Use when the work depends on the current state of a service, database, queue, third party, or live logs.

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

Bring how named experts would think about the question. Use when the user wants expert thinking on a tradeoff, choice, or stuck problem — not a verdict.

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

Report where a session missed moo's standard — the agent asks only while stating intent and shape, then works on its own — as issues a builder can act on. Pass a session id to report on a past session instead of this one.

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

Define how unsupervised work is judged before it runs. Use when work will run without a human watching, optimizing toward something.

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

Capture reproducible screenshots from the currently booted iOS Simulator and turn them into three App Store marketing cards with validated dimensions and concise copy. Use after a successful Simulator build, during the two-minute proof lane, or when replacing prototype images with real app captures.

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

Produce a truthful Japanese App Store metadata pack and app-name shortlist in twelve minutes without a multi-agent research round. Use for a live launch sprint, fallback ASO copy, app naming under a hard deadline, or when local product evidence is available but market research is intentionally deferred.

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

Use when the user needs to write, rewrite, review, or critique commercial copy meant to drive a reader toward action — landing pages, hero sections, headlines, email (cold outreach, nurture, promo, launch), CTAs, microcopy, product descriptions, value propositions, ads, or taglines. Also for copy audits, clarity checks, conversion reviews, or choosing a framework (AIDA, PAS, BAB, FAB, 4U's). Applies even when the user just says "write me an email" or "review this page." Not for channel/budget strategy (use channel-expert) or pricing structure (use pricing).

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

Use when the user wants to get found in Google or AI engines (ChatGPT, Perplexity, AI Overviews) — keyword and content strategy, technical or content SEO audits, schema markup, link building, topical clustering, E-E-A-T, AI citation (AEO), or deciding whether SEO is even the right channel for their startup. Calibrated for early-stage, low-authority sites. Not for paid acquisition or channel-mix/CAC analysis (use channel-expert), or writing the page copy itself (use copywriter-skill).

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

Use when the user needs to scope, write, or audit a product spec — a PRD, feature spec, user stories, acceptance criteria, or a "spec this out"/"break this into stories"/"definition of done" request — or wants an existing spec reviewed for gaps and anti-patterns. Triggers whenever a feature idea needs to become structured requirements that align a team on what to build. For the analytics behind success metrics, use data-analysis; for the technical design, use software-architect.

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

Use when the user needs to design, run, or audit product or GTM analytics — metric hierarchies and north stars, funnels, cohort retention, churn, pipeline velocity, forecasting, lead scoring, NRR, A/B tests, or analytical SQL — or uploads a dataset to analyze. Triggers on questions like "why did activation drop", "is this metric meaningful", "review my dashboard", or "what should I measure". For writing the spec that defines a feature's success metrics, use product-spec.

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

Use when a SaaS founder is deciding on or building a product-led growth motion — assessing PLG readiness, choosing freemium vs free trial vs reverse trial, defining activation and PQLs, designing self-serve onboarding and conversion triggers, building viral loops, or setting up PLG metrics (NRG, activation rate, TTV, NDR, CAC payback) and cohort analysis. Also for hybrid product-led-sales design and PLG-vs-sales-led GTM decisions. Not for paid acquisition channel mix (use channel-expert) or the mechanics of price points and tiers (use pricing).

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

Use when a SaaS founder needs to set, audit, or redesign pricing — choosing a value metric, structuring tiers and packaging, setting price points, designing discounts, planning a price increase, or optimizing a pricing page. Also for monetization questions like free-to-paid conversion, expansion revenue, willingness-to-pay research, or per-seat vs usage-based. Not for which acquisition channels to use (use channel-expert) or the wording of the pricing page (use copywriter-skill).

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

Maintain and publish the advisor-owned current research state, durable research-ideas syntheses, and dataset analysis. Use when evidence or human guidance changes the research focus or direction, durable research ideas should be recorded, or dataset understanding changes.

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

Create consistent nn_cfd W&B experiment comparison reports from selected run IDs using wandb and wandb_workspaces. Use this whenever the user asks to report experiment results, create a W&B Report, compare CFD training/eval runs, document baseline-vs-variant outcomes, reproduce the project experiment report template, or publish a leaderboard-style report for milieu/nn_cfd.

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

Coach the user through a rigorous, repository-grounded interview to create or improve program.md. Use when a target repository lacks program.md, its goals, metrics, data, or guardrails are unclear, or the user asks to be grilled about an autoresearch setup.

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

Choose, configure, launch, and collect bounded subagents for research and engineering decisions. Root agents and delegation-capable subagents should read this before delegating: every task requires an explicit model tier, and high-leverage work such as research ideation, round planning, plateau pivots, large research reviews, hard optimization, disputed evidence, and expensive experiment portfolios requires frontier judgment.

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

This skill should be used when the user says "找 bug" / "看一下有没有 bug" / "smart-qa" / "/smart-qa" / "帮我测一下这个项目" / "智能 QA" / "推断业务流程测一下"，or asks for an autonomous bug-hunt where they DON'T already know what to test. Distinct from `qa` (blind exploration) and `devtest` (verifies a specific change). smart-qa READS the project source — prefers PRD/requirements docs, falls back to code (activities, routes, click handlers, API calls) — then proposes a focused test plan for confirmation before driving the app. v1 stops after the user confirms the plan and hands off to the existing `qa` skill for execution. v2 (planned) adds per-step assertions.

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

ES — Critica a fondo una idea, plan, pitch o proyecto entero sin validar ni adular: asume que va a fracasar y lo demuestra por ocho ángulos (premisas, mercado, competencia, viabilidad, números, ejecución, pre-mortem y punto ciego), investiga fracasos reales cuando hay herramientas, y entrega un veredicto franco con la lista priorizada de qué arreglar. Activar con /abogado-del-diablo, "hazme pedazos esto", "critica mi idea sin filtros", "dime por qué va a fallar", "destruye este plan", "segunda opinión brutal", "pre-mortem". EN — Harshly critiques an idea, plan, pitch, or whole project without validating; assumes it will fail and proves it across eight angles, then returns a blunt verdict with a prioritized fix list. Trigger on "devil's advocate", "red team this", "tear this apart", "why will this fail", "brutal second opinion", "pre-mortem".

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

Run an authorized task inside an Available Work Time (AWT) window with a shorter Closeout Grace Period (CGP), fixed deadlines, forecast checks, proportional convergence points, and a hard stop. Use when the user explicitly requests timeboxing, supplies an AWT/CGP pair, says AWT or CGP, or an applicable project policy requires the protocol. Do not invent durations or activate timeboxing merely because a task may take time.

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

Orchestrate complex development with AUTOMATIC parallel subagent execution, continuous dispatch scheduling, dependency analysis, file conflict detection, and IOSM quality gates. Analyzes task dependencies, builds critical path, launches parallel background workers with lock management, monitors progress, auto-spawns from discoveries. Use for multi-file features, parallel implementation streams, automated task decomposition, brownfield refactoring, or when user mentions "parallel agents", "orchestrate", "swarm", "continuous dispatch", "automatic scheduling", "PRD", "quality gates", "decompose work", "Mixed/brownfield".

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

Use when collecting sampling profiles with perf record, reading perf report or perf annotate, measuring PMU counters with perf stat -e, or using PAPI instrumentation to interpret IPC, miss rates, MPKI, or memory bandwidth on Linux. Not for SVG rendering: use flamegraphs.

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

Use when writing Cortex-M NVIC ISRs, configuring priorities, handling HardFault, tail-chaining, or measuring interrupt latency. Not for the vector table itself: use baremetal-startup.

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

Use when choosing a linker, fixing link order or undefined symbol errors, enabling LTO or ThinLTO, or cutting dead code with --gc-sections. Not for inspecting the linked binary: use elf-inspection.

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