variation-theory
Skill1 starsChanged 9 days agoNo licenceView on GitHub
Apply variation theory of learning to structure content using contrast, generalization, and fusion patterns. Variation must target the critical aspects of the learning objective. Use proactively when (1) writing educational materials, explanations, tutorials, or lecture slides, (2) designing or reviewing examples in documentation, READMEs, or literate programs (.nw files), especially when multiple examples illustrate alternative approaches to the same task, (3) structuring code examples, CLI usage examples, or API examples where the reader should notice what differs between alternatives, (4) user mentions variation theory, pedagogy, contrast, invariance, or critical aspects. Also activate when asked to elaborate or add examples. Works alongside literate-programming and didactic-notes skills; in educational LaTeX or .nw materials, keep variation-analysis labels in \ltnote{} rather than student-facing prose, unless the design is the document's subject (e.g. prose documenting a tangled learner-facing tutorial).
In this repository34 other files it gives its agents.
- canvas-quiz/CLAUDE.mdCLAUDE.md
- didactic-notes/CLAUDE.mdCLAUDE.md
- latex-writing/CLAUDE.mdCLAUDE.md
- literate-programming/CLAUDE.mdCLAUDE.md
- skill-management/CLAUDE.mdCLAUDE.md
- try-first-tell-later/CLAUDE.mdCLAUDE.md
- update-project-docs/CLAUDE.mdCLAUDE.md
- variation-theory/CLAUDE.mdCLAUDE.md
- writing-crypto/CLAUDE.mdCLAUDE.md
- backing-claimsSkill
- canvas-course-repoSkill
- canvas-infoSkill
- canvas-quizSkill
- commitSkill
- didactic-decksSkill
- didactic-notesSkill
- document-issuesSkill
- inbox-infoSkill
- kth-dataSkill
- latex-writingSkill
- literate-programmingSkill
- mentipySkill
- microsoft-foundrySkill
- nytid-todoSkill
- remarkableSkill
- reviewSkill
- scientific-writingSkill
- skill-managementSkill
- stacked-prsSkill
- testingSkill
- try-first-tell-laterSkill
- update-project-docsSkill
- worktree-subagentsSkill
- writing-cryptoSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 10 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.

