菜单
Trace a behavior, event, or request path through the Stave codebase. Use when the request asks "where does this happen", "execution path", "call flow", "흐름 추적", "어디서 처리돼", or needs the exact producer -> bridge -> consumer chain.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Ship the full current in-progress work as a PR in one pass. If already running inside a workspace-linked `git worktree` (for example under `.stave/workspaces/*`), reuse that same worktree in place. Otherwise move the dirty state into a dedicated temporary worktree, commit with a Conventional Commit message, push, open a GitHub pull request, and clean up the temporary worktree unless the user asks to keep it. Use for prompts like "worktree 만들어서 PR", "현재 작업 PR로 올려줘", or "spin this dirty tree into a PR branch".
Use the Lens built-in browser to inspect a running web application. Trigger when the request involves previewing a page, taking screenshots, reading DOM, checking console errors, picking elements to locate source code, or comparing rendered output to a design spec.
Explore an unfamiliar area of the Stave codebase quickly. Use when the request asks for workspace structure, architecture overview, relevant files, entrypoints, "where should I look first", "관련 코드 확인", "구조 파악", or broad code search before implementation.
Audit Stave multi-file contracts before or during changes. Use when a task touches provider runtime options, IPC payloads, window.api, schemas, NormalizedProviderEvent, replay payloads, or asks for a contract or sync checklist. Trigger on phrases like "ipc", "schema", "runtimeOptions", "window.api", "provider event", "계약", "스키마", "동기화 체크".
Keep Stave's Claude and Codex provider runtimes in sync when editing one of them. Use when a change touches `electron/providers/claude-sdk-runtime.ts`, `electron/providers/codex-app-server-runtime.ts`, executable lookup, env construction, CLI session launch env, tooling status probes, or any provider-agnostic behavior. Trigger on phrases like "provider runtime", "claude adapter", "codex adapter", "sibling adapter", "PATH env", "CLAUDE_CONFIG_DIR", "CODEX_HOME", "tooling status", "어댑터 대칭", "양쪽 프로바이더 확인".
| name | the-trace-execution-path |
| description | Trace a behavior, event, or request path through the Stave codebase. Use when the request asks "where does this happen", "execution path", "call flow", "흐름 추적", "어디서 처리돼", or needs the exact producer -> bridge -> consumer chain. |
| compatible-tools | ["claude","codex"] |
| category | navigation |
| test-prompts | ["이 이벤트가 어디서 어디로 가는지 따라가줘","trace how a chat turn reaches the Claude adapter","provider event 렌더까지 어떻게 흘러가는지 확인","where does the terminal attach IPC end up in main"] |
Trace forward and backward across boundaries.
| Boundary | Files to confirm |
|---|---|
| Renderer → preload | src/types/window-api.d.ts, electron/preload.ts |
| Preload → main IPC | electron/main/ipc/*.ts, strict Zod schemas in electron/main/ipc/schemas.ts |
| IPC → provider runtime | electron/providers/claude-sdk-runtime.ts, electron/providers/codex-app-server-runtime.ts, electron/providers/adapter.factory.ts |
| Provider emit → normalize | src/lib/providers/provider.types.ts (TS union) + src/lib/providers/schemas.ts (Zod union, strictly validated at parseNormalizedEvent) |
| Normalized event → UI state | src/lib/session/provider-event-replay.ts, src/store/app.store.ts consumers, src/components/session/chat-panel-message-parts.tsx |
| Terminal IPC | electron/main/ipc/terminal.ts, electron/host-service/terminal-runtime.ts, src/components/layout/useTerminalSessionManager.ts |
docs/architecture/conversation-flow.md.src/lib/session/provider-event-replay.ts and the chat panel components.electron/host-service/, remember that async runtime functions (e.g. attachSession) must be awaited before being passed to respond() — JSON.stringify(Promise) silently becomes {}.Return:
parseNormalizedEvent