agentleFS
deciqAIdeciqAI/knowledge-skills/cognitive-load-theory/SKILL.md

cognitive-load-theory

Skill13 starsChanged 4 months agoMITView on GitHub

Activate when: someone says 'this is too much to take in at once', 'learners aren't getting it despite good material', 'our onboarding is overwhelming new hires', 'why does this tutorial confuse people', 'how do I design training that actually works', 'this documentation is hard to follow', 'cognitive load', 'working memory'.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 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.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    One-line: when learners aren't getting it, check if working-memory load exceeds capacity — the fix is usually to reduce extraneous load, …

    line 31
  2. Distinctive:

    Check fit: If audience is expert, novice-friendly CLT techniques may backfire (expertise-reversal).

    line 32

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

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

Cognitive Load Theory

Overview

Working memory holds ~4 chunks of novel information — a hard limit. Instruction that exceeds it produces no learning regardless of effort. CLT (Sweller 1988) identifies three load types: intrinsic (task complexity), extraneous (poor presentation), germane (schema-building effort). Target: minimize extraneous, manage intrinsic by sequencing low-to-high element-interactivity, maximize germane.

Composes with metacognition (learners aware of limits pace themselves), deep-work (same working-memory conditions), and api-and-interface-design (UX design = instructional design).

When to Use

  • Designing training, documentation, onboarding, or instructional material
  • Learners aren't understanding despite good intent and reasonable material
  • Diagnosing why a course / tutorial / interface is underperforming
  • Someone says "cognitive load," "working memory," "too much at once," "this is overwhelming"

Not when: audience is already expert (expertise-reversal); bottleneck is motivational not cognitive.

Coaching Novices (Adaptive Front Door)

  • Engine mode: user has a concrete design problem → run The Process directly.
  • Coach mode: user is unfamiliar → guide step by step.

In Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.

  1. One-line: when learners aren't getting it, check if working-memory load exceeds capacity — the fix is usually to reduce extraneous load, not add more explanation.
  2. Check fit. If audience is expert, novice-friendly CLT techniques may backfire (expertise-reversal).
  3. Elicit the specific failure. Who's learning what, where stuck, what's the current instruction?

[WAIT — do not advance until user responds]

  1. Diagnose load types one question at a time: intrinsic too high? Extraneous load sources? Expertise match?

[WAIT — do not advance until user responds]

  1. Close: redesigned instruction with specific CLT effects applied + test with target learners.

[WAIT — do not advance until user responds]

The Process

Step 1 — Diagnose: Who is learning (expertise level) · What · Where stuck · Current instruction format · Overload signals (frustration, drop-off, error patterns).

Step 2 — Identify load types: Intrinsic (element interactivity, 1-5) · Extraneous sources (split attention / redundancy / wrong modality / irrelevant info / confusing notation) · Germane opportunity.

Step 3 — Reduce extraneous load: Split-attention → integrate diagram + label · Redundancy → cut duplicated text · Modality → narration over diagram, not text + text · Irrelevant → cut.

Step 4 — Match expertise: Novice: worked examples + heavy scaffolding · Intermediate: partial solutions + faded scaffolding · Expert: free problem-solving (CLT scaffolding now hurts — expertise reversal).

Step 5 — Maximize germane load: Sequence concrete→abstract · Use contrast to force schema-building · Pose questions before answers · Variable practice (same deep structure, different surface).

Step 6 — Test and iterate: Comprehension test with target learner (not designer) · Measure time-to-mastery · Track error patterns · Cut more extraneous load if struggle persists.

Output Template

# CLT-Informed Design: <instruction>
Learner (expertise): | Material: | Stuck point: | Overload signals:
Intrinsic load (1-5): | Extraneous sources: | Germane opportunity:
CLT effects applied: | Expertise match (novice/intermediate/expert):
Test plan: target learner · comprehension test · iteration trigger · owner

→ Method in Action: Sweller 1988 and the Development of CLT

Pack: CLT Application Patterns

DomainHigh-extraneous mistakeCLT fix
Software docsLong prose separated from codeIntegrate code + commentary; dual-modality
Onboarding"Read these 12 documents"Worked example: walk through 1 real task end-to-end
Training videosTalking head + bullet slidesDiagram + narration; cut redundant text
User interfacesMany simultaneous optionsProgressive disclosure; group related items
Code reviewMany unrelated changes in one PRSplit PRs by concern; one change at a time

Applying It Well

  • The right response to "they're not learning" is usually to cut extraneous load, not add more content.
  • Instructional design matters more than subject-matter expertise — a CLT-aware non-expert beats an oblivious expert.
  • Expertise-reversal is real: differentiate instruction for novices vs. experts; one-size-fits-all hurts one group.

→ Primary sources: references/sources.md

Common Rationalizations

[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.

Fake moveReality
[D] "Smart people can handle it"Working memory is hard-capped at ~4 chunks regardless of intelligence.
[D] "More information is better"False above capacity threshold — additional content above the limit produces no learning.
[D] "We can't cut anything — it's all important"Redundancy effect: cutting duplicated content improves comprehension.
[D] "Discovery learning is more engaging"Often true, but empirically poor for novices — imposes high extraneous load. Scaffold first.
[D] "Worked examples are passive"Sweller 1988: worked examples produce more learning than unaided problem-solving for novices.
[D] "Add another diagram to clarify"If it duplicates existing content, redundancy effect makes things worse. Replace, don't add.
→ Add [O] entries here after each real use — paste the actual failure patternWhat went wrong and why

Red Flags

  • Learners abandon training/docs at the same point repeatedly
  • "It's just complex" explains high failure rates without examining presentation
  • Instruction untested with target audience before deployment
  • Highly expert author unaware of expertise-reversal
  • Diagram and its explanation physically separated

Verification

  • Intrinsic, extraneous, and germane load identified separately
  • At least one CLT effect (split-attention, redundancy, modality) applied
  • Expertise level specified and instruction matched to it
  • Tested with target learners (not self-reviewed)
  • Comprehension or completion metrics measured

Part of deciqAI Knowledge Skills — 253 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. See it run → https://www.deciqai.com/s/cognitive-load-theory · Built by deciqAI · github.com/deciqAI · Contributions welcome.

Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/cognitive-load-theory.json

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.

Reviews can't be read right now.

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.