3.7천건 · 관련도순
Use this skill when a driver is being screened for sleep apnea. Covers FMCSA Medical Review Board (MRB) recommendations, BMI thresholds, sleep study referrals, and continued certification.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when the user asks how to design or improve a fleet safety scorecard — what KPIs to track, how to weight them, telematics signals vs document compliance vs roadside outcomes, monthly cadence, driver-facing vs admin-facing dashboards, gamification considerations, peer-comparison metrics, and how a scorecard ties to insurance premiums + retention. Reference SMS Methodology v3.20 for industry-standard weights.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a carrier needs to build an internal dispatcher training program, onboard new dispatchers, or certify dispatcher competency. Covers job description, required skills, training modules, certification frameworks (CDS, CTP), shadowing, evaluation, and career path.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when discussing the mobile apps drivers use day-to-day — load boards (DAT, Truckstop), route planners (Trucker Path, CoPilot Truck), expense and per diem apps (Per Diem Plus), parking apps (Park My Truck), maintenance / DVIR apps, and how these stack with the carrier's ELD app.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit whether a "current product focus receipt" (Decision/Now/Why-now/Evidence/Not-now/Cut-suspend/First-visible-proof/ Acceptance-gate/Kill-revisit-trigger/Owner/Review-date) and the work order it gates state a real, testable decision and a real agent launch — not planning-placeholder prose that sounds like an assignment but can't be proven. Use when deciding whether to launch an agent chain against a milestone or a stated "focus," when a work order lacks explicit input/output/owner/proof-gate, or when an acceptance gate would only prove a cached UI state instead of daemon truth. NOT for distinguishing roadmap items from energy-driven sidequests (legible-roadmap-with-sidequests), reviewing a PRD/prototype for product-completeness gaps like cold start or pricing (product-reality-reviewer), or accepting already-finished work against a personal acceptance bar (port-daddy-user-surrogate-pm-review).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
State-of-the-art data visualization for React/Next.js/TypeScript with Tailwind CSS. Creates compelling, tested, and accessible visualizations following Tufte principles and NYT Graphics standards. Activate on "data viz", "chart", "graph", "visualization", "dashboard", "plot", "Recharts", "Nivo", "D3". NOT for static images, print graphics, or basic HTML tables.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert data engineer for ETL/ELT pipelines, streaming, data warehousing. Activate on: data pipeline, ETL, ELT, data warehouse, Spark, Kafka, Airflow, dbt, data modeling, star schema, streaming data, batch processing, data quality. NOT for: API design (use api-architect), ML training (use ML skills), dashboards (use design skills).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement AI chatbot analytics and conversation monitoring. Use when adding conversation metrics, tracking AI usage, measuring user engagement with chat, or building conversation dashboards. Activates for AI analytics, token tracking, conversation categorization, and chat performance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Choose, compare, and decompose work into the right coordination topology: dag, workflow, manager-driven team, swarm, blackboard, team-builder, or recurring loop. Use when the coordination shape is unclear, when you need topology-native breakdown instructions instead of a generic DAG, or when planning topology and runtime topology may differ. NOT for actual execution, node-level skill matching, or framework/tool installation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design polished terminal UX for CLIs and TUIs. Use for setup flows, dashboards, tables, and actionable errors. NOT for web UIs, desktop windows, API schemas, or shell automation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design and build mathematically rigorous, high-density, interactive data graphics and streaming telemetry visualizations following Mike Bostock's D3.js and Observable methodologies. Use when crafting custom SVG/Canvas charts, reactive streaming time-series, multi-dimensional brush-and-link coordinates, small multiples, or topological swarm graphs. NOT for generic dashboard template clones, basic spreadsheet charts, or off-the-shelf low-effort wrapper libraries.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Author a pull request an AI coding agent can actually get merged: a scoped, coherent diff; a Summary and Test Plan backed by real evidence; correct triage of required-and-blocking CI gates versus external/advisory checks (e.g. a Cloudflare Pages preview build); draft-while-WIP discipline; named fixup commits for real review findings; and a clean landing through a merge queue without force-pushing or bypassing branch protection. Use when opening, updating, triaging red CI on, or landing an agent-authored GitHub PR. NOT for this repo's internal release ceremony, actor embodiments, or contributor mirror-sync mechanics (use port-daddy-internal-dev), tracking backlog/issue lifecycle across a board (use agent-issue-tracker-workflow), or deciding what to build next / sequencing a roadmap (use legible-roadmap-with-sidequests).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Connect a customer agent to Coval and complete a small first evaluation with inspected voice or chat results. Use when no usable evaluation exists yet; reuse existing recordings and resources when available.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Lean, sharp UI posture — the everyday default for building or redesigning a UI. Use when asked to build or make a page, panel, list, form, or dashboard good, cleaner, or nicer, or for a fast confident refresh where the agent uses its judgment instead of asking for a spec.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Dense UI posture — maximum information density with clear hierarchy. Use when building or reworking admin dashboards, data tables and grids, ops or monitoring views, settings-heavy panels, debug inspectors, state or log viewers, and multi-pane tool UIs someone drives all day.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use whenever a form needs to accept ONE image and produce permanent public URLs for one or more platform-specific sizes (OG image, social posts, avatars, logos, favicons, app icons). Replaces every legacy image-URL input, single-size uploader, and base64-data-URL flow. Triggers when you see a manual `<input type="url">` for an image, a single-size uploader, or anywhere a `dataUrl` could leak into a clipboard or a saved record.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Recipe for an agent building a small custom web app (an Applet) for one person or business on THEIR OWN store tables, live at aimatrx.com/applets/<slug>. Use when asked to build an app, portal, calendar, tracker, dashboard screen or client view on someone's tables/data in AI Matrx. NOT for platform features (use build-sub-feature) or tables the platform keeps for itself (defineTypedTable).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apple Human Interface Guidelines for iPad. Use when building iPad-optimized interfaces, implementing multitasking, pointer support, keyboard shortcuts, or responsive layouts. Triggers on tasks involving iPad, Split View, Stage Manager, sidebar navigation, or trackpad support.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apple Human Interface Guidelines for Mac. Use when building macOS apps with SwiftUI or AppKit, implementing menu bars, toolbars, window management, or keyboard shortcuts. Triggers on tasks involving Mac UI, desktop apps, or Mac Catalyst.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide the user through starting a new web application project — elicit requirements (MoSCoW scoping), create architecture and requirements documents, break work into tasks, and register them as a GitHub Project kanban board. Use when the user says "新しいWebアプリを作りたい", "Webアプリの立ち上げを手伝って", "start a new web app project", "プロジェクトの要件を整理したい", or "GitHub Projectにタスクを登録したい".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
未知のコードベースを分析し、アーキテクチャマップ、主要エントリポイント、規約、スターター CLAUDE.md を含む構造化されたオンボーディングガイドを生成する。新しいプロジェクトに参加する際や、リポジトリで初めて Claude Code をセットアップする際に使用。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a running Spark or DSH web service needs real-browser verification — page load, client-plugin boot errors, console errors, failed requests, or onboarding/dialog rendering — with the repository's own Playwright chromium.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Directs pixel art that must read at several zoom scales at once — per-scale palette and silhouette rules, terrain-versus-unit contrast, a one-scene look test, and briefs for an artist or image generator. Trigger when a game renders one world through zoom bands or levels of detail, a pixelated 3D or 2.5D band with billboards included; when a sprite, unit or icon vanishes against terrain zoomed out; for a cross-band look test or pixel-art style guide; or say pixelsmith (test, brief, audit, 3d). Works from a described scene. Drawing is an art tool's job; rendering and LOD code the game's engineering; a brand palette brandscribe's; game audio soundsmith's.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Convex UI component patterns from the live Storybook preview. Use when building React components, forms, modals, navigation, feedback states, or app layouts that should match the current Convex design system. Applies to both shared primitives and dashboard style product UI.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.