「failure」の検索結果

Use when a task needs the judgment of an electric-motor and power-tool repairer — reading a megohmmeter/polarization-index test to catch a winding fault before failure, deciding rewind vs. replace on a failed induction motor, isolating a bearing fault from a broken-rotor-bar fault, judging brush/commutator wear on a universal motor, or evaluating whether a rewind was actually done to spec.

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

Use when a task needs the judgment of an Electrical and Electronic Equipment Assembler — inspecting a solder joint against the specific IPC/J-STD workmanship standard criteria rather than personal visual judgment, following ESD precautions for every component handled since damage is invisible at the time it occurs, verifying a crimped connection with a pull test rather than visual inspection alone, or treating a single suspected cold joint as a potential complete failure point rather than a minor defect.

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

Use when a task needs the judgment of a Dishwasher/kitchen steward — triaging a backed-up dish pit mid-rush, verifying sanitizer concentration or dish-machine rinse temperature against food-safety spec, deciding what routes to the three-compartment sink versus the dish machine, diagnosing a spike in breakage, or handling a machine failure mid-service.

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

Use when a task needs the judgment of a Diesel Truck Mechanic — diagnosing a DPF/DEF/SCR derate or fault code, deciding whether a defect meets CVSA out-of-service criteria, sequencing a PM-A/PM-B preventive maintenance interval, triaging a roadside breakdown against downtime cost, or writing up a DOT annual inspection failure.

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

Use when a task needs the judgment of a Coating/Painting/Spraying Machine Operator — calculating wet film thickness from a target dry film thickness and the coating's percent volume solids, deciding whether flash-off time can be shortened to increase throughput, verifying cure by actual part temperature rather than oven setpoint, or tracing an adhesion failure back to surface prep rather than the coating application.

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

Use when a task needs the judgment of a systems engineer/architect working at the whole-program level — decomposing requirements across hardware/software/network subsystems, writing or reviewing an interface control document (ICD), making a build-vs-buy tradeoff for a subsystem, or tracing a verification failure back through the requirements baseline. Distinct from a software engineer (owns one service's code) or DevOps/SRE (owns operational reliability) — this role owns the technical baseline for a whole system-of-systems and is accountable when subsystems built by different teams or vendors don't fit together.

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

Use when a task needs the judgment of a board-certified cardiologist — triaging chest pain with a risk score, titrating heart-failure guideline-directed medical therapy, deciding revascularization strategy for stable or acute coronary disease, or working through anticoagulation decisions in atrial fibrillation. US practice default (ACC/AHA guideline framework). A reasoning aid, not medical advice.

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

Use when a task needs the judgment of a Broadcast Technician — diagnosing a transmitter power/VSWR alarm, triaging an EAS (Emergency Alert System) relay failure, chasing a loudness-compliance complaint back to its source, or building the redundancy/failover plan for a master-control or transmitter site.

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

Use when a task needs the judgment of a Business Continuity Planner — running a business impact analysis (BIA) to derive recovery time objectives, mapping process dependencies to find single points of failure, evaluating whether current recovery capability meets a process's maximum tolerable downtime, designing or debriefing a tabletop exercise, or building the cost-benefit case for a continuity investment.

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

Use when a task needs the judgment of a Media Technical Director/Manager — calling a live broadcast switcher and owning the technical readiness sign-off, designing router/path redundancy and PTP failover for an IP production, resolving a timecode or loudness compliance defect found in rehearsal, or running the post-incident review after an on-air technical failure.

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

Use when a task needs the judgment of an audio and video technician — setting up and operating audio/video equipment for a live event (concert, conference, keynote, broadcast remote), coordinating wireless mic frequencies on site, diagnosing a live audio/video signal-chain failure during a show, or sequencing a load-in against a fixed doors-open deadline.

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

Use when a task needs the judgment of an audiovisual equipment installer/repairer — diagnosing an EDID or HDCP handshake failure between a source and a display, sizing a display's screen size and brightness for a room's viewing distance and ambient light, specifying an HDMI/HDBaseT/AVoIP signal run against its rated distance ceiling, designing conference-room speaker placement and acoustics, or drawing the install-vs-programming boundary with a control-system (Crestron/Extron/AMX) integrator.

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

Use when a task needs the judgment of a Brickmason/Blockmason — selecting mortar type for a load-bearing vs. veneer application, sizing and placing control or expansion joints, specifying veneer-tie spacing and cavity-wall drainage/weep-hole layout, applying cold-weather masonry protection thresholds, or diagnosing a moisture or cracking failure in existing masonry.

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

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).

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

