7,876 件 ・ 関連度順
概要と使いどころ
Smart, granular git commits following monorepo conventions. Analyzes changes, filters to session-relevant files, groups by intent, and uses conventional commit format. Use when committing code changes.
日本語の概要は準備中です。原文の説明を表示しています。
QA Engineer role in AID methodology. Use for test strategy, BDD scenarios, bug reporting, acceptance testing, flaky test prevention.
日本語の概要は準備中です。原文の説明を表示しています。
Roblox and Luau game code standards. Writes, reviews, and fixes Script, LocalScript, and ModuleScript code and game systems such as shops, DataStore saves, RemoteEvents, combat, NPCs, and UI. Use when a request involves Luau code or a Roblox Studio project, even when Roblox is never named, when a game bug is reported with no file named, and when the user asks to keep these standards active. Also covers Rojo, Argon, Azul, Script Sync, Studio MCP, and community libraries such as ProfileStore, Knit, Trove, and Fusion. Applies to requests written in any language. Not for plain Lua outside Roblox (Neovim, LOVE, Defold, other engines) or for game design with no Luau to write or review.
日本語の概要は準備中です。原文の説明を表示しています。
Draws an interactive HTML Architecture Viewer for any code flow the user names. Walks through seven research-driven steps (flow, name, repo research, lens colors, evidence flags, lens+mechanism per stop, build) and verifies links, claims, and generated artifacts before delivery.
日本語の概要は準備中です。原文の説明を表示しています。
Use the Crabbox wrapper for OpenClaw remote validation across Linux, macOS, Windows, and WSL2, including delegated Blacksmith Testbox proof. Report the actual provider and id.
日本語の概要は準備中です。原文の説明を表示しています。
既存のスライドデッキ/レポートを output_mode を保ったまま指定箇所だけ部分修正したいとき、意匠/技術コアと非対象箇所を壊さず修正後の再評価で視覚崩れ0にしたいときに使う。
Use when working in a repository that uses bd or Beads for durable project task tracking, issue dependencies, blocker management, multi-session handoff, or shared work memory. Trigger when the user asks to find ready work, claim or close tasks, create follow-up work, inspect blockers, recover project context, or choose between local planning and persistent project tracking.
日本語の概要は準備中です。原文の説明を表示しています。
スライドやレポートを新規生成し、開ける実HTMLを最小guard後に先に提示し、利用者が選んだ場合のみ診断・有界改善したいときに使う。
表形式の数値データを、記述・比較・分解・可視化・意思決定支援の単一 HTML レポートにするスキル。数値はコードで再現し、根拠の強さと限界を示す。レポートの打ち手を、ユーザーへのヒアリングを往復して、現場で動く人向けの「目的・ゴール・やること」の資料にもする。因果推論や高度な予測は対象外。「レポートを作って」「分析して」「データから何が言えるか」「月次レポート」「現場向けの資料」「実行部隊に渡す」「アクションプランにして」などで使う。アプリの画面には使わない。
Lightweight multi-agent research orchestration using one coordinator, three domain leads, and three lightweight research agents. Use for medium-size research, market scans, competitor comparisons, prior-art style exploration, report planning, and any task that benefits from parallel domain decomposition without running a full high-cost research lab.
日本語の概要は準備中です。原文の説明を表示しています。
Use when work needs deeper thinking, less generic output, repo evidence, tradeoffs, monitoring signals, or stronger quality discipline.
日本語の概要は準備中です。原文の説明を表示しています。
Use for documents, reports, memos, guides, academic papers, or formal text that needs clear structure, reliable tone, formatting, and diagrams.
日本語の概要は準備中です。原文の説明を表示しています。
Use before completion, PR, deploy, handoff, or when verifying code changes. Runs advisory or blocking checks and reports evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Conduct reproducible web searches and decision-oriented research across official sites, search engines, news, papers, forums, social platforms, and public datasets. Use when Codex must investigate a person, organization, product, market, technical resource, reputation, career choice, or other current topic; compare candidates; verify claims; collect dated citations; distinguish facts from inference and anecdote; or write an evidence-backed research report.
日本語の概要は準備中です。原文の説明を表示しています。
Design original, scalable logos and production-ready asset sets for a specific usage context. Use when Codex needs to create or refine a logo, symbol, wordmark, app icon, repository identity, CLI mark, website brand, social preview, or Codex skill/plugin icon; adapt concepts, formats, dimensions, variants, and delivery checks to the target platform instead of producing a context-free image.
日本語の概要は準備中です。原文の説明を表示しています。
Loads org- and repo-level coding rules from Qodo before code tasks begin, ensuring all generation and modification follows team standards. Use before any code generation or modification task when rules are not already loaded. Invoke when user asks to write, edit, refactor, or review code, or when starting implementation planning.
日本語の概要は準備中です。原文の説明を表示しています。
Loads org- and repo-level coding rules from Qodo before code tasks begin, ensuring all generation and modification follows team standards. Use before any code generation or modification task when rules are not already loaded. Invoke when user asks to write, edit, refactor, or review code, or when starting implementation planning.
日本語の概要は準備中です。原文の説明を表示しています。
Audit a composer output against four hard checks before delivery — cite integrity, voice rules, word count, schema validity. Always invoked after the polisher (English) or humanizer-* (Arabic / Hebrew). Emits a VerificationReport Pydantic object; orchestrator branches on `overall_passed`. Target ≥0.9 score per run. Triggers automatically as the final composer sub-agent; not user-facing.
日本語の概要は準備中です。原文の説明を表示しています。
Use when rating a project with Jevaluate that must stay private -- "/jevaluate-private <link or folder>", "rate this privately", "evaluate my own project", a client's or employer's code, a design doc or a local folder that isn't public, or any rating that must not reach the public ratings or the repo.
日本語の概要は準備中です。原文の説明を表示しています。
Use when rating whether a project, repo, skill, workflow, plugin, agent product or post uses TypeSafe's Jev (System One) model well -- "is this a good use of Jev?", "rate this Jev integration", "jevaluate <url>", or a link to something named after Jev; also when checking whether something that calls itself Jev actually uses it.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a .idd.yml by auto-detecting a repo's stack, test runner, and size. Use to init, setup, or configure IDD Stack, or set up IDD. Don't use for editing an existing .idd.yml, creating issues (use /issue-creator), or plain git/npm init.
日本語の概要は準備中です。原文の説明を表示しています。
Agent Ready project design context for navigation, docs links, and interface tone. Use when building or reviewing UI in this repo so patterns match the documented product feel.
日本語の概要は準備中です。原文の説明を表示しています。
Run every Convex audit (authz, reviewer, advisor, insights) into one scored, deduped readiness report with an ordered fix plan — Lighthouse for your backend.
日本語の概要は準備中です。原文の説明を表示しています。
Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.
日本語の概要は準備中です。原文の説明を表示しています。