afaraha8403/balakit

subsystem-walkthrough

Walk through how a subsystem works: architecture, runtime flow, ownership, layering.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/afaraha8403/balakit --skill subsystem-walkthrough

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

Subsystem walkthrough

Leading words: mental model, one explainer, parallel slices, inherit host model.

Answer "how does X work?" at the level of a senior engineer onboarding onto the subsystem. Not annotated source.

Copy these steps into the todo list verbatim. Skip with skip: <reason>.

  1. Assess complexity. Simple → one explainer. Complex → 2–4 read-only explorers, then one synthesizer. Write Complexity: simple or Complexity: complex (N slices) as the first line of the output.
  2. Explore or explain (see below). Inherit the host model. Do not hardcode a slug.
  3. Present the explainer output with light edits only. Keep the Complexity line.

When in doubt, take the simple path.

Simple

One read-only subagent explores and explains in a single pass. Fill references/explainer-prompt.md without explorer findings.

Complex

Decompose into 2–4 distinct slices. Spawn explorers in one message, each with references/explorer-prompt.md. Then one synthesizer with the explainer template and every explorer's findings filled in. If the host cannot spawn subagents, run the slices sequentially yourself.

Output

First line: Complexity: simple or Complexity: complex (N slices).

Then: Overview / Key Concepts / How It Works / Where Things Live / Placement / Gotchas. Drop a section that does not apply. Placement is where new code for this subsystem should live (package, file, layer) — one short paragraph, not a second architecture essay.

Reply contract

The Complexity line, then the explanation. Do not rewrite it into a different structure after the explainer returns.