AGENT SKILL

principle-guard-the-context-window

Apply when context is filling up: large outputs, long files, repeated reads, fan-out planning. Route bulk to subagents; keep summaries in the main thread, not raw payloads.

License 许可
MIT
最近更新
2026-11-01
Stars
★ 0
Forks
0

01 前言 Front Matter

name
principle-guard-the-context-window
description
Apply when context is filling up: large outputs, long files, repeated reads, fan-out planning. Route bulk to subagents; keep summaries in the main thread, not raw payloads.
disable-model-invocation
true

03 SKILL.md 正文

Guard the Context Window

The context window is finite and non-renewable within a session. Every token should be worth its cost.

Why: Context overflow degrades reasoning quality, creates compression artifacts, and halts progress.

Pattern:

  • Isolate large payloads. Route verbose outputs, screenshots, and large documents to subagents. The main context gets summaries, not raw data.
  • Don't read what you won't use. Read selectively based on relevance. If a file isn't needed for the current task, skip it.
  • Keep frequently used content inline. Templates and references used on every invocation belong in the skill file, not in separate files that cost a read each time.
  • Size phases and cap scope. Limit files per phase, set turn budgets, account for mechanism costs.

04 同仓库更多 Skills

YunosukeYoshino
YunosukeYoshino/pstack-devin

pstack

poteto-mode for Devin: deliberate, verified, concise engineering mode that routes to the bundled pstack library (how, why, architect, swarm, arena, interrogate, tdd, unslop, principles, playbooks). Invoke explicitly via @skills:pstack or when the user asks for poteto / pstack mode.

★ 0
YunosukeYoshino
YunosukeYoshino/pstack-devin

why

Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.

★ 0
YunosukeYoshino
YunosukeYoshino/pstack-devin

unslop

Cut AI tells from any writing. Must always apply.

★ 0
YunosukeYoshino
YunosukeYoshino/pstack-devin

typescript-best-practices

TypeScript best practices. Use when reading or editing any .ts or .tsx file.

★ 0
YunosukeYoshino
YunosukeYoshino/pstack-devin

technical-writing

Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.

★ 0
YunosukeYoshino
YunosukeYoshino/pstack-devin

teach

Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.

★ 0