Design preference ledger

People repeat themselves when an agent keeps not listening. This skill makes repetition mechanical: every restatement raises the rank of a preference, until it stops being a suggestion and becomes a constraint.

The ledger lives at docs/frontend-preferences.md. It is a file in the repo, so it survives across sessions, works for any agent, and shows up in code review.

Read before you propose

Before proposing an approach, read the ledger. Hard rules are constraints. Contradicting a strong preference without acknowledging it is how you get told a third time.

Recognizing a preference

Record when someone expresses a durable choice between options: