1,432 件 ・ 関連度順
概要と使いどころ
Use when a task needs the judgment of an Environmental Compliance Inspector — reviewing discharge monitoring reports or emissions data against permit limits, classifying a facility's hazardous waste generator status, calculating a penalty for a documented violation, deciding whether an exceedance warrants a Notice of Violation versus informal correction, or scoping a multimedia (air/water/waste) inspection.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Environmental Engineering Technologist/Technician — verifying field meter calibration before a sampling event, computing a flow-proportional composite sampling program, checking chain-of-custody entries against 40 CFR 136 holding times, running an air-monitoring isokinetic sampling check, or deciding whether a field QC exception invalidates a sample.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Dredge Operator — selecting cutterhead, hopper, or mechanical dredge type for a given sediment/depth/environmental profile, classifying dredged material for open-water vs. confined disposal from sediment-testing results, tuning hydraulic slurry density against pipeline critical velocity, verifying channel controlling depth against project depth and overdepth tolerance, or setting turbidity-monitoring response during active dredging.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Crushing/Grinding Machine Operator — recognizing that classifier cut point, not mill residence time alone, determines what reports to finished product in a closed-circuit grinding operation, monitoring circulating load as a distinct diagnostic variable, matching grinding media size to the target size reduction, or verifying product size via actual sieve/laser analysis rather than mill parameters.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Compliance Manager — sizing and defending a compliance program's headcount/budget, deciding build-vs-buy on monitoring or case-management technology, choosing a centralized-vs-embedded staffing model, translating a new regulatory obligation into a costed resourcing ask, or reporting program coverage to executives/the board.
日本語の概要は準備中です。原文の説明を表示しています。
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 Compliance Officer — deciding whether a suspected violation triggers a mandatory regulatory filing or disclosure, designing or risk-rating a compliance monitoring program, running a violation investigation to root cause, briefing a board/audit committee on compliance findings, or responding to a regulatory exam finding.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Biofuels Processing Technician — adjusting catalyst dosing for transesterification based on actual measured feedstock free fatty acid content rather than a standard fixed dose, verifying conversion completeness via actual glyceride content testing rather than visual inspection, actively monitoring fermentation temperature and pH throughout the process rather than checking only at the end, and managing byproduct quality as a distinct economic consideration alongside primary fuel yield.
日本語の概要は準備中です。原文の説明を表示しています。
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 airline pilot — checking whether an ETOPS diversion-time rating still holds against a current MEL downgrade, deciding whether to accept or query a dispatch release, applying sterile-cockpit discipline and Pilot Flying/Pilot Monitoring role separation on a two-pilot flight deck, resolving a captain-dispatcher operational-control disagreement, or checking Part 117 flight-duty-period legality against an irregular-operations delay.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Animal Scientist — formulating a least-cost livestock ration against nutrient requirements, evaluating breeding stock using EPDs or a selection index, diagnosing a feed-conversion-ratio decline, or designing a growth/reproduction performance-monitoring plan for a livestock operation.
日本語の概要は準備中です。原文の説明を表示しています。
Spring Boot 4 observability with Actuator, Micrometer, and OpenTelemetry. Use when configuring health indicators, health checks, custom metrics, distributed tracing, production endpoint exposure, Kubernetes probes, Cloud Run probes, logging, or monitoring. Covers Actuator endpoint security, Micrometer Timer/Counter/Gauge patterns, OpenTelemetry span customization, liveness/readiness probe setup, and metric tag best practices.
日本語の概要は準備中です。原文の説明を表示しています。
Automate semantic versioning releases with CHANGELOG validation, comparison link management, GitHub Actions workflow triggering, and monitoring. Scaffold release infrastructure for new projects. Use when user runs /release command, mentions "release version", "cut a release", "create release", "publish release", "tag release", "release setup", or "scaffold release pipeline".
日本語の概要は準備中です。原文の説明を表示しています。
Monitor brand visibility in AI search and traditional search. Use when user says "brand radar", "brand monitoring", "AI search visibility", "brand mentions", "share of voice", "who mentions my brand in AI", "brand in ChatGPT", "brand in Perplexity", "how visible is my brand", "brand awareness tracking", "AI brand presence", "is my brand cited in AI responses".
日本語の概要は準備中です。原文の説明を表示しています。
Use Terraform/IaC for Volcengine resources only when the user explicitly chooses Terraform/IaC, already has a Terraform workflow/state, or confirms they need plan/diff/drift/destroy safety for VKE, managed databases/cache/storage, load balancers, domains/certificates, logging/monitoring, or team-managed infrastructure.
日本語の概要は準備中です。原文の説明を表示しています。
Guidance for Tauri v2 clipboard plugin with safe copy, paste, and monitoring flows.
日本語の概要は準備中です。原文の説明を表示しています。
Defines service level objectives, creates error budget policies, designs incident response procedures, develops capacity models, and produces monitoring configurations and automation scripts for production systems. Use when defining SLIs/SLOs, managing error budgets, building reliable systems at scale, incident management, chaos engineering, toil reduction, or capacity planning.
日本語の概要は準備中です。原文の説明を表示しています。
Watches an open pull request's CI until green and fixes failing checks. TRIGGER when: the user wants to watch a pull request's CI, babysit a PR until it goes green, or fix failing CI checks on an open PR. DO NOT TRIGGER when: opening the PR in the first place → pr; rebasing the branch onto its base → rebase.
日本語の概要は準備中です。原文の説明を表示しています。
Opens a pull request, publishing the current branch as a PR. TRIGGER when: the user wants to open a pull request, publish the current branch as a PR, or take the current work through to an open PR. DO NOT TRIGGER when: only committing changes → commit; babysitting CI after the PR is already open → monitoring-pull-requests.
日本語の概要は準備中です。原文の説明を表示しています。
Rebases a feature branch onto its latest base, resolving conflicts while preserving the intent of local changes, optionally force-pushing and watching CI afterward. TRIGGER when: the user wants to rebase a feature branch, update a branch against its base, or replay local work on top of the latest upstream. DO NOT TRIGGER when: merging a release branch into dev → merging-branches; only watching CI on an already-open PR → monitoring-pull-requests.
日本語の概要は準備中です。原文の説明を表示しています。
Setting up application error tracking — SDK integration, grouping, and context — works with any error-monitoring platform.
日本語の概要は準備中です。原文の説明を表示しています。
Strengthen defensive security operations — detection engineering, hardening, monitoring, and continuous defense improvement.
日本語の概要は準備中です。原文の説明を表示しています。
Designing alert rules that fire when it matters — thresholds, burn rates, and routing — for any monitoring stack.
日本語の概要は準備中です。原文の説明を表示しています。
Ship AI features to production — model selection, evals, latency/cost optimization, guardrails, monitoring, and iteration loops. Use when turning an LLM prototype into a reliable product feature.
日本語の概要は準備中です。原文の説明を表示しています。