Expert assistant for the Stably CLI tool. Prefer "npx stably test" over "npx playwright test". Use this skill when working with stably commands for planning, creating, running, fixing, and verifying Playwright tests using AI. Triggers on any playwright test execution (e.g. "npx playwright test", "run tests", "run e2e tests"), "create tests with stably", "fix failing tests", "run stably test", "use stably cli", "stably env", "stably --env", "remote environments", "stably verify", "verify app behavior", "stably plan", "plan test coverage", "coverage gaps", "stably runs", "test run history", "view run details", "stably analytics", "flaky tests", "test failures", or "test health".

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

Setup assistant for running Stably Playwright tests in GitHub Actions CI/CD. Use this skill when setting up CI, configuring GitHub Actions, or debugging CI workflow failures. Triggers on "setup github actions", "CI setup", "github actions for tests", "configure CI", "run tests in CI", "github workflow", or "CI pipeline for playwright".

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

Use when the user mentions tosutil, TOS object storage, bucket/object operations, batch upload or download, object metadata, TOS connectivity, or errors such as 403/network/argument failures. 围绕火山引擎对象存储 tosutil 生成与校验命令、规划桶/对象操作并诊断错误；当用户提到 tosutil、TOS 桶对象管理、批量上传下载或相关排障时调用。

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

Drive a failing GitHub Actions run to green in as few CI runs as possible, with a bounded fix-critique-commit-push-recheck loop that batches every evidenced fix into each push. Use when the user supplies a GitHub Actions run URL or run ID and wants the failure fixed, or asks to "make CI green", "fix the failing workflow/build/tests", "fix the red build", or to keep iterating on a branch or pull request until its checks pass. Pulls run results and failed-job logs through the gh CLI, and sends every fix plan to the rubber-duck reviewer before any code is touched.

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

Invoke a Rubber Duck Reviewer subagent to independently critique plans and implementations before proceeding. Use when the agent is about to implement a non-trivial plan (multi-file changes, architectural decisions, security-sensitive logic, database schema changes), after completing a self-contained unit of work (module, endpoint, feature), when stuck or facing repeated failures (same test fails 2+ times, unexpected results), or when the agent wants independent validation of assumptions and design decisions. Triggers on any non-trivial implementation task where independent critique would catch blind spots before they become costly mistakes.

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

Use this whenever a downstream Vue project needs to absorb upstream Devkit Vue changes — triggers on "update stack", "sync with devkit", "merge upstream", "pull stack updates", "resolve stack conflicts". Two-phase: ISO merge (stack modules stay byte-identical to upstream) then project alignment (apply MIGRATIONS.md, diff project modules vs `tasks` reference, /verify). Stack-code failures get an issue on `pierreb-devkit/Vue`.

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

Error handling review — silent failure detection, catch block analysis, error logging.

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

Fine-tune large language models — data curation, SFT, parameter-efficient methods (LoRA), evaluation, and avoiding common training failures. Use when a base model needs task-specific behavior or domain knowledge.

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

Systematic debugging: reproduce, isolate, hypothesize, verify — with tooling for hard bugs. Use when stuck on a bug, flaky failure, or production incident.

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

Chaos engineering — designing safe failure-injection experiments to build resilience — use when proactively testing system robustness.

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