umbel
CLAUDE.md7 starsChanged 5 months agoMITView on GitHub
tend tracks planned work across sessions. If it's not updated, the next session starts blind. When you need it: /tend discover (map an existing codebase into features) · /tend change (requirement changes) · /tend narrate (write the article body) For reads of a single feature, use the polyglot: bash docs/tend/<id>.tend.html data | jq.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- tend-auditSkill
- tend-brainstormSkill
- tend-changeSkill
- tend-discoverSkill
- tend-narrateSkill
- tend-planSkill
- tend-positionSkill
- tend-runSkill
- tendSkill
The file
We split this CLAUDE.md into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
When you need it: /tend discover (map an existing codebase into features) · /tend change (requirement changes) · /tend narrate (write the …
- Very specific: line 17
No plan? → /tend plan creates implementation steps
- Very specific: line 19
All done? → /tend audit verifies code matches checks
- Distinctive: line 22
When asked to implement multi-file changes, check tend first:
- Very specific: line 24
No match → /tend brainstorm to create one (minimal draft is fine)
≈ “Common” is an estimate: at least 1 in 5 of the 27,641 CLAUDE.md 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
tend — Feature Map
tend tracks planned work across sessions. If it's not updated, the next session starts blind.
Start here
/tend position— define who you're building for (personas + jobs)/tend brainstorm— shape your first feature into slots + checks/tend plan— break it into testable steps/tend run— build it/tend audit— verify it with real evidence
When you need it: /tend discover (map an existing codebase into features) · /tend change (requirement changes) · /tend narrate (write the article body)
Daily loop
/tend— see status + what's unblocked- Pick the suggested feature or choose from the list
- No plan? →
/tend plancreates implementation steps - Implement steps —
tend_update_featurewith steps[] (by-id merge) as you complete each - All done? →
/tend auditverifies code matches checks
Before you build
When asked to implement multi-file changes, check tend first:
ls docs/tend/features/(ortend_get_unblocked) — does this work map to a feature?- No match →
/tend brainstormto create one (minimal draft is fine) - Match →
tend_update_featurewith the touched step's status as you complete each
MCP tools
tend_get_context— full feature context in one calltend_get_unblocked— what to work on nexttend_update_feature— single write surface; step status is one of many fieldstend_get_gaps— what needs attention; each gap names the closing skillnpx tend-cli ui— generate web dashboard and open in browser
For reads of a single feature, use the polyglot: bash docs/tend/<id>.tend.html data | jq.
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.

