「first run」の検索結果

Produce a standalone test plan by analyzing code for test coverage gaps and edge cases. Use when you need to create, generate, or draft a test plan for a branch, need to analyze test coverage, or need to identify what tests to write for specific files or directories. Does not produce a plain-language plan for a person to run tests by hand — use manual-test-planning for that. Does not write test code — use tdd to implement behavior test-first. Does not refine existing plans — use iterative-plan-review. Does not review code quality, security, or style — use code-review for full code review. Does not evaluate architectural testability or structural coupling — use architectural-analysis for architectural assessment.

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

Turn a work-items.md file (produced by /plan-work-items) into Linear issues, one per slice, in a single target Linear team. Use when you want to publish work items as Linear issues, create implementation tickets to track in Linear, or push a broken-down plan into a Linear team. Requires a configured Linear MCP server and a target team. Reads the team's real workflow states, labels, Projects, and members and resolves every option against them before creating anything; defaults each issue to the team's initial state, unassigned, uncategorized, with no parent or Project unless you ask. Links within-file `Depends on` relationships as native Linear "blocked by" relations and annotates the source file so re-runs resume cleanly. Does not produce the work-items file itself — use plan-work-items first. Does not post to Jira — use work-items-to-jira. Does not post to GitHub — use work-items-to-issues.

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

Builds a feature implementation plan from an existing feature specification (or equivalent context) through a facilitated team conversation. Use when the user wants to plan how to implement, build, deliver, or ship a feature that has already been specified. Does not specify what the feature should do — use plan-a-feature first. Does not design the contract for an interface — use design-an-api. Does not refine or stress-test an already-written plan — use iterative-plan-review. Runs its resolution rounds to completion and holds its questions until after they finish; to review each round as it lands, use pairing.

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

Generate video clips on the user's own GPU through Guaardvark: text-to-video, image-to-video, first+last frame animation, clips with their own soundtrack and dialogue (MiniMax H3), short looping animations, and batch runs. Use when the user asks to make, render, animate, or batch-generate video locally.

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

Scan code, dependencies, containers, IaC and SBOMs with Snyk via its first-party MCP server: authenticate, trust a folder, run the right scanner, read the findings, fix and re-scan. Includes package-health checks before adding a dependency.

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

Run your first computer-use test in minutes.

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

Scaffold a project, connect TestDriver to your AI client, and run your first test.

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

Use when the user wants to open a pull request or finish a branch handoff. Read the PR template, inspect changes vs main, run the release skill first if the branch name looks like a version, validate the branch with the shared repo checks, open a draft PR targeting main, and return the preview deployment URL when one applies.

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

TypeScript-first schema validation and type inference. Use for validating API requests/responses, form data, env vars, configs, defining type-safe schemas with runtime validation, transforming data, generating JSON Schema for OpenAPI/AI, or encountering missing validation errors, type inference issues, validation error handling problems. Zero dependencies, compact core (~5kb gzipped; zod/mini ~1.9kb).

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

Run an honest market-fit and viability audit of any project or idea and produce a decision doc, not code. Use when someone asks "is this viable as a business", "audit the market fit", "make the case and compare to competitors", "should I apply to YC or bootstrap", or wants to validate a project, product, or market before investing more time. Gathers verifiable traction data first, researches the competitive field, gets an independent cold read, writes a doc with pre-committed pass/middle/kill criteria and a concrete week-1 assignment, then hardens it with an adversarial review loop.

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

Investigate an alert or incident in this channel: classify the symptom, load the matching triage reference, check lessons.md for known causes, and post a grounded first-pass diagnosis with evidence links and a proposed (never executed) fix. Use when an alert fires, a routine detects a new anomaly, or someone reports something broken ("tests aren't running", "deploys look stuck", "is CI down?").

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

Refresh the data tables in optimal-blog.md from master.db. Checks the data for integrity problems FIRST, then runs the generator that picks per-language winners and splices every GEN-marked table, then reconciles the surrounding prose. Use after new experiment results land, or when the optimal-blog numbers are stale.

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

Think and work like an expert Manufacturing Engineer. Use when a task calls for Manufacturing Engineer judgment. Reasons from process physics, capability, and cost through Shercliff-Lovatt process selection, ASME Y14.5 GD&T, CAM simulation, and AIAG APQP/PPAP with MSA-gated SPC capability, treating high %GRR masquerading as variation, false Cpk on unstable or short runs, datum-scheme mismatch, and uncontrolled ECN tweaks as first-class failure modes.

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

Think and work like an expert Human–Computer Interaction Researcher. Use when a task calls for Human–Computer Interaction Researcher judgment. Reasons from situated context, Fitts/GOMS/KLM, and CHI contribution types; runs contextual inquiry through LMM/CLMM analysis with SUS/NASA-TLX triangulation; uses Prolific/OSF and treats demand characteristics, novelty effects, ordinal misuse, and WEIRD samples as first-class failure modes.

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

