September 2026

Every skill you write is a bet that the model cannot do something on its own, and that bet expires. The next one ships already knowing how to verify its own work and split its own tasks, and the patch you wrote for the last one now only makes it search more, detour more and burn tokens it did not need to burn. The more obedient the model, the more an old instruction costs you.

My own usage says it plainly. I have explored 141 skills. Out of 10,100 runs, four of them carry 4,500, about 45 percent, and all four are Waza's. Everything else I ever installed barely moves.

That is how I have kept Waza. Eight skills since April, none added since, and the part that sits in context permanently keeps getting smaller: those eight SKILL.md files were 164KB in mid July and are 128KB now, 22 percent off in two months. Duplicated gotchas went. Summaries that fought each other for routing went. Branches that almost never fired went. The detail moved into references that load only when the task needs them, so what you do not use never costs you anything, and not one skill can do less than before.

The last two changes I made follow the same rule. think has to beat the one-line brute force version on risk, rollback or latency before it may add a file, an abstraction or a config knob, because winning on elegance does not count. check has to say keep, adjust or replace about the approach before it is allowed to list a single patch.

A skill is worth what it lets the model do, not what it saves the model from doing. Install less, hold looser, keep the judgment with the model, and put the parts that must not move into code and tests.

github.com/tw93/Waza

Typography exists so people can read and understand. Not to look clever. Not for the big-company PPT vibe. Content comes first. If you bend a good idea just to fit a template, or pad empty slots with filler, you lose the real voice.

Keep type, tracking, leading, size, spacing, and radius calm enough that the page feels steady. Then ask the harder questions: who is reading, what must be said first, what is the core, what should they take away. Only then turn that into a clear page: where to start, what is important, what is secondary.

Same for charts and images. A chart that shows a pattern, or a picture that explains the point, beats a wall of text. A pretty asset that says nothing is noise.

My rule is Occam for layout: do not add a line, a box, or a fill unless it helps the reader understand something. If size, spacing, and alignment already carry the relationship, stop. Keep weight or color when they genuinely help reading. Minimal does not mean empty.

Recent Kami releases were mostly that kind of work. Side ticks next to titles are gone. Blue bars on callouts are gone. Soft shadows that did nothing are gone. Table rules got thinner and quieter. Spacing opened up. We also added lint checks so agents do not quietly put the clutter back.

I want Kami to handle those boring layout details, so you can spend the energy on what you actually mean. Good content deserves a good layout.