1.3만건 · 관련도순
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build native iOS apps with SwiftUI, UIKit, SnapKit, Apple HIG, accessibility, and platform UI patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Refines raw ideas through structured divergent and convergent thinking for ordinary non-command brainstorming, idea shaping, options comparison, and explicit IDEATE deepening routed by `aili-delivery-flow`; do not use as the top-level `/ideate` command owner or for existing-plan stress-test, review, or completion-claim checks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
将已有中文论文正文、报告、邮件、说明或 PPT 文案改得自然、减少 AI 腔与模板感；用于明确的“说人话”、自然化改写或论文 AIGC 风险段落处理，不用于自动润色所有回答、从零代写论文、英文改写、概念教学、事实核查、检测分数保证或 PPTX 文件生成。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnose user-reported AILI/ROSE harness or workflow behavior problems without editing files; use when the user says a command, skill trigger, subagent packet, memory flow, installer, docs, or agent prompt behavior is wrong and wants to know where the issue lives and how to fix it. Do not use for normal product-code bugs; return any approved modification need to ROSE.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Produce or apply an approved report-first proposal for workflow, ROSE, skill, command, subagent, memory, install, or harness-doc changes; use after harness-issue-triage localizes a harness problem or when the user explicitly requests harness maintenance, and do not edit core harness files without explicit human approval.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Handle an explicit Git intent such as branch/worktree setup, commit organization, history archaeology, conflict resolution, PR preparation, or versioning; do not trigger as a process skill for every code or file change.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build rich marketing/media frontend experiences with cinematic motion, AI assets, copy, and generative art.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build Flutter/Dart cross-platform apps with widgets, state management, navigation, tests, and performance patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze source data, tables, CSV/XLSX extracts, metrics, or experiment results with explicit data-authenticity checks. Use for profiling, cleaning assumptions, statistical summaries, segmentation, trend analysis, or "analyze this data"; do not use for spreadsheet file surgery, chart design only, database migrations, or claims without data provenance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create, edit, analyze, format, or validate Excel/XLSX/CSV spreadsheets with managed OfficeCLI first and pandas/XML preservation-aware fallbacks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structure source-grounded consulting-style analysis for strategy, market, product, operations, or decision memos. Use for MECE problem framing, hypotheses, options, tradeoffs, executive recommendations, or "consulting analysis" requests; do not use for legal/financial advice, implementation, data computation, chart rendering, or unsourced business claims.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review comment, JSDoc, TODO, README, and docs-to-code factual consistency, stale or low-value comments, and Chinese comment/variable appropriateness; do not use for general code review, broad documentation rewrites, or auto-editing comments without approval.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.