synthetic

Heuristic

One design rule: a heading, a bold one-line rule, the reasoning, and optional code or a live example.

One primary actionRule, rationale, and a live checklist

One primary action

Give each screen one primary button.

Two filled buttons make the crew stop and choose. Keep the rest secondary or tertiary.

Save changes is filled

Cancel is outlined

Delete project is destructive and last

Rule only

Name the button for what it does.

“Save changes” beats “Submit”.

With code

Say what is lost before it goes.

Name the project and what goes with it.

<Button variant="destructive">Delete</Button>

Design principles pageHeuristics stacked, as on a guidelines page

Write “24 Oct”, not “2026-10-24”.

People read dates; machines get the ISO form in the markup.

Every task shows who has it.

An avatar and a first name answer “who do I ask?” without opening the task.

{ type: "heuristic", id: string, title: string, rule: string, rationale: ProseNode[], code?: string, exampleBlocks?: Block[] }