2,519 件 ・ 関連度順
概要と使いどころ
Use when safely removing dead frontend code, unused exports, stale components, obsolete routes, unused dependencies, or cleanup targets found by tools such as knip, depcheck, ts-prune, TypeScript, ESLint, or manual review. Do not use for feature rewrites that change behavior; Chinese triggers include dead code, clean up unused, refactor clean, dependency cleanup, delete useless code.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing, implementing, or reviewing frontend interaction motion, page transitions, scroll animation, Framer Motion, GSAP, Lottie, CSS animation, motion intensity, animation performance, reduced-motion behavior, or cinematic but accessible UI motion. Do not use for SVG-only path drawing, Canvas/WebGL rendering, or ordinary hover states; Chinese triggers include motion design, interactive effects, page transitions, scroll animation, Framer Motion, GSAP.
日本語の概要は準備中です。原文の説明を表示しています。
Shape, implement, review, copy-edit, or harden Arcade user interfaces. Use for the website, terminal UI, game HUDs, interaction flows, responsive behavior, accessibility, Geist consistency, and any change affecting what a user sees, understands, chooses, or does. Skip backend-only, telemetry-only, generated-file, and test-only work with no shipped UI impact.
日本語の概要は準備中です。原文の説明を表示しています。
Build an ORC behavior tree workflow using the DSL
日本語の概要は準備中です。原文の説明を表示しています。
Validate OpenClaw release candidates through OCM using the built OpenClaw artifact, a broad reusable scenario matrix, copied existing-user state, clean new-user state, concise pass/fail reporting, and focused failure notes. Use when asked to test OpenClaw origin/main, release readiness, upgrade behavior, plugins, services, channels, doctor recovery, packaging, or broad release risk.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Embedded/Firmware Engineer — analyzing worst-case execution time for a hard real-time deadline, choosing static over dynamic memory allocation to avoid fragmentation on a long-uptime device, keeping an interrupt service routine minimal and deferring work to the main loop, synchronizing a variable shared between an ISR and main context to prevent a torn read, or verifying a hardware register interaction against the datasheet's exact timing rather than observed bench behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a board-certified Clinical Neuropsychologist — building a neuropsychological battery to localize a brain-behavior deficit, adjudicating performance validity before interpreting any cognitive score, distinguishing a dementia subtype or mTBI sequela from a psychiatric or malingering cause, or writing a forensic, pre-surgical (epilepsy/tumor), or serial-retest report.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Childcare Worker — checking ratio/headcount compliance across mixed-age groups, deciding whether a fall or minor incident needs a written report versus a verbal mention at pickup, redirecting a behavior problem in an unstructured (non-curriculum) setting, or triaging which of several simultaneous demands (a crying toddler, a fight over a toy, a diaper) gets attention first.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Adapted Physical Education Specialist — writing a legally-defensible PE present level and annual goal from motor/fitness assessment data, choosing the right test battery and alternate items for a student's mobility profile, recommending a placement step on the PE least-restrictive-environment continuum, or distinguishing a motor/balance deficit from a behavioral avoidance pattern.
日本語の概要は準備中です。原文の説明を表示しています。
Content quality and E-E-A-T analysis with AI citation readiness assessment. Enhanced with live Ahrefs (actual keyword rankings, positions) and GSC (search query performance) data to validate static E-E-A-T analysis with real user behavior. Use when user says "content quality", "E-E-A-T", "content analysis", "readability check", "thin content", or "content audit".
日本語の概要は準備中です。原文の説明を表示しています。
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Create `AGENTS.md` file for a project. Use when the user wants to set up custom instructions, configure AI coding assistant behavior, or create project-specific coding guidelines for AI agents.
日本語の概要は準備中です。原文の説明を表示しています。
Security audit of a codebase — web apps, APIs, services, CLI tools, libraries, daemons, and more. Use when asked to find security bugs, do a security review, audit for vulnerabilities, or pen-test the code. Focuses on exploitable issues with real impact, not theoretical concerns or industry-standard behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Guidance for Tauri v2 shell plugin with secure command execution and open behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Guidance for Tauri v2 single-instance behavior and second-launch argument handling.
日本語の概要は準備中です。原文の説明を表示しています。
Guidance for Tauri v2 system tray interactions and platform behavior differences.
日本語の概要は準備中です。原文の説明を表示しています。
Test coverage quality analysis — behavioral coverage, critical gap identification, test resilience evaluation.
日本語の概要は準備中です。原文の説明を表示しています。
Observes runtime behavior of binaries via QEMU emulation, GDB debugging, and Frida hooking — syscall tracing, breakpoints, memory inspection, and function interception. Use when running, tracing, or debugging a binary, verifying hypotheses from static analysis, or watching actual syscalls, network calls, or file access; requires human approval before any execution.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes ELF binaries, executables, and firmware images to understand behavior without source code; coordinates sub-skills binary-re:triage, binary-re:static-analysis, binary-re:dynamic-analysis, binary-re:synthesis, and binary-re:tool-setup. Use when working with a binary, executable, or ELF file; asked to reverse engineer, disassemble, decompile, or figure out what something does; targeting ARM64, ARMv7, x86_64, or MIPS; or analyzing Python bytecode (.pyc, marshal). For Python bytecode analysis, see docs/python-bytecode-re.md.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze behavioral health outcome tracking systems for clinical measurement validity, treatment effectiveness, and provider performance comparison.
日本語の概要は準備中です。原文の説明を表示しています。
Audit personal finance and budgeting app spending intelligence features. Triggers: you need to evaluate transaction categorization accuracy (MCC mapping, ML classification, merchant matching).
日本語の概要は準備中です。原文の説明を表示しています。
Audit a student information system for dropout risk prediction. Analyzes attendance patterns, grade trajectories, behavioral indicators, early warning model accuracy, intervention tracking, equity in risk scoring, and socioeconomic factor integration..
日本語の概要は準備中です。原文の説明を表示しています。
Analyze fleet safety programs including driver behavior scoring, accident trend analysis, CSA BASIC score monitoring, DOT audit readiness, Hours of Service compliance, and drug and alcohol testing programs.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze fleet fuel optimization systems including MPG consumption analytics, eco-driving behavior scoring, route fuel cost modeling, idling detection and anti-idle programs, IFTA tax compliance reporting, alternative fuel transition planning, EV charging infrastructure readiness, and EPA SmartWay partnership metrics for commercial vehicle fleets.
日本語の概要は準備中です。原文の説明を表示しています。