703건 · 관련도순
Use when working with *.excalidraw or *.excalidraw.json files, user mentions diagrams/flowcharts, or requests architecture visualization - delegates all Excalidraw operations to subagents to prevent context exhaustion from verbose JSON (single files: 4k-22k tokens, can exceed read limits)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use quando executar planos de implementação com tarefas independentes na sessão atual
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Sistema autônomo multi-agente para startups em Claude Code. Ativado com "Loki Mode". Orquestra 100+ agentes especializados em engenharia, QA, DevOps, segurança, dados/ML, operações comerciais, marketing, RH e sucesso do cliente. Vai de PRD para produto totalmente implantado e gerando receita com zero intervenção humana. Inclui ferramenta Task para despacho de subagentes, revisão de código paralela com 3 revisores especializados, triagem de problemas baseada em severidade, fila de tarefas distribuída com tratamento de dead letter, implantação automática em provedores de nuvem, testes A/B, loops de feedback de clientes, resposta a incidentes, circuit breakers e auto-recuperação. Gerencia limites de taxa via checkpoints de estado distribuído e retomada automática com backoff exponencial. Requer flag --dangerously-skip-permissions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply when context is filling up: large outputs, long files, repeated reads, fan-out planning. Route bulk to subagents; keep summaries in the main thread, not raw payloads.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or proves it (codemod, script, generator, or a skill your subagents follow) instead of working by hand. The tool is the artifact a reviewer can rerun.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan and document handoffs, parent lane contracts, and parallel batch contracts between specialized AI agents (foreman, workers, reviewers). Use for multi-agent workflows, subagents, original goal preservation, native gates, claim ceilings, terminal states, baton passes, or guild-style agent coordination.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when executing implementation plans with independent tasks in the current session
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a coding agent (Claude Code, Cursor, Codex, Copilot CLI) burns through tokens or usage limits, sessions get slow or hit context limits, or the user asks to cut agent cost. Measures where the tokens go, then applies levers in order: session hygiene, always-loaded context (CLAUDE.md, skills, MCP), tool-output filtering, subagent delegation, output verbosity, and model/effort choice.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when designing defensive monitoring for agent systems whose risks accumulate across users, sessions, subagents, files, or tool calls. Adds online cross-context clustering with rare escalation, time-to-detect evaluation, provenance checks for control-like workspace content, and sanitized commits for persistent prompt-injection defense.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when designing long-horizon agents that need subagents, isolated context windows, filesystem-backed work, persistence, human approval, MCP tools, or production tracing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Accessibility review for Vue surfaces — the code-cleaning analog of /code-review and /simplify, pointed at WCAG/ARIA. Reviews just your diff (or a package/file), rates findings by severity, and either comments inline on the PR (--comment) or applies the safe fixes for you (--fix). Steers the depth-aware `a11y` subagent. Use when asked to "check accessibility", "a11y this", "audit ARIA/keyboard", or run /a11y.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Adversarially probe this monorepo for security flaws at the right depth. Steers the red-team subagent — picks quick/standard/deep from the request, spawns it (fanning out for a wide deep sweep), collates findings into a dated report, and files security/sec:* issues for confirmed high/critical findings. Use when asked to "red-team", "try to hack this", "find security holes", "pentest this package/app", or as the brain behind the CI + daily security runs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Front-end conventions review for Vue surfaces — the component-usage analog of /a11y, pointed at Nuxt UI 4 + crouton conventions instead of WCAG. Reviews just your diff (or a package/file) for v3 component names, the v4 overlay pattern, Options API, raw-HTML re-implementations, and hardcoded colors; rates findings by severity; and either comments inline on the PR (--comment) or applies the safe fixes for you (--fix). Steers the depth-aware `frontend-review` subagent. Use when asked to "check the frontend", "are we using Nuxt UI right", "review component usage", "frontend-review this", or run /frontend-review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when work needs Scrum roles, ceremonies, backlog refinement, sprint planning, story delivery, release readiness, or role handoffs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Add Agent Swarm (Teams) support to Telegram. Each subagent gets its own bot identity in the group. Requires Telegram channel to be set up first (use /add-telegram). Triggers on "agent swarm", "agent teams telegram", "telegram swarm", "bot pool".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Add Agent Swarm (Teams) support to Telegram. Each subagent gets its own bot identity in the group. Requires Telegram channel to be set up first (use /add-telegram). Triggers on "agent swarm", "agent teams telegram", "telegram swarm", "bot pool".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Update documentation to match code changes. Triggered by: 'update docs', 'sync documentation', 'README outdated', 'docs更新', 'ドキュメント直して'. Delegates to subagent to protect context.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Multi-agent collaboration plugin that spawns N parallel subagents competing on the same task via git worktree isolation. Agents work independently, results are evaluated by metric or LLM judge, and the best branch is merged. Use when: user wants multiple approaches tried in parallel — code optimi...
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create custom AI subagents with proper plugin structure, persona generation, and companion routing skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
ADHD-friendly output shaping for subagent responses. Lead with the next action, number multi-step tasks, end with one concrete next step, suppress tangents, restate state across turns, give specific time estimates, make wins visible, matter-of-fact errors, cap visible lists to 5, no preamble or closers. Loaded by genin, jonin, anbu, tokubetsu-jonin, and chunin when shaping final responses.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Standard Operating Procedures and router for MCP task triage, subagent selection, and orchestration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Coordinate Codex work across the current task, internal subagents, user-owned tasks, worktrees, handoffs, formal review gates, or recurring automation. Use for delegation, parallel roles, another Codex task, cross-repo work, QA/review handoffs, scheduled follow-up, or task inspection and continuation. Chinese triggers include 子Agent/子进程/子对话, 另一个对话接手, 并行处理, 分给QA, 多仓库收口, 巡检, 持续推进, 定时自动继续, 创建/读取/转交任务.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for AI SDK for Python async-generator tools, streaming tool output, subagent tools, PartialToolCallResult events, and custom tool aggregation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Procedimiento estructurado de 6 pasos para mejorar, renovar o reconstruir pipelines existentes, carpetas de proyectos individuales, estructuras de documentación o stacks de software. Direccionable como "pipeline optimizer" (para pipelines temáticos completos, p. ej. de software, investigación o desarrollo de videojuegos) o "project-folder optimizer" (para carpetas de proyectos individuales dentro de un pipeline, p. ej. una herramienta de software o proyecto de artículo académico). Se activa ante tareas como "mejorar pipeline X", "optimizar el stack", "reconstruir Y", "renovación", "refactorización de pipeline", "limpiar carpeta de proyecto", "mejorar estructura de carpetas", "unificar convenciones", "consolidación de documentación", "integrar en sistema existente" o cualquier intervención sustancial en estructuras establecidas. Proporciona análisis del estado actual, aclaración del propósito, boceto del estado ideal, plan de brechas, identificación empírica de puntos de dolor y reevaluación con subagentes limpios. Previene estándares paralelos, duplicación y rupturas en el pipeline.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.