docs-reading
Skill1 starsChanged 6 months agoMITView on GitHub
Use before coding or reviewing Theseus runtime, primitive, server, client, or architecture changes when docs may define the intended boundary, status, or domain vocabulary.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- emeraldwalk/skillstheir own version, first seen Mar 28, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- emeraldwalk/skills★ 0same name
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 repository28 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-self-checkSkill
- biome-grit-rulesSkill
- biome-toolingSkill
- bun-testSkill
- bun-workspaceSkill
- cleanup-auditSkill
- code-reviewSkill
- dispatch-satelliteSkill
- docs-managementSkill
- effect-concurrency-lifecycleSkill
- effect-errors-schemaSkill
- effect-observability-timeSkill
- effect-services-layersSkill
- effect-testing-runtimeSkill
- effect-v4Skill
- jsx-md-authoringSkill
- monorepo-maintenanceSkill
- refactoring-disciplineSkill
- roadmap-managementSkill
- runtime-engineSkill
- server-runtimeSkill
- testing-patternsSkill
- theseus-designSkill
- tool-authoringSkill
- typescript-strictSkill
- ui-layout-disciplineSkill
- theseus-designSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill before code changes when docs may contain the boundary contract.
- Distinctive: line 35
If a draft conflicts with current docs or code, current docs/code win.
- Distinctive: line 54
Verify before asserting a doc is current.
- Very specific: line 55
Do not implement from drafts, brainstorms, or archive unless the user explicitly asks to promote that design.
- Distinctive: line 57
When code and active docs disagree, report the mismatch and update docs if the task includes docs maintenance.
- Distinctive: line 59
Do not import archived crew, lock-session, queue RuntimeBus, or plugin-host architecture into current runtime work.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Theseus Docs Reading
Use this skill before code changes when docs may contain the boundary contract. The goal is to read the right docs without treating drafts or brainstorms as implemented truth.
Read Order
Always start with:
docs/README.mddocs/maps/coding-agent-reading-map.md- the section README for the package or concept you are touching
- the nearest current concept note in
direction,primitives,runtime, orclients
Then read source code and tests. Docs guide what to inspect; code proves what exists.
Status Semantics
direction,primitives,runtime,clients: current doctrine or current implementation notes.drafts: proposals, research, or POCs. Useful context, not authority.brainstorms: speculative ideas. Never implementation authority.archive: superseded history. Read only to avoid reintroducing old paths.design-notes: adopted or active rationale. Use to understand why a current concept exists, then verify against current code.
If a draft conflicts with current docs or code, current docs/code win. Mention the conflict if it affects the task.
Package Pointers
- Core primitives:
docs/primitives/primitives.md, plus the specific note such astool.mdoragent-comm.md. - Runtime:
docs/runtime/architecture.md,docs/runtime/mission-system.md,docs/runtime/isolation.md,docs/maps/runtime-truth-map.md, anddocs/maps/not-real-yet.md. - Server: read runtime docs first, then server package code; server is a host adapter, not runtime owner.
- Client/operator surfaces:
docs/clients/README.mdand runtime command, control, query contracts. - Design changes: also read
docs/design-notes/self-editable-harness.mdand relevant drafts only if the task is exploring new direction.
Coding-Agent Rules
- Verify before asserting a doc is current.
- Do not implement from
drafts,brainstorms, orarchiveunless the user explicitly asks to promote that design. - When code and active docs disagree, report the mismatch and update docs if the task includes docs maintenance.
- Do not import archived crew, lock-session, queue RuntimeBus, or plugin-host architecture into current runtime work.
- Link docs with relative Markdown links when editing docs.
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.