「trace」の検索結果

Use when a task needs the judgment of a CNC Tool Operator — diagnosing a dimension trending toward its tolerance limit across consecutive parts before it actually crosses, deciding whether to apply a tool wear offset or flag the tool for replacement, evaluating whether a failed part traces to work-holding repeatability versus a program or tool issue, or verifying a setup change with a first-article inspection before running production quantity.

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

Use when a task needs the judgment of a Butcher/Meat Cutter — computing true cost per sellable pound from a primal's actual cutting yield, allocating a primal's cost across cut categories by relative market value, pricing dry-aged product against its finished (not green) weight, or diagnosing whether a below-average yield traces to cutting spec rather than the animal itself.

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

Use when a task needs the judgment of a biomedical/bioengineering engineer — running a design control phase (inputs, outputs, verification, validation) for a medical device, scoring a Design FMEA and deciding whether a failure mode needs mitigation, planning a human factors/usability validation study, building a design traceability matrix, or writing a design verification or risk-mitigation report. Distinct from a regulatory-affairs-specialist (owns the submission/clearance process, not the engineering itself) and from a clinical-data-manager/biostatistician (trial data and analysis, not device design).

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

Use when a task needs the judgment of an Automotive Engineering Technician — setting up and instrumenting test equipment (strain-gauge bridges, thermocouples, load/torque sensors) to an engineer's written test plan, selecting DAQ sample rate and an SAE J211 CFC filter class for a vehicle test channel, verifying instrument calibration (torque wrench, thermocouple, load cell, shunt-cal check on a strain bridge) against a traceable standard before a test run, reducing dyno or road-load test data (SAE J1349 power correction, rainflow-counted durability damage fraction) into engineering units, and documenting test results against the engineer's target with stated margin. Distinct from an automotive engineer (owns the system-level design decisions — structure, powertrain sizing, suspension geometry, NVH) — this role installs the sensors, configures the DAQ, executes the instrumented test, and reduces the data under a design and test plan the engineer specified.

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

Use when a task needs the judgment of a Baker — scaling a formula using baker's percentages to hit an exact batch weight, diagnosing whether a fermentation problem traces to dough temperature or mixing development, judging proof readiness from a poke test rather than a fixed clock, or tracing a poor-oven-spring result back to over- or under-proofing instead of the oven.

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

Use when a task needs the judgment of an Agricultural Inspector — grading a lot of produce against a USDA grade standard's defect tolerances, evaluating agricultural water test results against FSMA microbial thresholds, checking a pesticide residue result against the commodity-specific EPA tolerance, deciding whether a finding warrants a stop-sale order versus a corrective-action letter, or verifying a facility's traceability records against a recall deadline.

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

Builds Flux manifests locally, diffs YAML files, patches FluxInstance upgrades, creates authentication secrets, traces GitOps delivery pipelines, and bootstraps clusters with the Flux Operator. Use this skill whenever the user mentions flux-operator, FluxInstance, FluxReport, ResourceSet, ResourceSetInputProvider, Flux CD operator management, or asks about GitOps CLI tooling for Kubernetes with Flux. Also trigger when users ask about building Flux manifests, diffing YAML, patching Flux instances, creating Flux secrets, tracing GitOps delivery pipelines, or bootstrapping clusters with Flux. Even if the user just says "flux operator" or "flux-operator cli" without details, this skill has the authoritative reference.

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

Evidence-first academic research workflow for topic ideation, scholarly search, paper reading, literature and systematic reviews, study and experiment design, statistics and data analysis, scientific figures, manuscript drafting and polishing, citation checks, peer review, rebuttals, submission packages, theses, and paper-to-presentation work. Use when an agent must plan, execute, audit, write, revise, or package research while keeping claims traceable to verified sources, data, analysis, or official requirements.

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

Compiles binary analysis findings into structured reports — correlates facts from triage, static, and dynamic phases, validates hypotheses against evidence, and produces traceable documentation. Use when ready to summarize findings, generate a report, document what a binary does, or prepare results for handoff or archival.

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

Deep cross-layer consistency audit for any codebase. Traces every feature from UI to database, finds broken wiring, missing handlers, model mismatches, and security gaps. Auto-fixes critical and warning issues. Use this after building features, before releases, or whenever something feels off. Works with any tech stack.

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

Start a session from what was left - trace saves, briefs, proposals, review reports, issues - and ask what to continue. Never resume or implement automatically.

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

Save where the session stands before ending it, so next can resume it in a clean context. Also reads or records project progress.

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

Set up an end-to-end test suite in any repo, following practices that make e2e a reliable per-PR gate: real flows over bypass, layered assertions, a reusable auth/session helper, video+trace evidence, and a compounding suite. Use when a repo has no e2e (or weak e2e) and you want system-level tests — "set up e2e", "add end-to-end tests", "scaffold a test gate".

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

Apply Yuzu-specific test-driven development using tracer-bullet red-green-refactor cycles and the repo's Meson, gateway, proto, and ABI validation rules. Use when the user says `/tdd`, asks for TDD, red-green-refactor, or wants a feature/fix built test-first in Yuzu.

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

Fix a bug using Scout → Diagnose → Fix → Review → Finalize. Use when the user pastes an error message, stack trace, or test failure, or says "fix this bug", "something's broken", "tests are failing", "I'm getting an error". Also accepts `--from-quality <report>` or `--from-test <report>` to fix exactly the findings/failures a report lists. Modes (pick one): --fast (trivial errors — lint, type, build — skip scout and review), --hard (mandatory review, no auto-approve).

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

