2026-05-04 — Yesterday I Learned
Skills Are Routers,
Not Documents
A good skill doesn't explain what to do — it decides what enters context, at what cost, and when to earn its place. The words matter, but the structure decides everything.
Metadata is a routing decision, not a usage decision. If the description is wrong, nothing else matters.
A Skill Is a Budget Contract
for Working Memory
Specification
Skills are loader specifications
A way to describe what enters context, when, and at what cost. The skill is a routing contract, not an instruction document.
Routing
Metadata is a routing decision
If the description is wrong, nothing else matters. The metadata decides whether the skill enters context at all — get it right first.
Architecture
The kitchen at dinner service
Get the architecture right and the skill costs almost nothing until it earns its place. Get it wrong and you pay every turn.
Evaluation
Eval methodology: paired runs
Once with the skill, once without. The question is not "is it good?" but "is it better than baseline, and by how much?"
Search for Collisions
Before You Ship Tailwind
/* existing repo — pre-theme text flip */
.invert {
color : var(--color-text-inverted) ;
}
/* tailwind utility — CSS filter inversion */
.invert {
filter : invert(1) ;
}
/* result: both active → behaviors cancel → mysterious regression */
When bringing Tailwind into an existing codebase, audit for utility-name collisions —
especially generic words like
invert,
ring,
shadow,
hidden.
Practitioners Are Already Bringing
AI Into Design Systems
A YouTube conversation with Chris, Dave, Brad, and Ian surfaced how practitioners are already weaving AI into design-system work — not as a research topic but as something Brad and Ian are actively doing.
One emerging angle: using AI to help non-profit sites that are in rough condition reach a defensible baseline quickly. Sites that exist to serve communities but have fallen behind on maintenance — AI as a force-multiplier for civic good.
The conversation also touched on Chris and Dave's current thinking: the craft of knowing when AI accelerates versus when it flattens, and what it means to bring these tools into systems that other people depend on.
Design Systems
Chris, Dave, Brad & Ian — AI and Design Systems
How practitioners are integrating AI into design-system workflows, plus the civic angle: AI to help struggling non-profit sites reach a defensible baseline.
Watch on YouTube →
Unique Because of Content,
Not Because of Chrome
Agent-created skills can silently encode design constraints that masquerade as "uniqueness" — pre-baked layout widgets that exist because the skill said so, not because the content calls for them.
The discipline: always read agent-generated skill files; review for baked-in assumptions. YIL pages should feel different from each other because of what they teach, not because the build skill prescribed different chrome for each one.