메뉴
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 직업 분류 기준
| 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-sdk-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:
parseNormalizedEventUse 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.
Apply Stave's desktop-first design system when a task changes UI, layout, theme, dialogs, sidebars, empty states, settings, prompt input, or other visual UX in this repo. Use for prompts like "디자인", "UI", "redesign", "polish", "sidebar", "dialog", "settings", or whenever a new interface pattern is introduced. Always use existing shadcn components and the radix-vega preset first — never hand-roll a control that shadcn already provides.
Release workflow for the Stave repository that confirms whether the next release is patch or minor before bumping the version, reviews the actual PR changes and PR description `Changes` sections in the release scope instead of relying on commit titles alone, generates release notes with `conventional-changelog`, and opens a pull request against `main` from a dedicated temporary release worktree so the user's original checkout stays on its original branch. Use when the user asks to cut the next release, ship the current changes as a versioned release, or prepare a release PR. After the PR merges, the repository's GitHub Actions workflow builds and publishes the release artifacts automatically.
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".
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.
Run a high-signal review of the current workspace diff or PR in Stave. Use when the user asks for "code review", "PR review", "review this diff", "high-signal review", "strict review", "inline comments only for real issues", or wants only objective bugs and applicable policy violations with validation before commenting.