7,860 件 ・ 関連度順
概要と使いどころ
Use when a task needs the judgment of a Civil Engineer — sizing stormwater detention/drainage systems, checking foundation bearing capacity against a geotechnical report, verifying IBC/ASCE 7 code compliance for site civil work, reviewing construction RFIs against stamped drawings, or evaluating value-engineering changes for safety-margin impact.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Chief Technology Officer — deciding build vs buy for a core system, choosing whether an architecture bet is worth a full rewrite, sizing an SLA/uptime commitment against engineering cost, structuring engineering teams around a product roadmap, or writing the technical risk section of a board update.
日本語の概要は準備中です。原文の説明を表示しています。
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 Chemical Plant and System Operator — reconciling a batch's mass balance to catch a leak or unaccounted reaction that individually normal readings would miss, responding to an early exotherm temperature trend before it accelerates, prioritizing simultaneous alarms by consequence severity rather than order of occurrence, or flagging a combination of near-limit variables that no single-variable check would catch.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Chief Data Officer — resolving conflicting metric definitions across dashboards, deciding whether a dataset should be retained or purged, assigning data ownership for a system feeding regulatory or board reporting, sizing a privacy/breach risk against a proposed data collection, or auditing data readiness before an AI/ML initiative kicks off.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Automotive Engineer — computing weight transfer and tire friction-circle limits for a braking-while-cornering maneuver to set brake-force distribution, sizing a powertrain and gear ratio against a 0-60 mph acceleration target while checking traction versus power limits, sizing a crumple zone's crush distance against FMVSS 208 occupant-deceleration limits, or checking a powertrain-mount or driveline natural frequency against engine firing-order excitation for NVH isolation. Distinct from an automotive-service-technician (diagnoses and repairs a vehicle already designed) — this role owns the system-level design decisions (structure, powertrain sizing, suspension geometry, restraint/crash structure, NVH) that produce the vehicle the technician later services.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Aviation Inspector — determining whether an air carrier's fleet is in compliance with an Airworthiness Directive across a maintenance-records sample, deciding where the FAA's compliance-and-enforcement ladder places a finding (compliance action vs. Letter of Correction vs. civil penalty vs. certificate action), auditing a Safety Management System for a functioning safety-assurance loop rather than paperwork completeness, scoping a records-sampling strategy across a fleet under surveillance, or deciding whether to ground an aircraft pending an AD compliance finding.
日本語の概要は準備中です。原文の説明を表示しています。
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 an astronomer — calculating exposure time or signal-to-noise for a target, writing the feasibility math for a telescope-time proposal, reducing photometric or spectroscopic data, distinguishing a systematic error floor from statistical noise, or reviewing an observational result for calibration or upper-limit red flags.
日本語の概要は準備中です。原文の説明を表示しています。
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 an aircraft service attendant — servicing an aircraft's potable water or lavatory/waste system without cross-connecting the two, sequencing turnaround tasks inside a fixed gate-time window, staging ground support equipment around an active aircraft, or timing servicing against a deicing/anti-icing holdover-time window before pushback.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Certified Anesthesiologist Assistant (CAA) working inside an Anesthesia Care Team — building and executing an intraoperative anesthetic plan under a directing anesthesiologist, reading a vital-sign trend for anesthesia-specific emergencies (malignant hyperthermia, local anesthetic systemic toxicity, awareness), deciding when a deviation is an immediate-escalation trigger versus an independently correctable event, or navigating the jurisdiction/concurrency limits of CAA practice.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a board-certified anesthesiologist — building a preoperative anesthesia plan and risk stratification, choosing general vs. regional technique and airway strategy, managing an intraoperative crisis (difficult airway, malignant hyperthermia, local anesthetic systemic toxicity), or writing a PACU handoff and postoperative pain-management order set.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Aircraft Structure, Surfaces, Rigging, and Systems Assembler — deciding whether an out-of-tolerance hole or fastener needs a nonconformance report versus a field fix, verifying torque and calibration status before a fastener installation, diagnosing a FOD (foreign object debris) risk before closing a structure, or reading a drawing callout against a conflicting work instruction.
日本語の概要は準備中です。原文の説明を表示しています。
Expert guidance for Domain-Driven Design architecture and implementation. Use when designing complex business systems, defining bounded contexts, structuring domain models, choosing between modular monolith vs microservices, implementing aggregates/entities/value objects, or when users mention "DDD", "domain-driven design", "bounded context", "aggregate", "domain model", "ubiquitous language", "event storming", "context mapping", "domain events", "anemic domain model", strategic design, tactical patterns, or domain modeling. Helps make architectural decisions, identify subdomains, design aggregates, and avoid common DDD pitfalls.
日本語の概要は準備中です。原文の説明を表示しています。
Install Tilt and scaffold or audit Tiltfile + tilt/ configurations with ecosystem-aware templates. Auto-detects Java/Gradle (Spring Boot), Next.js, Python/uv, and external infrastructure; recommends single-file or modular tilt/*.star + service-config.yaml + environments.yaml patterns based on project complexity. Bakes in production-context safety guards, PVC persistence toggles, JDWP debug ports, and optional Prometheus/Grafana/Traefik scaffolds. Use when user runs /devtools:tilt-setup, mentions "tilt setup", "setup tilt", "scaffold tiltfile", "audit tiltfile", "tilt configure", "tilt project setup", "Tiltfile", "local kubernetes dev", or "kubernetes development environment".
日本語の概要は準備中です。原文の説明を表示しています。
Install Taskfile (task) and scaffold or audit Taskfile.yml configurations with ecosystem-aware templates. Auto-detects Node.js/pnpm, JVM/Gradle, Python/uv, Docker, and recommends single-file or multi-file (includes) patterns based on project complexity. Use when user runs /devtools:taskfile-setup, mentions "taskfile setup", "setup task runner", "audit taskfile", "scaffold taskfile", "add taskfile", "taskfile.yml", or "developer tasks".
日本語の概要は準備中です。原文の説明を表示しています。
UI/UX design agent for crafting user experiences, visual designs, and game interfaces. Auto-detects the designer role (UX Designer, UI Designer, Game UI Designer) and spawns a role-scoped sub-agent with only the relevant reference files. Triggers on phrases like "user flow", "wireframe", "design system", "design tokens", "accessibility", "WCAG", "UI pattern", "HUD", "game menu", "inventory UI", "minimap". Full per-role triggers in references/roles/.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive index for Tauri framework development, including Rust backend, frontend integration, and full plugin ecosystem. Acts as a router to specialized sub-skills with local examples and templates.
日本語の概要は準備中です。原文の説明を表示しています。
Guidance for Tauri v2 os-info plugin with safe system diagnostics and reporting.
日本語の概要は準備中です。原文の説明を表示しています。
Vira's design system — TailwindCSS conventions, color palette, typography, spacing, components, and accessibility rules. Use when working on UI components, styling, or layout in this project (Lucid HTML in Haskell sources under packages/vira).
日本語の概要は準備中です。原文の説明を表示しています。
Iterative measurement-driven improvement loop. Measure, profile, mutate, re-measure, commit. Works for performance, bundle size, complexity, test coverage — anything quantifiable. Use when the user wants to systematically improve a metric through repeated cycles of profiling and targeted changes.
日本語の概要は準備中です。原文の説明を表示しています。
Implements concurrent Go patterns using goroutines and channels, designs and builds microservices with gRPC or REST, optimizes Go application performance with pprof, and enforces idiomatic Go with generics, interfaces, and robust error handling. Use when building Go applications requiring concurrent programming, microservices architecture, or high-performance systems. Invoke for goroutines, channels, Go generics, gRPC integration, CLI tools, benchmarks, or table-driven testing.
日本語の概要は準備中です。原文の説明を表示しています。
Master Rust async programming with Tokio, async traits, error handling, and concurrent patterns. Use when building async Rust applications, implementing concurrent systems, or debugging async code.
日本語の概要は準備中です。原文の説明を表示しています。