context-engineering
Skill1 starsChanged 7 months agoMITView on GitHub
Context rot prevention and subagent orchestration rules. Enforces clean context windows, file-based state, and delegation patterns. Auto-invoked during any Bayes Ship execution phase.
131 other projects use a version of this.
Adopted by
Most recently taken up by
- thistleknot/skillstheir own version, first seen Nov 8, 2026
- gerivdb/SKILLStheir own version, first seen Nov 8, 2026
- ishandutta2007/Awesome-Agent-Skillstheir own version, first seen Nov 8, 2026
- MMACABRE/SKILLStheir own version, first seen Nov 8, 2026
- gopalparashar421/agent-skillstheir own version, first seen Nov 8, 2026
- komluk/scaffoldingtheir own version, first seen Nov 7, 2026
Used with
Projects with it also use using-agent-skills, idea-refine and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
LLl0k0laDSkillusing-agent-skills
Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked.
Also in 36 projects that use this
- LLl0k0laDSkill
idea-refine
Refine ideas through structured divergent and convergent thinking. Use "idea-refine" or "ideate" to trigger.
Also in 44 projects that use this
HK-hubSkilldeprecation-and-migration
Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code.
Also in 40 projects that use this
MrCipherSmithSkillconstraint-driven-development
Use when a project needs a persistent, measurable quality bar — starting a project without documented standards, 'set up constraints', or when coverage/perf/a11y thresholds get re-debated per-PR. Produces CONSTRAINTS.md with enforceable numbers, ratchets, and a guard against silent weakening. NOT for throwaway prototypes or a one-off CI setup.
Also in 14 projects that use this
- HK-hubSkill
source-driven-development
Grounds every implementation decision in official documentation. Use when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.
Also in 44 projects that use this
- +6 more from LLl0k0laD
- +1 more from HK-hub
Other versions131 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 131
- addyosmani/agent-skills★ 114ksame name
- bojieli/ai-agent-book-projects★ 53ksame name
- bojieli/ai-agent-book★ 53ksame name
- rohitg00/pro-workflow★ 2.9ksame name
- mrgoonie/claudekit-skills★ 2.2ksame name
- kdlbs/kandev★ 1.1ksame name
- liza-mas/liza★ 418same name
- typv/nest-turbo-starter★ 224same name
- VAMFI/claude-user-memory★ 206same name
- shashankswe2020-ux/whoop-mcp★ 174same name
121 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository43 other files it gives its agents.
- accessibilitySkill
- agent-evalSkill
- agentic-engineeringSkill
- ai-regression-testingSkill
- api-designSkill
- atomic-planningSkill
- backend-patternsSkill
- coding-standards-eccSkill
- frontend-patternsSkill
- git-worktreesSkill
- langchain-dependenciesSkill
- langchain-fundamentalsSkill
- langchain-middlewareSkill
- langchain-ragSkill
- langgraph-fundamentalsSkill
- langgraph-persistenceSkill
- minimalist-skillSkill
- output-skillSkill
- redesign-skillSkill
- security-scanSkill
- ship-architectSkill
- ship-autoSkill
- ship-bugfixSkill
- ship-deploySkill
- ship-discoverSkill
- ship-executeSkill
- ship-finish-branchSkill
- ship-newSkill
- ship-planSkill
- ship-researchSkill
- ship-resumeSkill
- ship-reviewSkill
- ship-settingsSkill
- ship-specSkill
- ship-statusSkill
- ship-testSkill
- ship-worktreeSkill
- soft-skillSkill
- systematic-debuggingSkill
- taste-skillSkill
- test-driven-developmentSkill
- two-stage-reviewSkill
- verification-before-completionSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 117 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Subagents receive ONLY the context they need: Never pass full session history.
- Distinctive: line 28
When dispatching a subagent:
- Distinctive: line 30
Do not inherit session history
- Distinctive: line 31
Do not pass unrelated state files
“Common” is measured: kept by at least 6 in 10 of the 117 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Context Engineering
Context rot
Quality degrades as the context window fills:
- 0-30% context: Peak quality. Thorough, comprehensive.
- 50%+: Starts rushing. Cuts corners.
- 70%+: Hallucinations. Forgotten requirements.
Prevention rules
- Keep main session under 40% context. Delegate heavy work to subagents.
- Every execution task runs in a fresh subagent. Clean 200k token window per task.
- Subagents receive ONLY the context they need. Never pass full session history.
- State lives in files, not conversation memory.
- PROJECT.md, CONTEXT.md, PRD.md, ARCHITECTURE.md, progress.json
- Plans in .claude/state/plans/
- Research in .claude/state/research/
- After compaction, re-read progress.json to reconstruct state.
- Never say "I'll be more concise." That is a context rot symptom. Spawn a subagent instead.
Subagent isolation principle
When dispatching a subagent:
- Construct exactly the context it needs
- Do not inherit session history
- Do not pass unrelated state files
- The subagent should be able to do its job with only what you gave it
File-based state protocol
| File | Written by | Read-only after |
| PROJECT.md | /ship-new | Always |
| CONTEXT.md | /ship-discover | User approves discovery |
| RESEARCH.md | /ship-research | Always |
| PRD.md | /ship-spec | User approves spec |
| ARCHITECTURE.md | /ship-architect | User approves architecture |
| progress.json | Every phase | Never (always updated) |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.