coach
AGENTS.md6 starsChanged 8 months agoMITView on GitHub
Project context for AI agents working in this repository. Read this file to understand the project, conventions, and workflow. Coach is a skills and knowledge workspace for AI-assisted course development. The primary artifacts are agent skill definitions (skills/), YAML knowledge files (knowledge/), and markdown documentation. This is not a code project. Course content lives in separate repos that symlink to this one. See docs/setup-course-repo.md for the pattern. SLT Format: Always "I can..." or "Learner can..." phrasing. Tool/library names are fine;…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,774 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository16 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- andamio-cliSkill
- apprenticeSkill
- assess-sltsSkill
- beginnerSkill
- classify-lesson-typesSkill
- compileSkill
- compoundSkill
- course-workflowSkill
- draft-sltsSkill
- gather-code-examplesSkill
- gather-screenshotsSkill
- releaseSkill
- self-assess-readinessSkill
- startSkill
- teacherSkill
The file
We split this AGENTS.md into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 45
SLT Format: Always "I can..." or "Learner can..." phrasing.
- Very specific: line 48
Ready: All dimensions Strong/Current — can coach now
- Distinctive: line 60
Avoid em-dash flourishes, dangling participles after em-dashes, route-path-only descriptions, non-decisional UI element descriptions, and …
- Very specific: line 84
All assessment skills read from knowledge/ before running.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.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
AGENTS.md
Project context for AI agents working in this repository. Read this file to understand the project, conventions, and workflow.
Project Overview
Coach is a skills and knowledge workspace for AI-assisted course development. The primary artifacts are agent skill definitions (skills/), YAML knowledge files (knowledge/), and markdown documentation.
This is not a code project. Course content lives in separate repos that symlink to this one. See docs/setup-course-repo.md for the pattern.
Directory Structure
skills/ # Agent skill definitions (15 skills, Agent Skills standard)
start/ # Entry point — welcome and pathway selection
beginner/ # Guided pathway for new course creators
apprentice/ # Collaborative pathway for content experts
teacher/ # Fast-track pathway for experienced educators
course-workflow/ # Orchestrates the 12-phase workflow
draft-slts/ # Generates SLTs from topic, audience, and goals
assess-slts/ # Evaluates SLT quality across 5 dimensions
self-assess-readiness/ # Evaluates coaching readiness per SLT
classify-lesson-types/ # Classifies SLTs by lesson type
gather-screenshots/ # Screenshot checklists for Product Demo lessons
gather-code-examples/ # Code example checklists for Developer Documentation
compound/ # Extracts patterns to improve future runs
compile/ # Packages modules into Andamio import format
andamio-cli/ # Import/export content via Andamio CLI
release/ # Publishes new versions across all channels
knowledge/ # Compound knowledge base (YAML files)
index.yaml # Master index and aggregate stats
voice-patterns.md # Prose style guide for lesson writing
slt-patterns/ # Verb bank, quality issues, successful rewrites
readiness/ # Context leverage rankings, calibration data
lesson-types/ # Heuristics and edge cases
lesson-writing/ # Style anti-patterns and acceptable patterns
compile/ # Import gotchas discovered during platform uploads
research/ # SLT research report
docs/ # Framework and product documentation
scripts/ # Setup script for course reposConventions
SLT Format: Always "I can..." or "Learner can..." phrasing. Tool/library names are fine; implementation details belong in lessons.
Readiness Tiers:
- Ready: All dimensions Strong/Current — can coach now
- Needs Context: At least one dimension Partial/Uncertain — needs supplementary docs
- Needs Human: At least one dimension Weak/Likely Stale — requires expert co-authorship
Lesson Types:
- Product Demo — SLT + screenshots → visual walkthrough
- Developer Documentation — SLT + code + docs link → technical lesson
- How To Guide — SLT + optional materials → step-by-step procedure
- Organization Onboarding — SLT + org context → setup guidance
- Exploration — SLT + framing questions → big ideas, thought leadership, worldview challenges
Lesson Writing Style (from knowledge/voice-patterns.md and knowledge/lesson-writing/style-patterns.yaml):
- Avoid em-dash flourishes, dangling participles after em-dashes, route-path-only descriptions, non-decisional UI element descriptions, and over-explaining what just happened
- See
knowledge/lesson-writing/style-patterns.yamlfor the full anti-pattern list with examples
Course Development Workflow (12 Phases)
- Draft SLTs →
01-slts.md - Assess quality →
assess-sltsskill →02-slts-quality-review.md - Revise SLTs → apply feedback to
01-slts.mdand00-course.md - Classify lesson types →
classify-lesson-typesskill →03-lesson-type-classification.md - Assess readiness →
self-assess-readinessskill →04-readiness-assessment.md - Create delegation map →
05-delegation-map.md - Gather context →
gather-screenshotsandgather-code-examplesskills - Build lessons →
lessons/with Fist to Five signals - Compile modules →
compileskill →compiled/ - Import to platform →
andamio-cliskill - Compound →
compoundskill →knowledge/ - Promote → move to
courses/[slug]/
Multi-Repo Setup
Course content lives in standalone repos that symlink to this skills repo. See docs/setup-course-repo.md for the full pattern and setup script. Knowledge compounds back to this repo regardless of where skills are invoked.
Skill Dependencies
All assessment skills read from knowledge/ before running. If knowledge files don't exist (fresh install or after reset), skills proceed without prior patterns.
The compound skill writes back to knowledge/, closing the compounding loop.
Roadmap
Current phase: Phase B (Package and Distribute). Phase A (Build Workflow and Lesson Skills) is complete with 14 skills. Phase B adds plugin manifests, npm packaging, and the Andamio marketplace for Claude Code. Phase C extends to additional platforms.
Plugin Context
When running as a Claude Code plugin, skills resolve paths using ${CLAUDE_PLUGIN_ROOT} (immutable plugin files) and ${CLAUDE_PLUGIN_DATA} (persistent user data). The /start skill initializes user knowledge from seed data on first run. The /compound skill writes to ${CLAUDE_PLUGIN_DATA}/knowledge/. Clone/symlink users are unaffected — paths default to project-relative.
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.

