guide-authoring
Skill11 starsChanged 7 days agoMITView on GitHub
Protocol for learn/**/*.md guides, tutorials, and docs (except learn/blog/*.md, owned by blog-post, and ADR bodies); use before authoring, relocating, or reviewing any learn/**/*.md document.
In this repository39 other files it gives its agents.
- architecture-pre-flightSkill
- blocked-task-stateSkill
- blog-postSkill
- context-recoverySkill
- create-skillSkill
- design-sweepSkill
- epic-createSkill
- epic-resolutionSkill
- epic-reviewSkill
- goal-scopingSkill
- hostile-content-quarantineSkill
- ideation-sandboxSkill
- identity-firewallSkill
- industry-friction-radarSkill
- lane-intentSkill
- lead-roleSkill
- memory-miningSkill
- neo-app-authoringSkill
- neo-identity-updateSkill
- neural-linkSkill
- overviewSkill
- peer-namingSkill
- peer-roleSkill
- post-review-pickupSkill
- pr-reviewSkill
- pull-requestSkill
- release-notesSkill
- self-repairSkill
- session-sunsetSkill
- structural-pre-flightSkill
- tech-debt-radarSkill
- ticket-createSkill
- ticket-intakeSkill
- ticket-triageSkill
- turn-memory-pre-flightSkill
- unit-testSkill
- update-roadmapSkill
- video-createSkill
- whitebox-e2eSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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
- Very specific: line 8
If you are authoring, relocating, OR reviewing a learn//*.md document (excluding learn/blog/*.md, owned by blog-post, and ADR bodies), you …
≈ “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
Guide Authoring Skill
If you are authoring, relocating, OR reviewing a learn/**/*.md document (excluding learn/blog/*.md, owned by blog-post, and ADR bodies), you MUST immediately use the view_file tool to read and strictly adhere to .agents/skills/guide-authoring/references/guide-authoring-bar.md before choosing a section, writing the first sentence, or posting a review verdict.
A learn/ document is held to a 9/10 bar: pre-write container placement against the repo's local learn/tree.json (§0), grounded by using the system's tools + memory-mining (not inference), narrative + benefits-driven with lived voice, render-verified TD Mermaid diagrams, conceptual-vs-reference separation, never hand-editing generated files, and a no-rubber-stamp reviewer gate against the WHOLE bar. Skipping it is the higher-cost path — MemoryCore took ~7 cycles and KnowledgeBase a rubber-stamp reversal precisely because this discipline was skipped.
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.