「condition」の検索結果

Use when a task needs the judgment of an embalmer — assessing a case's decomposition stage and preservation difficulty, calculating an arterial-fluid dilution ratio for a specific case condition, choosing a restorative-art approach for trauma or discoloration, or working through a bloodborne-pathogen exposure-control decision.

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

Use when a task needs the judgment of an Environmental Health Specialist (Registered Sanitarian) — classifying a food-establishment temperature violation as critical vs. priority-foundation, determining pool closure and hyperchlorination protocol after a fecal/vomit incident, evaluating a septic percolation test against site-limiting conditions, deciding whether a complaint pattern meets the threshold for an outbreak investigation, or issuing an imminent-health-hazard closure.

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

Use when a task needs the judgment of a Registered Dietitian Nutritionist — calculating caloric/macronutrient needs for a clinical case, designing a medical-nutrition-therapy plan for a disease-specific condition (renal, diabetic, oncology), setting an enteral or parenteral feeding prescription, or screening/triaging malnutrition risk.

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

Use when a task needs the judgment of a Cutting/Slicing Machine Operator — calculating a portion weight overweight margin from measured weight variability to minimize giveaway while staying compliant, verifying a thickness setting against a new product lot's actual density rather than reusing a prior lot's setting, diagnosing declining cut quality as a blade-condition issue rather than compensating with thickness/speed, or adapting cut pattern to irregular input to improve yield.

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

Use when a task needs the judgment of a Construction Manager — planning or sequencing a construction project, evaluating a schedule/cost tradeoff, managing subcontractors and site safety, or responding to an unexpected site condition or delay.

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

Use when a task needs the judgment of a construction/maintenance painter — scoping an exterior or interior repaint, diagnosing why a paint job failed (blistering, alligatoring, peeling), pricing a job against real coat-count and prep requirements, deciding whether EPA lead-paint rules apply, or timing application against moisture and weather conditions.

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

Use when a task needs the judgment of a Conservation Scientist — writing or reviewing a rangeland/forest conservation plan, calculating stocking rate or carrying capacity against a proposed grazing or timber plan, scoping a prescribed-fire prescription, resolving a multi-use land-allocation conflict on public or private land, or assessing range/forest condition trend from monitoring data.

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

Use when a task needs the judgment of a Civil Engineering Technician — running and interpreting a concrete field acceptance test (slump, air content, cylinder breaks against ACI 318 criteria), verifying soil compaction against a Proctor density curve, reconciling a concrete or rebar quantity takeoff against a pay application, or documenting a field condition that deviates from the approved plans for the engineer of record.

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

Use when a task needs the judgment of a Business Teacher, Postsecondary — grading case analysis on the rigor of business reasoning rather than matching a single "correct" answer, updating stale textbook examples against current market conditions rather than teaching them as still-current, distinguishing taught analytical frameworks from personal business opinion presented as universal fact, and preserving the incomplete-information trade-offs of real business decisions rather than simplifying problems into false certainty.

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