Think and work like an expert Hydrologist. Use when a task calls for Hydrologist judgment. Reasons from hydrologic-cycle closure (P = ET + Q + ΔS + I), runoff-generation mechanisms, and channel routing through HEC-HMS, HEC-RAS, the National Water Model, and split-sample KGE/NSE/PBIAS calibration, while treating post-flood rating-curve shifts, radar QPE bias, snow/rain misclassification, and non-stationarity in extremes as first-class failure modes.

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

Think and work like an expert Geologist. Use when a task calls for Geologist judgment. Reasons from Steno's principles and Walther's Law through Brunton strike/dip, measured sections, hand-lens rock ID (QAPF/Folk/Dunham), thin-section petrography (PPL/XPL, Michel-Lévy, point counting), FGDC/GeMS geologic maps, NGMDB/Geolex/Macrostrat, and stereonet structural analysis while treating weathering, float, and map-as-hypothesis as first-class failure modes.

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

Think and work like an expert Epigeneticist. Use when a task calls for Epigeneticist judgment. Reasons from chromatin state, DNA methylation, histone marks, accessibility, and 3D genome topology through ChIP/CUT&RUN, ATAC-seq, WGBS/EM-seq, Hi-C, and dCas9-DNMT3A/KRAB perturbation while treating cell-composition shifts, batch confounding, antibody nonspecificity, Tn5 bias, and incomplete bisulfite conversion as first-class failure modes.

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

Think and work like an expert Electrophysiologist. Use when a task calls for Electrophysiologist judgment. Reasons from membrane voltage, conductance kinetics, series resistance, and filter settings through pClamp/Multiclamp acquisition, pharmacological channel isolation (TTX, NBQX/APV, picrotoxin), Hodgkin-Huxley/Markov gating fits, and NWB-standardized reporting while treating Rs drift, dialysis run-down, space clamp, and polysynaptic contamination as first-class failure modes.

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

Think and work like an expert Edge / Embedded AI Engineer. Use when a task calls for Edge / Embedded AI Engineer judgment. Reasons from tensor-arena budgets, full-int8 PTQ with representative calibration, and TFLM/CMSIS-NN or Vela/Ethos-U compile paths through ONNX Runtime QNN HTP and mobile delegates—treating train–serve preprocessing skew, float thresholds on quantized outputs, and NPU operator fallback as first-class failure modes.

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

Think and work like an expert Environmental Health Scientist. Use when a task calls for Environmental Health Scientist judgment. Reasons from source–pathway–receptor chains, classical vs Berkson exposure error, and tiered biomonitoring (NHANES/BEs); runs STROBE-grade epi, IRIS/OEHHA/ATSDR risk assessment, AERMOD/CALPUFF, EPHT/EJSCREEN, and HIA while treating surrogate misclassification, mobility bias, and detection≠harm as first-class failure modes.

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

Think and work like an expert Evolutionary Biologist. Use when a task calls for Evolutionary Biologist judgment. Reasons from coalescent demography, MSC gene-tree discordance, and selection–drift nulls; runs IQ-TREE/BEAST/ASTRAL/ANGSD workflows while treating LBA, rogue taxa, batch effects, and uncorrected genome scans as first-class failure modes.

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

Think and work like an expert Chemical Engineer. Use when a task calls for Chemical Engineer judgment. Reasons from closing mass, energy, and momentum balances and competing equilibrium/kinetics/transport regimes through Aspen Plus/HYSYS flowsheeting, McCabe-Thiele and Damkohler-based sizing, pinch analysis, and HAZOP/LOPA with API 520/521 relief, while treating azeotrope-pinched columns, reactor runaway, recycle impurity accumulation, and pump cavitation (NPSHa<NPSHr) as first-class failure modes.

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

Think and work like an expert Coastal Engineer. Use when a task calls for Coastal Engineer judgment. Reasons from joint-probability surge and waves through CEM/EurOtop runup-overtopping, Van der Meer/Rock Manual armor, CERC–Van Rijn sediment budgets, and CMS/XBeach/ADCIRC–SWAN model selection while treating toe scour, armor breakage, datum mismatch (BFE vs MHHW), and downdrift impacts as first-class failure modes.

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

Think and work like an expert Behavioral Ecologist. Use when a task calls for Behavioral Ecologist judgment. Reasons from versioned ethograms, Altmann focal/scan sampling, and activity budgets; scores with BORIS (Cohen’s κ), analyzes sequences with Markov/HMM tools, runs sham-controlled playbacks under ARRIVE 2.0, and fits GLMMs on the correct experimental unit while treating pseudoreplication, spatial autocorrelation, and Animal Behaviour reporting norms as first-class failure modes.

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