「spec」の検索結果

Use this skill for transporting logs. Covers § 393.116 specific rules, bunks, stakes, and tiedowns required.

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

Use this skill when the user asks about US-Canada cross-border CMV operations — CVOR (Commercial Vehicle Operator's Registration), NSC (National Safety Code), Ontario / Quebec / BC specific rules, US carrier obtaining Canadian operating authority, FAST card for drivers, customs (CBSA), Health Canada hazmat, and how Transport Canada equivalents differ from US FMCSA. Reference USMCA + Transport Canada NSC 14.

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

Use this skill for transporting pipes (water, gas, oil, structural). Covers § 393.122 specific rules and roll-prevention.

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

Use this skill to explain to customers/sales prospects why FMCSA CSA scores are not available in real-time. Covers the SAFER refresh cycle and what 'real-time' actually means for CSA data.

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

Use this skill when the user asks about cargo securement requirements under 49 CFR 393 Subpart I — Working Load Limit (WLL), tiedown counts, tiedown types, commodity-specific securement rules (lumber, metal coils, paper rolls, concrete pipe, intermodal containers, vehicles, large boulders, dressed lumber, building materials), CVSA out-of-service criteria, and how to calculate aggregate WLL. Cite 49 CFR 393.100-136.

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

Use this skill when the user asks how to market a trucking company — sales channels, prospecting, website + brand, industry directories (D&B Hoovers, ZoomInfo), referral programs, content marketing, and ROI of different acquisition channels. Reference industry sales practices.

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

Use this skill when the user asks about FMCSA Compliance Safety Accountability (CSA) program scoring — the seven BASIC categories, BASIC Severity Indicator (BSI), peer percentiles, intervention thresholds, how violations age out, SMS Methodology, ISS (Inspection Selection System), what "alert" status means, Safety Measurement System mechanics, or DataQ disputes. Cite SMS Methodology v3.20.

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

Use this skill when the user asks about FCRA adverse action procedures — what to do when a background check (MVR, criminal, drug test) returns information that may lead to denying employment or terminating a CDL driver. Covers the 5-business-day pre-adverse-action notice, FCRA Summary of Rights, final adverse action notice, state-specific add-ons (CA, NY, etc.), and how to handle disputes. Cite 15 USC § 1681 (FCRA) and 49 CFR 391.

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

Use this skill when the user asks about the agricultural exemption from Hours of Service (HOS) rules under 49 CFR 395.1(k) — what qualifies as agricultural commodity, the 150-air-mile radius rule, state-declared planting/harvest seasons, livestock hauling specifics, and how to document operations under the exemption. Cite 49 CFR 395.1(k) and 49 USC 5117.

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

Adversarial reviewer for The Federated Harbor whitepaper — the third paper in the Curiositech sequence after Anchor and Bonded Commons. Probes federation-specific threats: trust transitivity, cross-harbor token forgery, federated revocation under partition, cross-harbor Sybil, cross-domain settlement, equivocation, bond-pool draining, cold-start joining, federation-operator Sybil. Use during a versioned red-vs-white round; pairs with federated-harbor-whitehat. NOT for incident response, NOT for the Anchor or Bonded papers (use redteam-review).

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

Defensive counterpart to federated-harbor-redteam: closes the smells that red team opens against The Federated Harbor whitepaper. Federation-specific defenses for cross-harbor primitives — mechanization commitments, scope hedges, cross-paper dependency formalization, pre-emptive analogies (CT, Macaroons, atomic swaps), and defense-in-depth framing (refuses vs prices). Use during a versioned red-vs-white round; pairs with federated-harbor-redteam. NOT for ad-hoc code review, NOT for the Anchor or Bonded papers (use whitehat-defense).

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

Design error handling strategies for TypeScript and Python applications — exception hierarchies, Result/Either types, retry patterns, error boundaries, and structured error logging. Use when designing error handling architecture, choosing between exceptions and Result types, implementing retry logic, or building error recovery flows. Activate on "error handling", "exception hierarchy", "Result type", "retry pattern", "circuit breaker", "error boundary", "Pokemon exception". NOT for debugging specific runtime errors, logging infrastructure setup, or monitoring/alerting configuration.

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

Manage feature manifests for code traceability. Use when creating new features, updating existing features, checking feature health, or exploring the feature-to-code relationship. Activates for manifest validation, feature creation, changelog updates, and traceability queries.

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

Expert landscape designer transforming yards through photo mapping, 3D visualization, seasonal planning, and deep plant knowledge. Specializes in fast-growing privacy screens (knows arborvitae pitfalls), architecture-appropriate design, outdoor living spaces, and realistic maintenance expectations. Activate on "landscape design", "yard design", "garden planning", "plant selection", "privacy screen", "outdoor living", "backyard makeover", "arborvitae", "hedge", "fast growing tree", "landscaping ideas". NOT for interior design (use interior-design-expert), hardscape construction (consult contractors), or lawn care chemicals (consult local experts).

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

Guides the practical path from 'we have no design system' or 'we have a mess' to a real, functional design system. Component inventory, design token extraction, headless UI adoption (Radix, React Aria, Headless UI), migration order of operations, and the assessment-to-rollout pipeline. Activate on 'design system from scratch', 'bootstrap design system', 'no design system', 'design system migration', 'headless UI adoption', 'component audit', 'design token extraction', 'design system strategy'. NOT for building specific components once a system exists (use design-system-creator), not for generating token files/configs (use design-system-generator).

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

Large-scale data migrations with validation, rollback, and zero-downtime strategies. Activate on: data migration, database migration, zero-downtime migration, dual-write, backfill, cutover, data validation, schema migration. NOT for: schema evolution in streams (use schema-evolution-manager), API versioning (use api-versioning-backward-compatibility).

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

Schema design, normalization decisions, indexing strategies, and migration safety for relational databases. Use when designing tables, choosing between normalize vs denormalize, selecting index types, planning zero-downtime migrations, or setting up connection pooling. Activate on "schema design", "normalization", "denormalization", "foreign key", "index strategy", "migration", "connection pooling", "composite key", "surrogate key", "soft delete", "polymorphic association". NOT for PostgreSQL-specific query tuning or EXPLAIN analysis (use postgresql-optimization), NoSQL or document database design, or cloud database provisioning.

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

Plan database migrations before executing them: risk assessment, dependency mapping, multi-service sequencing, rollback budgets, and stakeholder communication plans. Use when deciding HOW to migrate, not when writing the actual DDL. NOT for: writing migration SQL (use database-migration-manager), data ETL pipelines (use data-migration-specialist), query optimization, or ORM configuration.

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

Implementing distributed tracing with W3C Trace Context — the byte-precise `traceparent` and `tracestate` header formats, OpenTelemetry's W3CTraceContextPropagator as the modern default (replacing X-B3-* and X-Datadog-*), head vs tail sampling, and HTTP→SQL trace propagation via sqlcommenter. Grounded in the W3C REC and OpenTelemetry specs. NOT for OTel metrics/logs pipelines, vendor backend setup (Datadog/Honeycomb/Jaeger/Tempo), or browser RUM tracing.

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

Use when optimizing Docker builds with BuildKit, designing multi-stage Dockerfiles, leveraging cache mounts, building multi-arch images, choosing distroless vs alpine, or signing images with cosign. Triggers: docker build slow, layer cache not hitting, npm install / pip install reruns, multi-stage final image bloat, glibc vs musl issues, RUN --mount=type=cache, BUILDKIT_INLINE_CACHE, registry cache exporters, qemu emulation for arm64, COPY ordering for cache. NOT for Docker daemon admin, Kubernetes-specific image policies, container security scanning workflows, or Buildpacks (different paradigm).

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

Audit designs, color palettes, and UI components for WCAG 2.1 accessibility compliance, providing specific fixes for contrast, touch targets, focus indicators, and screen reader support. NOT for color harmony aesthetics or design system creation.

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

Write production-grade Dockerfiles, docker-compose configurations, multi-stage builds, and container optimization. Activate on "Dockerfile", "docker", "docker-compose", "container", "multi-stage build", "docker image", "container optimization", "docker security". NOT for Kubernetes orchestration, cloud-specific container services (ECS, Cloud Run), or CI/CD pipelines (use github-actions-pipeline-builder).

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

Organizing digital life for legacy, emergency access, and death preparedness. Specializes in password management, account documentation, digital asset preservation, and ensuring loved ones can access what they need.

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

Cross-platform desktop development for macOS and Windows -- platform abstractions, UI convention differences, and multi-platform CI/CD. Activate on: cross-platform app, macOS and Windows, platform differences, DMG installer, MSI installer, NSIS installer, Cmd vs Ctrl, platform abstractions, menu bar differences, native conventions. NOT for: mobile apps, web-only apps, Tauri-specific internals (use rust-tauri-development).

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