'trace' 검색 결과

Design traceable data checks for reconciliation, integrity, transactions, and atomicity with separate observable oracles.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Execute explicitly authorized tests and record traceable expected, observed, evidence-bound results.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Plan explicitly authorized read-only production observations and trace evidence-backed causes into preventive regression coverage without external effects.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyze product risk and propose traceable QA coverage, priorities, environments, data, and explicit coverage gaps.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Assess requirement clarity, testability, completeness, consistency, and traceability without inventing missing acceptance criteria.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Select traceable regression coverage from change impact, affected risks, criteria, dependencies, and prior defects rather than execution convenience.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design traceable accessibility checks that combine scanners with observable keyboard, focus, semantic, and assistive-technology behavior.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design traceable API checks for contracts, authentication, authorization, errors, and idempotency with observable outcomes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the status, progress, completeness, traceability, or next valid action of a PWDEV Power product roadmap is requested

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create an approval-gated product requirements document or decompose an approved PRD into a traceable roadmap. Use for product-level problems, new initiatives, multi-feature scope, PRDs, release outcomes, or roadmap planning.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Métricas, logs, traces, dashboards, alertas e SLO — Prometheus, Grafana, Loki, Tempo, Mimir, Zabbix, Alertmanager. Use quando o usuário disser "dashboard", "alerta", "métrica", "PromQL", "Grafana", "SLO", "golden signals", "não temos visibilidade", "monitoramento".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Apply systematic root cause analysis and debugging methodologies to diagnose and fix bugs, test failures, and unexpected behavior. Use when encountering production issues, investigating test failures, diagnosing performance problems, tracing error sources through call stacks, analyzing logs and stack traces, reproducing inconsistent bugs, debugging race conditions, investigating memory leaks, or applying scientific method to problem-solving before proposing fixes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when asked to debug, fix a bug, investigate an error, or do root cause analysis, and when users report errors, stack traces, unexpected behavior, or say something stopped working.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Interactive developer experience plan review. Explores developer personas, benchmarks against competitors, designs magical moments, and traces friction points before scoring. Three modes: DX EXPANSION (competitive advantage), DX POLISH (bulletproof every touchpoint), DX TRIAGE (critical gaps only). Use when asked to "DX review", "developer experience audit", "devex review", or "API design review". Proactively suggest when the user has a plan for developer-facing products (APIs, CLIs, SDKs, libraries, platforms, docs). (gstack) Voice triggers (speech-to-text aliases): "dx review", "developer experience review", "devex review", "devex audit", "API design review", "onboarding review".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Set a redesign direction for an existing website. Analyzes the user's intent, picks a palette and visual direction, and writes the target spec (PRODUCT.md, DESIGN.md, DESIGN.json) plus a reasoning trace at stardust/direction.md. Use when the user asks to redesign a site, refresh the design, set a new design direction, define a redesign target, or invokes /stardust:direct.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

DEBUGGING SKILL — Read and analyze Cocos Creator project.log for runtime errors, warnings, and stack traces. USE FOR: any bug report, crash, UI glitch, TypeError, null reference, missing asset, CompositePanel mount fail, ChildPanel route fail, or screen spec wiring error. Load this skill FIRST before any runtime debugging session. DO NOT USE FOR: compile errors (use get_errors tool instead).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build, update, and query a persistent project knowledge graph from skills, memory, docs, and code structure — stdlib Python only, no external tools. Dual-mode: skill-library (agent-loom) or application (any consumer repo). Load when the user asks for a knowledge graph, project map, skill relationships, query the graph, update the graph, or trace how components connect. Auto-runs on memory-handoff and project-setup bootstrap. Also triggers on "build the graph", "what connects to X", "map this project".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Instrument a shipped product's AI agents with tracing and observability so you can see what they did, why outputs happened, and what each run cost. Plain-language primer plus free-tier-first backend selection (Langfuse, Phoenix, LangSmith, Braintrust) and OpenTelemetry/OpenInference instrumentation. Load when the user asks to add observability, add tracing, instrument my agents, see what my agent is doing in production, set up Langfuse or Phoenix or LangSmith, debug why my agent gave a bad answer, or track LLM cost per request. Also fires when agent-system-architecture or setup-evaluation requires an observability plan for an agent-chain product. NOT for tracing the coding agent itself — that is run-trace. Precondition for runtime-learning-loop.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Diagnose Sentry issues without copy-pasting stack traces. Uses the Composio CLI to pull issue details, events, breadcrumbs, and suspect commits, then maps the frames to local source so the agent can propose a fix directly.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Systematically finds and fixes bugs using proven debugging techniques. Traces from symptoms to root cause, implements fixes, and prevents regression.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.