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

early-childhood-practice

Judges whether material for children under six is developmentally plausible — what is typical at each age, why pre-K is not a thinner kindergarten, and which frameworks apply where Common Core does not. Use this to design or review pre-K material, decide whether a task is reasonable for an age, choose the right framework for a pre-K alignment claim, or push back on material that pushes school-age expectations downward.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md5.1 KB
  • references/sources.md1.9 KB

SKILL.md(原文)

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

Early childhood practice

Pre-K is not grade zero. Material for three- to five-year-olds fails most often by being a smaller version of kindergarten work — the same task, fewer items, larger print — which is a different mistake from being too hard.

There is no Common Core below kindergarten

This is the first thing to establish, because the alignment claim printed on most pre-K material is either wrong or vague.

What does apply:

  • State early learning standards, which exist in every state and vary substantially in structure and in what they expect at each age.
  • The Head Start Early Learning Outcomes Framework, which covers birth to five across approaches to learning, social-emotional, language and literacy, cognition, and perceptual and physical development. It is a federal work and freely usable.
  • NAEYC's position on developmentally appropriate practice, which is not a standards document at all — it is a statement of what practice should look like, and is the thing most often cited when a task is challenged.

A claim of "Common Core aligned" on pre-K material is not defensible. education:standards-alignment covers alignment above kindergarten.

Developmentally appropriate is a range, not a line

The useful question is not whether a four-year-old can do a task. Some can. It is whether a typical four-year-old can do it without the experience becoming one of failing.

Ranges worth holding, with the caveat that variation at these ages is wide and normal:

  • Fine motor. Tripod grasp is still consolidating at four. Tracing within narrow lines, small-square handwriting and precision cutting are ahead of most of them, and repeated failure at a motor task teaches avoidance of the subject it was attached to.
  • Attention. Sustained focus on an adult-directed task runs in single-digit minutes. A page that takes twenty minutes is not one task, it is four, and it should be designed as four.
  • Counting and cardinality. Reciting number names comes well before understanding that the last number said is how many there are. Material that assumes the second because the first is fluent misreads the child.
  • Letters. Recognition, naming, sound and formation are four separate skills that develop at different rates. Name-writing typically precedes general letter formation, because the motivation is different.
  • Symbolic reasoning. A picture standing for a thing is not automatic at three and is usually secure by five. Worksheets depend on it entirely.

Play is the method, which constrains the format

The consensus position across the early childhood field is that young children learn through play, exploration and interaction — not that play is a reward after the work.

This is uncomfortable for anyone producing worksheets, and the honest conclusion is that the worksheet is a supporting format at this age, not the primary one. Material that acknowledges this is better material: a page that prompts an activity, a conversation or a hunt around the room does more than the same page asking for tracing, and it is what a knowledgeable reviewer looks for.

Where a page is the deliverable, the ones that work at this age tend to be open rather than closed — draw, sort, match, find — with no single correct answer to get wrong.

Pushdown is the failure mode to name

Academic expectations have migrated downward, so kindergarten now carries work that was first grade a generation ago, and pre-K material follows. The pressure is commercial: parents buy what looks rigorous, and "gets them ready" sells.

Being explicit about this is part of doing the work honestly. A pre-K page asking for sentence writing is not ambitious, it is misaimed, and the child who cannot do it concludes something about themselves rather than about the page. When a buyer asks for material a year ahead, that is a real request and it deserves a straight answer about what it will cost the child.

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

  • Claim Common Core alignment for material below kindergarten.
  • Treat a pre-K task as a kindergarten task with fewer items.
  • Require fine-motor precision the age has not typically reached.
  • Design a single page that needs more sustained attention than the age sustains.
  • Present a worksheet as the primary way a three-year-old should be learning.

レビュー

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

同じリポジトリのスキル

概要と使いどころ

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,0372026年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,0372026年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,0372026年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,0372026年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,0372026年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,0372026年9月18日 更新

cbrock84 のスキルをすべて見る

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