1.9천건 · 관련도순
AI-assisted pair programming with multiple modes (driver/navigator/switch), real-time verification, quality monitoring, and comprehensive testing. Supports TDD, debugging, refactoring, and learning sessions. Features automatic role switching, continuous code review, security scanning, and performance optimization with truth-score verification.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Trace bugs backward through call stacks and execution flows to identify the original source of errors, invalid data, or incorrect behavior. Use when debugging complex issues, tracing error origins, investigating data corruption, following execution paths, identifying where invalid data enters the system, or finding root causes of cascading failures.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Restrict file edits to a specific directory for the session. Blocks Edit and Write outside the allowed path. Use when debugging to prevent accidentally "fixing" unrelated code, or when you want to scope changes to one module. Use when asked to "freeze", "restrict edits", "only edit this folder", or "lock down edits". (gstack)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build generative UI apps with OpenUI and OpenUI Lang — the token-efficient open standard for LLM-generated interfaces. Use when mentioning OpenUI, @openuidev, generative UI, streaming UI from LLMs, component libraries for AI, or replacing json-render/A2UI. Covers scaffolding, defineComponent, system prompts, the Renderer, and debugging OpenUI Lang output.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Safety guardrails for destructive commands. Warns before rm -rf, DROP TABLE, force-push, git reset --hard, kubectl delete, and similar destructive operations. User can override each warning. Use when touching prod, debugging live systems, or working in a shared environment. Use when asked to "be careful", "safety mode", "prod mode", or "careful mode". (gstack)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Full safety mode: destructive command warnings + directory-scoped edits. Combines /careful (warns before rm -rf, DROP TABLE, force-push, etc.) with /freeze (blocks edits outside a specified directory). Use for maximum safety when touching prod or debugging live systems. Use when asked to "guard mode", "full safety", "lock it down", or "maximum safety". (gstack)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematic debugging with root cause investigation. Four phases: investigate, analyze, hypothesize, implement. Iron Law: no fixes without root cause. Use when asked to "debug this", "fix this bug", "why is this broken", "investigate this error", or "root cause analysis". Proactively invoke this skill (do NOT debug directly) when the user reports errors, 500 errors, stack traces, unexpected behavior, "it was working yesterday", or is troubleshooting why something stopped working. (gstack)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Debug AEM Workflow issues on AEM as a Cloud Service — stuck workflows, failed steps, missing Inbox tasks, launcher failures, stale instances, thread pool exhaustion, queue backlogs, purge failures, and permissions errors. Use when the user reports workflow problems on Cloud Service, asks why a workflow is stuck or failed, needs step-by-step troubleshooting, or provides thread dumps, configuration status output, or Sling Job console output for analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Triage AEM Workflow issues on AEM as a Cloud Service by classifying symptoms, gathering the right logs and metrics, and mapping to runbooks or Splunk searches. Use when the user asks for workflow activity/errors on a Cloud Service host, needs to classify a Jira ticket, or wants to know what to collect for workflow debugging.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Initialize an Adobe App Builder project end-to-end without Developer Console UI clicks. Creates the Console project and workspace, subscribes APIs (including those needing a product profile), maps user intent to the right template, runs non-interactive `aio app init`, and guides post-init customization. Use whenever the user mentions creating an App Builder app, scaffolding a project, `aio app init`, setting up an Experience Cloud extension, adding actions or web assets, creating a Console project or workspace, adding APIs, or bootstrapping App Builder — even if they don't say "App Builder". Also for SPA templates, AEM extensions, API Mesh, Asset Compute workers, and MCP server projects. Also handles debugging init failures — template not found, `aio app init` hangs or times out, Node version mismatches, npm install failures, post-init build errors, `aio login` issues, `aio app run` showing nothing, or `aio console project create` / `workspace create` / `workspace api add` errors.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guides concurrency and async decisions in Rust. Use when encountering Send/Sync errors (E0277), choosing between threads vs async, designing shared state, or debugging deadlocks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
iOS and Swift/SwiftUI development guidance, including App Clips, haptics, UI patterns, Liquid Glass styling, performance audits, view refactors, Swift concurrency, and iOS debugging. Use when building or reviewing iOS apps, SwiftUI views, or troubleshooting iOS issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when implementing or debugging ANY network request, API call, or data fetching. Covers fetch API, React Query, SWR, error handling, caching, offline support, and Expo Router data loaders (`useLoaderData`).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Deep reasoning mode for complex problems requiring maximum cognitive depth. Use when facing difficult architectural decisions, complex debugging, multi-step problem solving, or situations requiring careful analysis before implementation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
iOS and Swift/SwiftUI development guidance, including UI patterns, Liquid Glass styling, performance audits, view refactors, Swift concurrency, and iOS debugging. Use when building or reviewing iOS apps, SwiftUI views, or troubleshooting iOS issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert Bash help for writing, debugging, and optimizing safe, portable shell one-liners and scripts on macOS/Linux. Use when users ask for Bash or POSIX sh commands, script reviews, ShellCheck fixes, quoting/pipeline issues, process/file automation, or converting requirements into shell scripts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
BROWSER VFX ACCEPTANCE SKILL — Use built-in browser/headless browser to automatically verify Cocos VFX block effects and composed VFX recipes in BattleScene preview (`http://localhost:7456`, `previewMode=true`, `previewTarget=5`). USE FOR: VFX health audit, per-block smoke validation, combo recipe regression checks before merging `vfx-block-registry.ts` / `vfx-effects.json`. DO NOT USE FOR: Cocos Editor window screenshot capture, compile-error debugging, or pure log-only diagnosis without browser preview.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
COMPLETE BUG INVESTIGATION WORKFLOW — Combines screenshot + log reading into a full triage pipeline. USE FOR: any bug report that has both visual symptoms AND runtime errors, especially CompositePanel / ChildPanel mount failures, screen spec wiring breaks, or battle scene UI crashes. This is the master debugging workflow that orchestrates cocos-screenshot and cocos-log-reader together.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Append structured execution traces across operational, cognitive, and contextual surfaces with minimal overhead. Load when inspecting agent runs, logging tool calls and observations, enabling post-run debugging, or pairing with structured-planning step IDs. Also triggers on "trace this run", "log execution", "agent observability", "run log", or when fault-localize needs evidence. Default-on during multi-step plans. Traces live at .agent-loom/traces/ — git-ignored by default.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Capture actionable learnings that emerge during conversation — when the agent or user discovers that a skill, a set of skills, or a process needs to be updated based on what's happening in the current chat. Sub-skill of the learn-from orchestrator. Load when the user says "we should update the skill for this", "this should be a skill rule", "add this as a gotcha", "the skill should know about this", "update the process for this", "remember this for next time", "this is important for the skill". Also triggers when the agent notices a skill's guidance was wrong or incomplete, a process step failed or was unnecessary, a new pattern emerged, a guardrail was missing, a workaround became a pattern, or a debugging session reveals a gap.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Capture durable project memory from work, debates, debugging discoveries, learned conventions, deferred options, and session outcomes. Load when the user says remember this, save this learning, record what happened, update project memory, or preserve context for future agents.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Test and debug browser UIs using Chrome DevTools MCP — DOM inspection, console errors, network requests, performance traces, and visual verification. Load when building or debugging anything that renders in a browser, verifying a UI fix, profiling Core Web Vitals in a real page, or the user asks for browser testing with DevTools. Requires chrome-devtools MCP configured. Not for backend-only or CLI work. Pairs with frontend-design and performance-optimization.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Select alternative execution paths when a plan step fails — branch on outcomes instead of blind retry. Load when a structured plan step fails, an unexpected observation arrives, or the user asks what to try next after an error. Also triggers on "try another approach", "route around this failure", "replan on failure", "if X fails try Y", or outcome-based branching during multi-step work. Pairs with structured-planning and debug-and-fix. Does not replace root-cause debugging — adds plan-level path selection.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.