3.7천건 · 관련도순
Route an explicitly requested independent/delegated browser QA assignment or durable E2E evidence need; do not trigger for direct Playwright/DOM/console/network inspection, ordinary UI implementation, backend-only work, or production-mutating flows.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
E2E artifact handling routing. Use when traces, videos, screenshots, reports, or failure bundles need controlled repository-local placement; do not use for simple unit tests or production-mutating E2E flows.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Coverage review and verification sufficiency routing. Use when test coverage, uncovered paths, coverage reports, or verification adequacy need a read-only QA review; do not use for writing tests or running browser/E2E artifacts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Creates new Claude Code skills following repository conventions with proper structure, frontmatter, workflows, code examples, and reference files. Use when users request "create a skill", "new skill", "generate skill", or "add skill to collection".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Creates safe rollback procedures for deployments with automated workflows, rollback runbooks, version management, and incident response. Use for "rollback automation", "deployment recovery", "incident response", or "production rollback".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Creates comprehensive deployment checklists with pre-deployment checks, smoke tests, verification steps, and sign-off workflows. Use for "deployment checklist", "release verification", "deployment runbook", or "production readiness".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Creates comprehensive GitHub Actions CI/CD workflows for linting, testing, building, and deploying. Includes caching strategies, matrix builds, artifact handling, and failure diagnostics. Use for "GitHub Actions", "CI pipeline", "workflow automation", or "continuous integration".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when Spark engineering knowledge must be placed, deduplicated, migrated, or validated across AGENTS, Notes, Roles, Skills, and Workflows.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.