poorvith-mp/skills-agents

agent-architecture

Design role decomposition, message passing, shared state and failure isolation across agents.

소스 보기

사용 방법

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

시작 전 확인

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

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

Agent Architecture

Design multi-agent systems where coordination does not become the failure mode.

Process

  1. Justify the second agent. Most tasks that look multi-agent are one agent with better tools. Split only when roles need genuinely different context or run concurrently.
  2. Decompose by context boundary, not by job title. An agent exists to hold a distinct working set, not to mirror an org chart.
  3. Define the contract between agents — the exact shape of what is passed, and what is guaranteed about it. Free-text handoff is where multi-agent systems lose information.
  4. Decide where state lives. Shared mutable state between agents needs the same care as between threads.
  5. Isolate failure. One agent failing or looping must not stall the others; set timeouts and a supervisor that can terminate.
  6. Make the trace reconstructable. When output is wrong, you need to see which agent decided what, with what input.
  7. Bound the total cost. Agents that can spawn agents need a hard ceiling.

Deliverables

  • Role decomposition with the context boundary justifying each agent
  • Message contracts between agents
  • Failure isolation, timeouts and supervision model
  • Trace format and cost ceiling

Verification & Quality Checklist

  • [ ] Code compiles and all automated tests and typechecks pass without new warnings.
  • [ ] Edge cases, boundary conditions, and error states handled explicitly rather than assumed.
  • [ ] No hardcoded secrets, credentials, or insecure defaults introduced.
  • [ ] Changes are covered by a test that fails without them.

Anti-Patterns & Constraints

  • NEVER weaken or skip a failing test to make a change land.
  • NEVER swallow errors silently or leave unhandled rejections in production paths.
  • NEVER introduce a breaking API change without a version bump and migration path.