本文へ移動
cccskills
無料GitHub で公開

learning-materials-design

Designs worksheets, workbooks and practice material that actually teach — sequencing difficulty, managing cognitive load, writing instructions a child can follow unaided, and building answer keys that hold up. Use this to design or fix a worksheet or workbook, decide how much practice a skill needs, structure a page so it can be completed without an adult reading it aloud, or diagnose material that looks right and does not work.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md6.4 KB
  • references/sources.md2.9 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Learning materials design

Most bad worksheets are not wrong. They are unusable: the instruction assumes a reading level above the skill being practiced, the page asks the student to hold three things in mind at once, or the difficulty jumps in a place the author could not see because the author already knows the answer.

The instruction is the hardest part of the page

A worksheet is used by a child, often without an adult reading it to them, and frequently by a parent who did not see the lesson. The instruction has to survive that.

Two constraints that conflict and have to be resolved deliberately:

  • The instruction's reading level must sit below the skill being practiced. A second-grade math page whose directions need third-grade reading is a reading test with numbers on it. The child who fails it may have no trouble with the math.
  • The instruction must be complete. "Solve" does not say whether to show work, what form the answer takes, or what to do with the remainder.

Where the two cannot both be met, the answer is usually a worked example rather than more words. One solved item at the top carries more instruction than a paragraph, and it is read.

Cognitive load is the budget

Working memory is the scarce resource, and a page spends it on three things at once: the skill being learned, the format it is presented in, and everything incidental — decoration, unfamiliar layout, a font that makes a 9 look like a g.

Only the first is worth spending on. The practical consequences:

  • Change one thing at a time. A page that introduces a new skill and a new answer format measures neither.
  • Keep the format stable across a section. Familiarity with the layout is load the student stops paying after the first page, and resetting it is a cost with no return.
  • Decoration competes with content. Illustration that carries meaning earns its space; illustration that fills it costs attention, most sharply for the students who have least to spare.

Difficulty rises in steps somebody checked

The author knows the answer, which makes difficulty jumps invisible from the inside. The reliable method is mechanical: list the sub-skills the final task requires, order them by dependency, and confirm every item exercises only sub-skills already introduced.

Where practice sits in a sequence changes what it should look like:

  1. Acquisition — heavily scaffolded, worked examples adjacent, immediate feedback possible. Errors here are information, so the page should make them visible rather than punish them.
  2. Fluency — scaffolding removed, volume up, the same skill in the same form. This is the stage most commercial material skips, and the reason a student who "understands it" cannot do it in March.
  3. Generalization — the skill in unfamiliar wrappers, mixed with earlier skills, in contexts the examples did not cover. This is where transfer is tested and where spaced review belongs.

Mixing stages on one page is common and usually a mistake: a generalization item among acquisition items reads as unfair, and an acquisition item among fluency items reads as filler.

The answer key is part of the product

An answer key that is wrong is worse than no key, because it is trusted. It is also where multiple valid answers get discovered — the page that admits two readings, the drawing task with no determinate result, the word problem whose units were never stated.

Build the key by solving the page cold, from the printed instruction, without reference to what was intended. Every item that is ambiguous when solved that way is ambiguous to the student, and the fix belongs on the page rather than in the key.

For anything open-ended, the key states what makes an answer acceptable rather than pretending there is one answer. A parent needs that more than the child does.

Print is a constraint, not a format

Material that will be printed or sold as a file has limits that a screen mockup hides: margin loss on a home printer, greyscale rendering of a color-coded task, and the fact that nobody can zoom.

Design in black and white first and add color as reinforcement rather than as the carrier of meaning. A task that requires distinguishing red from green fails in greyscale and fails for the significant minority of readers who cannot make that distinction anyway.

marketing:visual-content covers the design craft; what is specific here is that the constraint is a child's hand, a home printer and no adult present.

Tooling

Layout for print material is a document problem before it is a design one. InDesign, Affinity Publisher, Canva and similar all produce a usable page; what determines whether a hundred-page workbook stays maintainable is whether the layout is driven by styles and templates rather than placed by hand, because the correction always arrives after page sixty.

Generated material — the same task shape across many values — is worth scripting rather than copying. A script that emits items from a parameter set makes the difficulty sequence explicit and regenerable, and it is the only way a mistake in item construction gets fixed once rather than eighty times.

For anything sold, keep the source and the output separate and treat the PDF as a build artifact. The alternative is a product nobody can correct.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

  • Write an instruction that reads above the level of the skill being practiced.
  • Introduce a new skill and a new answer format on the same page.
  • Build the answer key from what you intended rather than from what the page says.
  • Carry meaning in color alone.
  • Ship a difficulty sequence nobody walked through from the student's side.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0282026年9月18日 更新

Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0282026年9月18日 更新

Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0282026年9月18日 更新

Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0282026年9月18日 更新

Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0282026年9月18日 更新

Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0282026年9月18日 更新

cbrock84 のスキルをすべて見る

このスキルの問題を報告する