9,351 件 ・ 関連度順
概要と使いどころ
Use this skill when the user asks about International Fuel Tax Agreement (IFTA) compliance — quarterly returns, jurisdiction reporting, fuel + miles reconciliation, IFTA-100/101 forms, base jurisdiction selection, IFTA license + decals, recordkeeping requirements, common IFTA audit findings, or how to handle non-IFTA jurisdictions. Cite IFTA Articles of Agreement.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a carrier (asset-based, brokerage, or 3PL) asks how to respond to a shipper RFP / RFQ — bid packaging, lane analysis, rate strategy, SOPs/SOWs, qualifications response, insurance compliance, EDI requirements, and how to win competitive bids without leaving margin on the table.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks about trucking dispatch software — McLeod, TMW (Trimble), Tailwind, Truckbase, AscendTMS — vs load boards — DAT, Truckstop, 123Loadboard, Convoy, Uber Freight. Covers the workflow (find load, book, dispatch, run, settle), how dispatch software integrates with ELDs + accounting + customer EDI, and what small fleets vs larger fleets typically use.
日本語の概要は準備中です。原文の説明を表示しています。
SERP-based semantic topic clustering for content architecture planning. Groups keywords by actual Google SERP overlap (not text similarity), designs hub-and-spoke content clusters with internal link matrices, and generates interactive visualizations. Optionally executes content creation if claude-blog is installed. Use when user says "topic cluster", "content cluster", "semantic clustering", "pillar page", "hub and spoke", "content architecture", "keyword grouping", or "cluster plan".
日本語の概要は準備中です。原文の説明を表示しています。
FLOW framework integration: evidence-led SEO using the Find → Leverage → Optimize → Win loop. Surfaces stage-specific AI prompts from the FLOW knowledge base (41 prompts, CC BY 4.0). Use when user says "FLOW", "FLOW framework", "seo flow", "evidence-led SEO", "find leverage optimize win", or wants stage-specific SEO prompts.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Moves a person's whole Notion workspace into AI Matrx using only the AI Matrx and Notion connectors — every page and sub-page becomes an AI Matrx page (a Space) with its blocks, icons, covers, files and comments, and every database becomes a real table with typed columns, links, roll-ups, row pages, templates and views. Safe to run again; nothing duplicates. Use when the person says "move my Notion into AI Matrx", "copy my Notion", "import my Notion", or anything like it.
日本語の概要は準備中です。原文の説明を表示しています。
Scaffold recipe for a new authenticated route: SSR shell, DB-derived types, Redux hydration, view sub-pages. Use when creating a new route or page, adding a feature with a sidebar/main layout, adding view modes to a route, or feature types don't match database.types.ts.
日本語の概要は準備中です。原文の説明を表示しています。
react-resizable-panels v4 rules for this SSR codebase. Use when importing react-resizable-panels (PanelGroup and PanelResizeHandle are v3 names), editing components/ui/resizable* or features/code/layout/, building a split-pane, sidebar, or drag-handle layout, or persisting or toggling panel sizes.
日本語の概要は準備中です。原文の説明を表示しています。
Entry point and shared rules for structural changes to the live Matrx database. Use before any DDL: dropping, merging, or renaming a table, changing a function, RPC, trigger, or policy, hunting straggler tables, or starting a deprecated, schema move, or canonicalization (it routes to those skills).
日本語の概要は準備中です。原文の説明を表示しています。
The watch-fix-rerun method for making an existing platform agent or automated process efficient and correct: baseline its ledger, run one unit yourself, fix the class behind every wasted call, rerun, record. Use when asked to improve, optimize, watch, or 'make efficient' an agent, a sandbox session, a sync job, or any recurring automated process.
日本語の概要は準備中です。原文の説明を表示しています。
Bringing an existing table onto the platform base standard. Use when asked to canonicalize, retrofit, or 'Wave 3' a table, run apply_rls or an org backfill, retire a bespoke *_versions table, or move it onto platform comments/associations/permissions. NOT for a schema move (use db-move-table-schema).
日本語の概要は準備中です。原文の説明を表示しています。
Locate CCSPlayerPawn::SetModelFromClass in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the WeaponPaints gamedata entry "CCSPlayerPawn::SetModelFromClass" (symbol CCSPlayerPawn_SetModelFromClass). Shortlist via callers of CBaseModelEntity::SetModel inside pawn model-selection code: this variant takes the pawn's class model. The body resolves a cached model precache handle from the player class and calls SetModel. Distinguish from SetModelFromLoadout by the ABSENCE of loadout/inventory item lookups in the call chain. Trigger: CCSPlayerPawn_SetModelFromClass, CCSPlayerPawn::SetModelFromClass
日本語の概要は準備中です。原文の説明を表示しています。
Locate CCSPlayer_WeaponServices::DropWeapon in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the WeaponPaints gamedata entry "CCSPlayer_WeaponServices::DropWeapon" (symbol CCSPlayer_WeaponServices_DropWeapon). This is a VIRTUAL function — emit the vtable slot, NOT a byte signature. Resolve the CCSPlayer_WeaponServices vtable via RTTI and identify the DropWeapon slot: the body takes a CBasePlayerWeapon handle/pointer, detaches it from the player, spawns the dropped weapon entity and transfers ownership. Verify by xrefs from weapon-drop commands (!!drop) and pickup logic. vtable slots commonly differ between platforms — never assume identical indices. Trigger: CCSPlayer_WeaponServices_DropWeapon, CCSPlayer_WeaponServices::DropWeapon
日本語の概要は準備中です。原文の説明を表示しています。
Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Use when the user explicitly asks to threat model a codebase or path, enumerate abuse paths, or perform AppSec threat modeling.
日本語の概要は準備中です。原文の説明を表示しています。
Summarize URLs or files with the summarize CLI (web, PDFs, images, audio, YouTube). Use when you need fast CLI-based summaries from local or remote sources.
日本語の概要は準備中です。原文の説明を表示しています。
Converts Stitch designs into modular Vite and React components with system-level networking and AST-based validation. Use when translating design exports into production-ready React component architecture.
日本語の概要は準備中です。原文の説明を表示しています。
Create and manage teams of specialized AI agents that work together on tasks. Use when setting up multi-agent workflows, agent squads for content/marketing/research pipelines, configuring heartbeat-based agent coordination, or managing agent personalities via SOUL.md files. Enables orchestration of multiple OpenClaw sessions as a coordinated team with shared task systems (Linear, Trello, etc.).
日本語の概要は準備中です。原文の説明を表示しています。
Apple Human Interface Guidelines for Apple Watch. Use when building watchOS apps, complications, or workout features. Triggers on tasks involving Watch UI, Digital Crown, glanceable interfaces, or wrist-based interactions.
日本語の概要は準備中です。原文の説明を表示しています。
PostgreSQL、MySQL、および一般的なORM（Prisma、Drizzle、Kysely、Django、TypeORM、golang-migrate）にわたるスキーマ変更、データマイグレーション、ロールバック、ゼロダウンタイムデプロイメントのためのデータベースマイグレーションベストプラクティス。
未知のコードベースを分析し、アーキテクチャマップ、主要エントリポイント、規約、スターター CLAUDE.md を含む構造化されたオンボーディングガイドを生成する。新しいプロジェクトに参加する際や、リポジトリで初めて Claude Code をセットアップする際に使用。
Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component.
日本語の概要は準備中です。原文の説明を表示しています。
Set up Convex authentication with proper user management, identity mapping, and access control patterns. Use when implementing auth flows, setting up OAuth providers, or adding role-based access control.
日本語の概要は準備中です。原文の説明を表示しています。
Seed or import data into the Convex database.
日本語の概要は準備中です。原文の説明を表示しています。