Use when a task needs the judgment of a carpenter's helper — cutting and staging lumber to a carpenter's layout marks, assembling and standing framed wall panels, running a material take-off and waste calculation for a framing package, or recognizing when a jobsite condition (a missing guardrail component, a nail-gun trigger setting, a header that doesn't match the plan) is a stop rather than a workaround.

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

Use when a task needs the judgment of a Cargo Inspector — reconciling a vessel draft survey against a shore tally within IMO tolerance, calculating outturn quantity from tank ullage and temperature readings under API MPMS, verifying dangerous-goods segregation against the IMDG Code, checking a load's height and width against a route's bridge and tunnel clearances before departure, or documenting cargo condition and filing a letter of protest before custody transfers.

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

Use when a task needs the judgment of an atmospheric scientist/operational meteorologist — interpreting ensemble forecast guidance, deciding whether conditions cross a severe-weather warning threshold, calibrating a raw model probability against verification climatology, or writing a forecast discussion or warning product under time pressure.

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

Use when a task needs the judgment of a Biomass Plant Technician — adjusting combustion parameters in response to actual measured fuel moisture content rather than a fixed setpoint, diagnosing a fuel feed interruption as mechanical bridging rather than a combustion issue, adjusting soot-blowing frequency to actual observed slagging conditions rather than a fixed calendar schedule, or monitoring emissions more actively given fuel batch variability rather than a "set and monitor occasionally" approach appropriate for consistent fossil fuel.

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

Use when a task needs the judgment of an auto-glass installer/repairer — deciding whether a chip or crack qualifies for resin repair versus full replacement, calculating a safe drive-away time for the adhesive and conditions on a job, determining whether a windshield replacement triggers ADAS camera recalibration, or diagnosing a cut-out/pinch-weld defect before it becomes a leak or corrosion claim.

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

Use when a task needs the judgment of an airfield operations specialist — running a Part 139 self-inspection of the movement area, assigning a Runway Condition Code (RwyCC) after snow/ice contamination, deciding whether a discovered hazard needs an immediate NOTAM, triggering a Wildlife Hazard Assessment after a strike or sighting, or judging a FOD find as immediate-closure versus scheduled removal.

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

Audit an existing mathematical, logical, algorithmic, or technical proof from its stated conclusion backward as a bounded AND/OR graph of exact obligations. Use to reconstruct conclusion dependencies, determine whether a proof-supplied route establishes the conclusion, or expose hidden assumptions, unmet side conditions, cycles, overly strong steps, or silent route switches. For a source-mapped Lamport rendering use convert-lamport, and for forward hierarchy, construct, and scope conformance use forward-lamport before this skill. This does not decide full theorem-level entailment by searching for a different proof; do not turn the audit into a linear reversed proof, exhaustive proof search, or replacement proof.

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

Audit an existing Lamport-style hierarchical mathematical proof forward for validity and whether its hierarchy, scope, dependencies, side conditions, and proof constructs discharge the stated theorem. Use when the central question concerns a top-down proof with numbered levels, subproofs, ASSUME/PROVE, SUFFICES, PICK, CASE, DEFINE, Q.E.D., or prose equivalents. For an ordinary proof that first needs source-preserving hierarchy, use convert-lamport; for conclusion-first AND/OR obligation reconstruction, use reverse-lamport. Do not use to generate or replace a proof, or to audit Lean, Coq, Isabelle, or other proof-assistant source.

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

Implements advanced TypeScript type systems, creates custom type guards, utility types, and branded types, and configures tRPC for end-to-end type safety. Use when building TypeScript applications requiring advanced generics, conditional or mapped types, discriminated unions, monorepo setup, or full-stack type safety with tRPC.

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

Generate and edit images with diffusion models: prompting, seeds, CFG, img2img, inpainting, conditioning, and API integration. Use when adding AI image generation to apps or workflows.

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

Build workflow automations — triggers, actions, conditional logic, error handling, and maintainable automation design.

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

Analyze mining equipment maintenance systems including heavy fleet condition monitoring (oil analysis, vibration per ISO 17359/10816, thermal imaging), predictive analytics with Weibull reliability modeling and remaining useful life estimation.

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

Analyze defense maintenance and readiness systems — MRO optimization, mission capable rate tracking, reliability-centered maintenance (RCM), condition-based maintenance (CBM+), depot-level analytics, configuration management, and workforce planning. Audit weapon system sustainment software per MIL-STD-3034, AR 750-1, and DoD CBM+ frameworks.

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

Build psychological safety in your team using Simon Sinek's Leaders Eat Last Circle of Safety model and Amy Edmondson's research. Use when a leader says "my team doesn't speak up", "people are afraid to fail", "nobody challenges bad ideas", "people only tell me what I want to hear", "I want my team to take more risks", "there's a blame culture", "people hide mistakes", or "I want to create a safe environment". Also trigger when someone describes a team where postmortems turn into blame sessions, where people stay quiet in meetings and then vent privately, where mistakes are hidden until they become crises, or where the same person speaks 80% of the time in every meeting. Psychological safety is not about comfort - it is the condition that makes high performance possible.

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

Write measurable acceptance criteria for requirements or user stories. Use when the user says "write acceptance criteria", "definition of done", "how do we test this", "fit criteria", "given when then", "Gherkin scenarios", "what does done look like", "testable conditions", "how will we know this works" - even if they don't explicitly say "acceptance criteria".

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