An agent needs context to do good work.Most of it was never written down.

## Decision

We chose **terminal-rendered markdown**: monospace throughout, box-drawing characters for rules and tables, **markdown syntax present but recessive** rather than hidden, colour used only as signal, and hierarchy from case, weight and colour rather than from size. The palette is inherited entire from the existing system, both modes, unchanged.

The reason, in the owner's words on 2026-08-19 and deliberately not paraphrased:

> *"this direction feels more skill styles and markdown styles and which represent all the context or how all files stores also"*

## What we gave up

*(none identified)* — the trade was never articulated. Mechanically, a third family is a third webfont on a page whose stated virtue is restraint, and the two-family drafts demonstrably worked without it; but **no one recorded weighing that**, and it is not this record's job to supply the reasoning after the fact.

## What would make us revisit

*(not stated)*

## Decision

We split site content **by kind**, and say so. `website/components/lib/skills.ts` holds everything repeated or counted: the skill catalogue and its groups, every install command, the nine matrix rows, the hero specimens, the loop steps and the repo URLs. **Every count is derived from that data, never written** — `TOTAL_SKILLS`, `spellCount()` and `TOTAL_SKILLS_WORD` exist so that no sentence on the page, and no line of metadata, states a number a human typed. Section prose — headings, ledes and body paragraphs — lives in the component that renders it.

# 0000. Not logged

Candidates the decision log deliberately does **not** contain — so a re-run doesn't propose them again, forever.

**This is a ledger, not a decision.** Unlike its numbered siblings it is *hand-editable*: delete a row to make a candidate eligible again, or run `/decisions-logger reconsider` to re-open everything here for one run.

 website/components/Specimens.module.css      | 203 ------------------
 website/components/Specimens.tsx             | 222 -------------------
 website/components/lib/skills.ts             | 305 ++++++++-------------------
 website/package.json                         |   4 +-
 29 files changed, 915 insertions(+), 2291 deletions(-)
```

---

_Generated by `/changelog-tracker` from `git log -1` and `git show --stat`. Every fact here comes from git: **faithful, not generative.**_

## Corrections to the commit message

Four sentences in the message above do not survive a check against the diff. The message is in the git log permanently and cannot be edited, so the corrections are recorded here instead. Everything else in it was verified and holds.

**1. "Both shadow values are alpha of `--ink`" — true in light mode, false in dark.**

## Open Questions
Reconciled against the 2026-07-12 brief: - **[CLOSED] Slug-in-filename bug** — fixed in `8b02a1b` ("Fix: include slug in handoff filename"); Step 6A now uses `...-{date}-{slug}.md`. - **[CLOSED] Commit `bf31614` (README intro)** — merged to the default branch via PR #2. - **[STILL OPEN] Repo is private** — must be flipped public before anyone else can `/plugin marketplace add vidhunnan/agentic-skills`. - **[STILL OPEN] GitHub About description + topics** — drafted in the prior brief, not yet applied. - **[STILL OPEN] v2 ideas parked in the PRD** — auto-fire on chat wind-down, Cursor `.mdc` counterpart, multi-file handoffs, chaining across multiple prior handoffs.

### What we learned

The direction read as *"more decorative and interactive than the minimal, airy look the owner asked for"* — recorded in [ADR 0017](../../decisions/0017-the-website-design-direction-is-swiss-whitepaper.md).

### Verdict

**Killed** — with the Blueprint direction. Whether the typeface pairing was *independently* rejected, or simply went down with the direction it belonged to, is *(not recorded)*.

## Anti-goals

*What would count as failure even if it tested well:*

- **The records read as a design gimmick.** If the gaps and the redline look like a device invented for the layout rather than real artifacts from a real repo, the argument inverts — their entire value is that they are not decoration. - **Beautiful, and still can't say what this is.** Someone lands, admires it, leaves, and could not describe the library to a colleague. This is the current failure and the criterion above exists to catch it.

## Vocabulary

**The noun this runs on:** **context.** The UI, the README and the copy all use it and do not drift to synonyms.

**Out of bounds:**
- **"context engineering"** — the discipline label, as opposed to the plain noun. The closed positioning brief already suspected it loses the reader in the first sentence; the audience is now anyone building with Claude seriously, not engineers.