704 件 ・ 関連度順
概要と使いどころ
Humanization Quality Verifier - Ensures transformation integrity and quality Validates that humanization preserves meaning, citations, and academic standards Use when: after G6 transformation, before final export, for quality assurance Triggers: verify humanization, check transformation, validate changes
日本語の概要は準備中です。原文の説明を表示しています。
专业Marp演示文稿制作助手。支持完整工作流程：工作空间初始化、内容分析、slides制作、多维度审阅、中文语言规范审阅（中文演示文稿）、PNG转换检查、终稿确定。所有产出物集中管理在项目工作文件夹中。当用户提到"制作slides"、"做PPT"、"演示文稿"、"Marp"、"幻灯片"、"presentation"等关键词时自动启用。Professional Marp presentation assistant with complete workflow: workspace initialization, content analysis, slide creation, multi-dimensional review, Chinese language review (for Chinese presentations), PNG conversion check, and finalization. All outputs organized in project workspace.
日本語の概要は準備中です。原文の説明を表示しています。
Use when adding or following the red/yellow/green final status block convention for agent responses, especially by installing managed AGENTS.md or CLAUDE.md instructions.
日本語の概要は準備中です。原文の説明を表示しています。
Apply the same orchestration as `/efficient-fable` to any high-cost frontier model: delegate research, coding, and testing to cheaper subagents while keeping planning, synthesis, and final review with the expensive model.
日本語の概要は準備中です。原文の説明を表示しています。
Builds a consistent, filterable naming convention across your Google and Meta accounts based on your campaign types, objectives, targeting, and reporting needs. Makes filtering, reporting, and cross-platform analysis actually work instead of guessing what "Campaign_v3_Final_NEW" means. Platform: Google and Meta.
日本語の概要は準備中です。原文の説明を表示しています。
Write a `.cs` script file (create or overwrite) with the provided C# code. Validates syntax via Roslyn before write — invalid code is rejected with error details and the file is left untouched. Refreshes the AssetDatabase and delivers the final result via `requestId` after Unity finishes the triggered compilation. Use 'script-read' to inspect existing content first.
日本語の概要は準備中です。原文の説明を表示しています。
Delete one or more `.cs` script files from disk, refresh the AssetDatabase, and wait for Unity compilation to settle before delivering the final result via the request's `requestId`. Pair with 'script-read' to inspect files before deletion.
日本語の概要は準備中です。原文の説明を表示しています。
Uninstall a UPM package from the Unity project. Modifies `manifest.json` and may trigger a domain reload — the final result is delivered after the reload via the request's `requestId`. Built-in packages and packages that are dependencies of others cannot be removed. Use 'package-list' to list installed packages first.
日本語の概要は準備中です。原文の説明を表示しています。
Install a Unity package from the registry, a Git URL, or a local path. Modifies `manifest.json` and triggers package resolution; may also trigger a domain reload — the final result is delivered after the reload via the request's `requestId`. Use 'package-search' / 'package-list' for discovery first.
日本語の概要は準備中です。原文の説明を表示しています。
Package and finalize completed work for delivery — use when a feature is done and ready to ship
日本語の概要は準備中です。原文の説明を表示しています。
Qualify the exact final diff for a LoopX-managed goal. Use when goal policy enables change_quality_qualification, before a non-trivial delivery or merge, and when producing or repairing an exact-scope quality receipt. The workflow is language-neutral, permits at most one policy-authorized safe-fix pass, and never grants merge or repository authority.
日本語の概要は準備中です。原文の説明を表示しています。
Assess a JS SDK release candidate or release plan against the previous release and recommend ship or block.
日本語の概要は準備中です。原文の説明を表示しています。
Run the required final install, build, type, lint, test, and format checks after eligible SDK changes pass review.
日本語の概要は準備中です。原文の説明を表示しています。
Root-cause route for actual bugs, failing tests, build errors, crashes, stack traces, and unexpected behavior. Do not use for test-first/TDD feature work, test-report packaging, review-feedback handling, or final completion evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Test-first development route for TDD, writing failing tests first, RED -> GREEN -> REFACTOR, and behavior-changing feature/bug/refactor work. Do not use for already-failing test root-cause debugging, test-report packaging, or final completion evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Review-feedback handling route for CodeRabbit, GitHub, PR, or human reviewer comments. Use before implementing suggestions to verify each finding. Do not use for a fresh code review, security audit, TDD, or final completion evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Treat manuscripts as software: version control, reproducible builds, figure pipelines, CI, and structured repo layout. Helps teams avoid 'final_v7' chaos and ensures submission-ready artifacts.
日本語の概要は準備中です。原文の説明を表示しています。
Remove AI-generated code slop from a branch: unnecessary comments, redundant defensive checks, boilerplate, style drift, and type casts. Use for cleanup of AI-written code, not for broad code review, security audit, TDD, or final verification.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a reproducible final report, literature-outcome synthesis, JSON summary, and refreshed progress plot for a stopped or interrupted NVFLARE Auto-FL campaign.
日本語の概要は準備中です。原文の説明を表示しています。
Evidence-gated workflow for MoE performance optimization in Megatron Bridge. Covers measurement contracts, the Three Walls framework, parallel folding, profiling, matched A/B tuning, and final validation.
日本語の概要は準備中です。原文の説明を表示しています。
Convert user conversation into macro workflow requests and present curated clarification or final artifacts.
日本語の概要は準備中です。原文の説明を表示しています。
Review staged wiki writes and promote accepted pages to final locations when WIKI_STAGED_WRITES is enabled. Use for staging approval/commit; rejected pages return to _raw/ for editing.
日本語の概要は準備中です。原文の説明を表示しています。
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for 单色海报、双色印刷、单色调视觉、蓝色/绿色孔版印刷、risograph、网点照片、复古或当代编辑排版、zine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
日本語の概要は準備中です。原文の説明を表示しています。
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
日本語の概要は準備中です。原文の説明を表示しています。