Fix a bug using Scout → Diagnose → Fix → Review → Finalize. Use when the user pastes an error message, stack trace, or test failure, or says "fix this bug", "something's broken", "tests are failing", "I'm getting an error". Also accepts `--from-quality <report>` or `--from-test <report>` to fix exactly the findings/failures a report lists. Modes (pick one): --fast (trivial errors — lint, type, build — skip scout and review), --hard (mandatory review, no auto-approve).

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

Use this skill when designing the human-executable UAT test cases that prove a Salesforce feature works for a specific persona — the per-persona scripts with preconditions, data setup, permission setup, ordered steps, and pass/fail evidence that close out an RTM row. Trigger keywords: UAT test case salesforce, user acceptance test script salesforce, manual test salesforce feature, UAT script per persona, UAT precondition data setup, UAT permission set assignment for testing, negative path UAT case. NOT for high-level UAT planning, defect classification, regression strategy, or sign-off (use admin/uat-and-acceptance-criteria). NOT for the Given/When/Then technique used to write the AC the case is derived from (use admin/acceptance-criteria-given-when-then). NOT for Apex test method generation (use agents/test-class-generator). NOT for test data factory patterns (use templates/apex/tests/TestDataFactory.cls). NOT for performance or load testing.

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

Author the Salesforce Configuration Workbook — the structured, reviewable handoff document an admin uses to execute a feature across Objects/Fields, Page Layouts, Profiles/PSGs, Sharing, Validation, Automation, List Views, Reports, Integrations, and Data. Triggers: 'salesforce configuration workbook', 'admin handoff document', 'implementation workbook'. NOT for object design itself (use admin/custom-field-creation, admin/lookup-and-relationship-design, agents/object-designer/AGENT.md), NOT for permission set design (use admin/permission-set-architecture, agents/permission-set-architect/AGENT.md), NOT for Flow construction (use skills/flow/* and agents/flow-builder/AGENT.md), and NOT for the deployment manifest (use skills/devops/metadata-api-retrieve-deploy). More triggers: workbook row schema, recommended_agent, recommended_skills, row_id, source_req_id, RTM linkage block, not-in-scope-this-release, descope ledger, version-lock the workbook, check_workbook.py.

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

Systematically explore and test any software project (CLI, API, Backend, Library, etc.) to find bugs, usability issues, and edge cases. Produces a structured report with full reproduction evidence (exact commands, inputs, logs, and tracebacks) for every issue.

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

Use this skill when the user is working with an Aspire distributed application and needs to operate the AppHost or its resources through the Aspire CLI: start, restart, stop, or wait on the app; inspect resources, logs, traces, docs, or health; add integrations; manage secrets or config; publish, deploy, or rerun a named pipeline step; initialize Aspire in an existing app; recover missing `.modules` files in a TypeScript AppHost; discover the right frontend URL for Playwright from Aspire state; expose custom dashboard/resource commands; or understand unfamiliar Aspire AppHost APIs in C# or TypeScript. Use it even if they describe the task in terms of an AppHost, resources, dashboard, existing app bootstrap, missing generated modules, Playwright URL discovery, C# API understanding, or local distributed app workflow without explicitly naming Aspire. Do not use it for non-Aspire .NET apps, container-only repos with no AppHost, or ordinary build and test tasks.

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

MUST USE for any real runtime debugging across ANY language or binary — crashes, silent failures, wrong responses, stuck processes, memory leaks, async misbehavior, unexplained timing, reverse engineering. Runs a hypothesis-driven loop: form ≥3 hypotheses, investigate in parallel, after 2 failed rounds spawn Oracles from orthogonal angles, confirm root cause, lock with a failing test, fix minimally, QA by actually USING the system, scrub artifacts. The actual HOW lives in `references/` — READ THEM. Triggers: 'debug this', 'why is X not working', 'hanging', 'attach a debugger', 'reverse engineer', 'pwndbg', 'gdb', 'lldb', 'node inspect', 'tsx debug', 'pdb', 'dlv', 'delve', 'rust-gdb', 'set a breakpoint', 'context window exploded', 'why is the response empty', 'attach the debugger', 'debug it', 'why is this happening', 'trace this bug', 'reproduce and fix', 'silent failure', 'HTTP 200 but empty', 'why did it stop', 'inspect the binary', 'reverse engineering', 'playwright'.

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

Converts transparent or solid-background single-color PNG files and SVG files containing one embedded or local PNG into verified path-only SVG output. Removes pure-color backgrounds automatically. Uses Potrace threshold and parameter scans with alpha error metrics to preserve detailed logos, stamps, engravings, and line art. Use when the user asks to convert images to SVG, vectorize PNG, convert bitmap to true SVG, remove embedded raster data from SVG, 图片转矢量, PNG 转 SVG, 真矢量, or 位图描摹.

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

Diagnose a CrewRift policy failure from completed artifacts, source mechanics, and social behavior traces.

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

Trace every user-facing button/touchpoint through its full state change sequence to find bugs where functions individually work but cancel each other out, produce wrong final state, or leave the UI in an inconsistent state. Use when: systematic debugging found no bugs but users report broken buttons, or after any major refactor touching shared state stores.

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