원클릭으로 Manus에서 모든 스킬 실행

the-explore-codebase

스타1

포크1

업데이트2026년 6월 23일 12:19

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.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

sendbird

sendbird/stave

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

The Explore Codebase

Start narrow, not broad.

Workflow

Read AGENTS.md and the architecture docs before loading large implementation files.
Use docs/architecture/index.md to choose the right subsystem.
Use docs/architecture/entrypoints.md to identify the first files to inspect.
Prefer the Agent tool with subagent_type: "Explore" for open-ended searches across the repo — it is faster and keeps the main agent's context clean. Reserve manual rg / Glob chains for pinpoint lookups when the target is already known.
Read only the slices that answer the current question.

Context Already Available

Before issuing a broad search, check whether retrieved context already contains the answer:

stave:repo-map retrieved context — condensed codebase map (hotspots, entrypoints, guides). Read this before launching an exploration agent.
stave:current-task-awareness retrieved context — the current workspace/task, visible tasks, and workspace information panel.

If the retrieved context pinpoints the subsystem, jump straight to targeted reads.

Stave Hotspots

src/store/app.store.ts is a coordinator (~2 100 lines), not a good first file for broad scanning. Read targeted slices with offset/limit.
electron/main/ipc/schemas.ts is the first stop for schema-ish regressions.
electron/providers/claude-sdk-runtime.ts and electron/providers/codex-app-server-runtime.ts should be checked together when behavior is provider-adapter-specific.
src/lib/providers/schemas.ts is the Zod discriminated union mirror of NormalizedProviderEvent — always inspect alongside src/lib/providers/provider.types.ts.
src/lib/session/provider-event-replay.ts is where normalized events become shared chat state.
src/types/window-api.d.ts is the renderer-visible IPC contract.

Output

Return:

the subsystem you inspected
the first files to read
the key contract boundaries
the smallest next search queries or follow-up files

Avoid

loading entire large files when a narrower slice is enough
treating projectFiles as a semantic code index
explaining the whole repo when the user asked about one path or feature
chaining manual rg/Glob when an Agent/Explore subagent would answer the same question with one call

이 저장소의 다른 Skills

같은 저장소

stave-worktree-pr-flow

sendbird/stave

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".

2026-07-071

lens-inspect

sendbird/stave

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.

2026-06-291

the-ipc-contract-audit

sendbird/stave

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", "계약", "스키마", "동기화 체크".

2026-06-231

the-provider-runtime-symmetry

sendbird/stave

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", "어댑터 대칭", "양쪽 프로바이더 확인".

2026-06-231

the-trace-execution-path

sendbird/stave

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.

2026-06-231

name	the-explore-codebase
description	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.
compatible-tools	["claude","codex"]
category	navigation
test-prompts	["이 레포 구조 좀 빠르게 파악하고 싶어","chat panel 관련된 파일들 어디야","where should I start reading for the IPC layer","stave auto 구현 어디에 있어"]

The Explore Codebase

Start narrow, not broad.

Workflow

Read AGENTS.md and the architecture docs before loading large implementation files.
Use docs/architecture/index.md to choose the right subsystem.
Use docs/architecture/entrypoints.md to identify the first files to inspect.
Prefer the Agent tool with subagent_type: "Explore" for open-ended searches across the repo — it is faster and keeps the main agent's context clean. Reserve manual rg / Glob chains for pinpoint lookups when the target is already known.
Read only the slices that answer the current question.

Context Already Available

Before issuing a broad search, check whether retrieved context already contains the answer:

stave:repo-map retrieved context — condensed codebase map (hotspots, entrypoints, guides). Read this before launching an exploration agent.
stave:current-task-awareness retrieved context — the current workspace/task, visible tasks, and workspace information panel.

If the retrieved context pinpoints the subsystem, jump straight to targeted reads.

Stave Hotspots

src/store/app.store.ts is a coordinator (~2 100 lines), not a good first file for broad scanning. Read targeted slices with offset/limit.
electron/main/ipc/schemas.ts is the first stop for schema-ish regressions.
electron/providers/claude-sdk-runtime.ts and electron/providers/codex-app-server-runtime.ts should be checked together when behavior is provider-adapter-specific.
src/lib/providers/schemas.ts is the Zod discriminated union mirror of NormalizedProviderEvent — always inspect alongside src/lib/providers/provider.types.ts.
src/lib/session/provider-event-replay.ts is where normalized events become shared chat state.
src/types/window-api.d.ts is the renderer-visible IPC contract.

Output

Return:

the subsystem you inspected
the first files to read
the key contract boundaries
the smallest next search queries or follow-up files

Avoid

loading entire large files when a narrower slice is enough
treating projectFiles as a semantic code index
explaining the whole repo when the user asked about one path or feature
chaining manual rg/Glob when an Agent/Explore subagent would answer the same question with one call