1.1万 件 ・ 関連度順
概要と使いどころ
Explain a complex concept through a short allegory, story, analogy, metaphor, or intuitive teaching example, then map it back to formal concepts and limits; do not use as the primary skill for implementation, specs, source-cited API guidance, or fiction-only writing.
日本語の概要は準備中です。原文の説明を表示しています。
Build Flutter/Dart cross-platform apps with widgets, state management, navigation, tests, and performance patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Build rich marketing/media frontend experiences with cinematic motion, AI assets, copy, and generative art.
日本語の概要は準備中です。原文の説明を表示しています。
Build or modify production UI components, layouts, client state, responsive behavior, accessibility, or UX inside an app when that frontend surface is the primary deliverable; do not trigger for rich campaign/media pages, backend integration, every user-facing text change, delegated browser QA, or review alone.
日本語の概要は準備中です。原文の説明を表示しています。
Performs read-only GitHub issue or PR triage with evidence links. Use when analyzing public or repository GitHub issues/PRs without mutating labels, comments, branches, reviews, merges, or issue state.
日本語の概要は準備中です。原文の説明を表示しています。
将已有中文论文正文、报告、邮件、说明或 PPT 文案改得自然、减少 AI 腔与模板感；用于明确的“说人话”、自然化改写或论文 AIGC 风险段落处理，不用于自动润色所有回答、从零代写论文、英文改写、概念教学、事实核查、检测分数保证或 PPTX 文件生成。
日本語の概要は準備中です。原文の説明を表示しています。
Implement an accepted change in bounded dependency-ordered increments when the user requests implementation and the scope benefits from multiple coherent slices; do not trigger merely because work touches multiple files, changes behavior, or is over an arbitrary line count.
日本語の概要は準備中です。原文の説明を表示しています。
Build native iOS apps with SwiftUI, UIKit, SnapKit, Apple HIG, accessibility, and platform UI patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Research one bounded mature-project/prior-art question when the user explicitly asks how established projects handle it or ROSE names a decision-shaping prior-art gap; do not trigger automatically for IDEATE, DEFINE, BUILD, implementation, local review, or every design choice.
日本語の概要は準備中です。原文の説明を表示しています。
Create, edit, fix, or explain Mermaid diagrams for relationships, decision branches, interactions, lifecycles, and data models; also use when the parent selects a diagram to materially clarify an explanation. Do not trigger for simple status, one fact, short lists, quantitative charts, or marketing slides.
日本語の概要は準備中です。原文の説明を表示しています。
Create, edit, fill, or template-format editable Word/DOCX documents with managed OfficeCLI first and OpenXML fallback for complex or preservation-sensitive work.
日本語の概要は準備中です。原文の説明を表示しています。
Create, fill, or reformat print-ready PDFs with strong visual page fidelity.
日本語の概要は準備中です。原文の説明を表示しています。
Create, edit, analyze, format, or validate Excel/XLSX/CSV spreadsheets with managed OfficeCLI first and pandas/XML preservation-aware fallbacks.
日本語の概要は準備中です。原文の説明を表示しています。
Generate or edit a source-grounded newsletter issue, digest, or briefing from provided or researched sources. Use for weekly/monthly updates, curated links, executive digests, community newsletters, or "turn these sources into a newsletter"; do not use for UI landing pages, marketing campaign design, unsourced news claims, or long-form research reports.
日本語の概要は準備中です。原文の説明を表示しています。
Run a non-destructive open-source, npm, or public release readiness checklist covering package metadata, provenance, license, internal artifact exposure, and dry-run evidence; complements security, shipping, and sanitizer reviews, and must not publish, delete, rewrite history, or mutate release state.
日本語の概要は準備中です。原文の説明を表示しています。
Prefer a fresh matching specialist for a clear bounded non-trivial package when current capabilities and permissions permit it; use direct ROSE work only for accepted direct-work exceptions or a concrete block.
日本語の概要は準備中です。原文の説明を表示しています。
Optimize a measured performance problem when the user names a latency/load/Core Web Vitals/resource target or current profiling evidence identifies a bottleneck; do not trigger from generic implementation, review, or an unsupported suspicion that code may be slow.
日本語の概要は準備中です。原文の説明を表示しています。
Break a clear scope or accepted specification into ordered tasks/packages when the user explicitly asks for a plan, estimate, dependency order, or task breakdown; do not trigger for ordinary implementation, every multi-step task, speculative parallelism, review, or completion.
日本語の概要は準備中です。原文の説明を表示しています。
Generate, edit, inspect, or verify editable PowerPoint/PPTX decks when a .pptx file is the deliverable; use for template-preserving edits and from-scratch slide production, but not for HTML/SVG mockups, PDF-only reports, or presentation advice that needs no PPTX artifact.
日本語の概要は準備中です。原文の説明を表示しています。
PR test analysis routing. Use for pull request or diff test impact, changed-test review, CI failure interpretation, and focused test matrix recommendations; do not use for general code review or editing tests.
日本語の概要は準備中です。原文の説明を表示しています。
Clarify a concrete requirements decision, create one bounded static interview packet, or run an explicitly user-invoked frontier batch over a plan, decision, or idea; trigger on explicit grill/interview/refinement intent or a named material ambiguity, not on ordinary planning, implementation, research, test-plan, report-style review, or BUILD work.
日本語の概要は準備中です。原文の説明を表示しています。
Optional focused post-implementation review routing. Use only when the user requests review or the changed surface has a clear specialist evidence need that direct diff inspection and the smallest relevant check cannot cover. Never creates an automatic review swarm.
日本語の概要は準備中です。原文の説明を表示しています。
Perform a bounded security design/hardening pass for explicit security or threat-model intent, or a concrete auth/authorization/secret/untrusted-input/file-upload/sensitive-data risk; do not trigger for every input, data store, third-party call, implementation, review, or release.
日本語の概要は準備中です。原文の説明を表示しています。
Produces comprehensive system architecture plans for features and products including component breakdown, data flow diagrams, system boundaries, API contracts, and scaling considerations. Use for "system design", "architecture planning", "feature design", or "technical specs".
日本語の概要は準備中です。原文の説明を表示しています。