8,870 件 ・ 関連度順
概要と使いどころ
Build, modify, run, test, screenshot, record, and export Godot 4.x games with the gdx CLI. Use when Codex needs to create a new Godot game project, attach to an existing Godot project, generate GDScript, build scenes/resources from JSON specs, edit a running scene through the gdx daemon, capture screenshots, record animation clips, send input, inspect game state, run Godot tests, or produce exports through gdx.
日本語の概要は準備中です。原文の説明を表示しています。
Marketing operations manager handling budget planning, financial reporting, meeting preparation and follow-up, vendor management, and administrative workflows for marketing and communications departments. Designed for SME leaders who need to minimize time spent on operational overhead.
日本語の概要は準備中です。原文の説明を表示しています。
Manages brand identity, visual design system, and creative quality for MMIND.ai. Generates complete image prompts for Nano Banana Pro (Gemini), enforces the strict 5-color palette, flat-vector SaaS style, and typography standards. Use when user needs graphic prompts, brand consistency checks, visual style guidance, design briefs, or creative QA for any marketing asset.
日本語の概要は準備中です。原文の説明を表示しています。
Turn research, analysis, or any markdown the agent just produced into a live, beautifully designed web report with a shareable tracked URL via ReportRoom. Use when the user says "publish this", "make this shareable", "turn this into a report", "put this on a page", or wants findings to live beyond the chat. Not for recurring client deliverables (use client-reporter), slide decks (use deck-publisher), or proposals that need view alerts (use proposal-tracker).
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need to inspect NuGet package APIs, list public types, or decompile method/property signatures. Keywords: inspect package API, list types, decompile type, method signatures, NuGet interface.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need blast-radius analysis, dependency graphs, cross-repo impact, breaking-change diff, or architectural overview of .NET workspaces. Keywords: blast radius, dependency graph, impact analysis, cross-repo, call graph, endpoint map, EF Core lineage, breaking change, daemon, reindex.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need CRAP score and coverage risk analysis to find high-risk code before refactoring or release. Keywords: CRAP score, risk hotspots, cyclomatic complexity, test coverage gaps, coverage threshold.
日本語の概要は準備中です。原文の説明を表示しています。
Generate architecture and design documents for implemented code changes with risk-based depth selection. Automatically evaluates risk signals, layer spread, and change magnitude to choose documentation level (A/B/C). Use after completing a feature, before merging a PR that touches multiple layers or sensitive areas (auth, infra, migrations, payments), or when an implemented change needs a design record or ADR.
日本語の概要は準備中です。原文の説明を表示しています。
Specialized GitHub PR intelligence agent for automatically gathering comprehensive context from Pull Requests. Activate when users need CI failure analysis, review comment investigation, or PR status assessment. Triggers on requests like "CI 실패 원인 찾아줘", "gather review comments", "check PR status", "analyze PR".
日本語の概要は準備中です。原文の説明を表示しています。
Use when reverse engineering binaries, firmware, mobile apps, JavaScript/Electron apps, .NET assemblies, network protocols, or malware samples; when decompiling, deobfuscating, unpacking, debugging, or hooking shipped artifacts; when solving CTF challenges (pwn, crypto, forensics, web); when a conclusion needs evidence from a shipped artifact rather than available source; or when routing authorized pentest and security-analysis work. Do not use for ordinary review of source code you already have.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need this project's coding standards (line length, quotes, import order, naming, commit format) — derive them from the REAL tooling config as a pointer + digest, never a guessed claim.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a component library needs a workshop — one story per concept, JSDoc summaries the manifest can carry, stories run as tests, and an opt-in MCP channel that replaces guessing with querying.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user says 'create service', 'new service class', or needs a PHP service following SOLID principles with proper DI and repository usage.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a diff builds more than the task needs — code that should not exist, a dependency the platform already covers, or a clever form where a flat one reads better. Deletion-hunting, not quality.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user says "check Jira", "create ticket", "update issue", or needs JQL queries, ticket transitions, or branch-to-ticket linking.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a diff needs a requirement review — does it satisfy every stated acceptance criterion — dispatched by /review-changes, /do-and-judge, /judge. Never infers criteria from the diff.
日本語の概要は準備中です。原文の説明を表示しています。
When triaging the quick legal-question channel + intake; classifies and ROUTES, never reviews. Triggers on 'is this a legal problem', 'do we need a lawyer for this', 'quick legal question'.
日本語の概要は準備中です。原文の説明を表示しています。
Use when setting up Laravel Pulse — real-time dashboard, built-in cards, custom recorders, performance insights — even when the user just says 'I need app monitoring' without naming Pulse.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a diff needs a readability review — naming, single-responsibility, DRY, dead code, mismatch with codebase conventions — dispatched by /review-changes, /do-and-judge, /judge.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a diff needs correctness review — null-safety, edge cases, off-by-one, races, error handling — dispatched by /review-changes, /do-and-judge, /judge, even without 'judge'.
日本語の概要は準備中です。原文の説明を表示しています。
Use when validation needs entry, business-logic, environment, and instrumentation guards so a bad value cannot reach the failure point — turns a local bug fix into a structural one.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a release review needs machine-derived evidence from git history — hotspot risk and change-coupling analyzers. Triggers on 'hotspot', 'what changes together', 'release forensics'.
日本語の概要は準備中です。原文の説明を表示しています。
Shared corpus-grounding engine — BM25 + structured filters + decision rules over CSV corpora via a domain manifest. Use when a skill needs grounded pre-action option-space constraints.
日本語の概要は準備中です。原文の説明を表示しています。
Run a two-agent proxy approval council for autonomous sprint gates. Use when a sprint needs delegated approval for human gates such as deploy, live mutation, push, cleanup, skip, or shortened watch decisions, while requiring two independent agents to reach consensus that the human principal would approve under written policy and preferences.
日本語の概要は準備中です。原文の説明を表示しています。