agentleFS
Andamio-PlatformAndamio-Platform/coach/AGENTS.md

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;…

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
  1. Distinctive:

    SLT Format: Always "I can..." or "Learner can..." phrasing.

    line 45
  2. Very specific:

    Ready: All dimensions Strong/Current — can coach now

    line 48
  3. Distinctive:

    Avoid em-dash flourishes, dangling participles after em-dashes, route-path-only descriptions, non-decisional UI element descriptions, and …

    line 60
  4. Very specific:

    All assessment skills read from knowledge/ before running.

    line 84

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

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 repos

Conventions

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:

  1. Product Demo — SLT + screenshots → visual walkthrough
  2. Developer Documentation — SLT + code + docs link → technical lesson
  3. How To Guide — SLT + optional materials → step-by-step procedure
  4. Organization Onboarding — SLT + org context → setup guidance
  5. 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.yaml for the full anti-pattern list with examples

Course Development Workflow (12 Phases)

  1. Draft SLTs → 01-slts.md
  2. Assess quality → assess-slts skill → 02-slts-quality-review.md
  3. Revise SLTs → apply feedback to 01-slts.md and 00-course.md
  4. Classify lesson types → classify-lesson-types skill → 03-lesson-type-classification.md
  5. Assess readiness → self-assess-readiness skill → 04-readiness-assessment.md
  6. Create delegation map → 05-delegation-map.md
  7. Gather context → gather-screenshots and gather-code-examples skills
  8. Build lessons → lessons/ with Fist to Five signals
  9. Compile modules → compile skill → compiled/
  10. Import to platform → andamio-cli skill
  11. Compound → compound skill → knowledge/
  12. 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.