3.7천건 · 관련도순
Single entry point for all AEM as a Cloud Service Workflow skills. Covers workflow model design, custom process step and participant chooser development, launcher configuration, workflow triggering, and production support including debugging stuck/failed workflows, triaging incidents with Cloud Manager logs, thread pool analysis, and Sling Job diagnostics for the Granite Workflow Engine.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Optimize OpenCode IDE configuration and workflows for this portfolio
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Coordinate multi-step tasks across multiple skills for complex workflows.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Optimized workflows for OpenCode IDE with MiMo v2.5 free model
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build GLSL/WebGL/ShaderToy shaders and procedural visual effects such as SDF, ray marching, particles, and fluids.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create, revise, or evaluate repository Agent Skills when the user asks to write a SKILL.md, improve triggers or information hierarchy, restructure references/scripts/assets, or diagnose skill predictability; do not use for product code, AGENTS.md initialization, general prompt editing, or automatic repository-wide cleanup.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run a bounded red-green-refactor feedback loop only when the user explicitly requests TDD, accepts reproduction-first proof for a bug, or an accepted high-risk behavior specifically requires red/green evidence; do not trigger for every logic, bug, behavior, or implementation change.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate or materially revise a repository-local test plan, QA plan, acceptance matrix, or regression checklist on explicit request or when one concrete testability gap blocks formal DEFINE; do not trigger for ordinary implementation, test execution, TDD, review, or completion claims.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan and synthesize a source-grounded multi-paper literature review. Use for systematic literature reviews, survey matrices, inclusion/exclusion criteria, research gaps, or "review the literature on X" requests; do not use for reviewing one paper, ordinary web summaries, citation formatting only, or medical/legal conclusions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run one bounded adversarial pass when the user explicitly requests a report-style stress test or ROSE identifies a concrete material loophole in an existing strategy, spec, plan, review, or claim; do not trigger for an interactive grill/frontier interview or merely before write-back, implementation, reconciliation, or completion.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create or materially revise a durable specification when the user explicitly requests a spec/new feature contract or a named ambiguity requires formal DEFINE; do not trigger for ordinary bounded edits, implementation, task breakdown alone, review, or documentation of already-settled behavior.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Resolve one exact official/current documentation gap when the user requests source verification or a version-sensitive API/SDK/provider/framework question can materially change the current decision; do not trigger for every implementation decision, ordinary framework code, local business logic, or broad research.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Silent failure hunting routing. Use when a change might pass while skipping work, swallowing errors, losing evidence, weakening gates, or reporting false success; do not use for broad code review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Prepare an explicit production launch, staged rollout, launch-monitoring, or rollback plan; do not trigger from AILI SHIP, implementation completion, packaging, review, or release wording that lacks a concrete launch/rollout target.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Perform direct, bounded browser inspection through the `browser.qa` capability when the user requests runtime UI evidence or one browser-specific claim needs DOM/accessibility/console/network/visual verification; do not trigger for every UI change, backend work, delegated QA, or durable E2E artifact routing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create, edit, analyze, format, or validate Excel/XLSX/CSV spreadsheets with managed OfficeCLI first and pandas/XML preservation-aware fallbacks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
AI regression scouting routing. Use when agents, prompts, skills, model/tool routing, harness fixtures, or generated-output expectations change and need regression scenarios; do not use for ordinary product-code regressions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a backend service or an end-to-end frontend/backend integration when service/API/data boundaries are the primary deliverable; do not trigger for pure UI, contract design only, security review, test workflow, or every feature touching both folders.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.