Taste

The judgements Frank has already given, so nobody spends his time making them twice. Read before producing. Add a judgement the moment he gives one, in his own words, with the date.

A judgement goes in only when he has reacted to something real he could see. Nothing here comes from a discussion.

How a page should look

12-08-2026

Three options means three different ideas

i have 3 times the same UI, it is clear that no inspiration was looked at in the studio

Apply it as: if the three candidates share a skeleton, a type scale or a colour behaviour, they are one option. Hunt further before showing anything.

12-08-2026

Taste is not produced by specifications

The second attempt gave the agents measurable targets: largest type at least five times body size, colour over a third of the first screen, no more than twenty-five words on the first screen.

stop, it is very ugly

Apply it as: numbers may check a design after the eye has approved it. They can never generate one. Choose a real model and copy it faithfully instead.

12-08-2026

The house rules were making everything identical

Six rules, all correct for a document read calmly, all fatal to a page meant to impress: grayscale first with colour as a scarce accent · the 66 to 72 character reading measure · the token ladder's snap-never-invent · hierarchy by de-emphasis · the shared block vocabulary · the two audits run as a delivery gate.

Apply it as: mode pièce suspends all six, as set out in the README. Do not run token-audit.py or composition-audit.js on a pièce.

12-08-2026

The skeleton he recognises instantly

sticky nav meta line, date and links h1 grey dek hairline cards, 10px round one centred container, 1100 to 1300
Measured across three options that were meant to differ: 1280, 1280, 1180.

Apply it as: in a pièce, none of these may appear. Structure comes from the reference, never from our last page.

12-08-2026

Never dark, whatever the reference does

no dark themes

Apply it as: copy a dark reference's scale, rhythm, confidence and colour behaviour. Never its darkness, in any section, band, tile or footer.

Still to be filled. The most useful entry this record can get is a page Frank finds beautiful. Ask him for one, capture it, and write down what he liked. Until that exists, every judgement here is about what he does not want, and taste built only from refusals stays timid.

Source of record: taste.md.

How a speaker, a voice and a film should look

Twenty-two judgements are recorded for this stream. The ones below are about what he sees and hears; the rest set the production line and live in the full record.

31-07-2026

Show, do not label

A card carrying an abstract label conveys nothing. Every concept on a page carries a real example image, so he can judge on sight whether it is what he wants. A named site gets its thumbnail and one plain line.

whatever doesn't convey any clear meaning should be eliminated

31-07-2026

No unexplained jargon

I have no idea what GSAP is, so either you explain if it is worth it, or you don't mention

A term is worth one plain line, or it does not appear.

31-07-2026

Everything he reads here is a page, not a file

I see that you still write documents in md for the UI/UX document. They all should be in HTML

Markdown stays as the source behind the view; every index and back-link points at the page.

02-08-2026

The word is speaker, and the sizes are settled

The person on a page is a speaker. Its forms are sizes: face, to the bottom of the neck · half bust, head and shoulders · bust, to the chest · full body, to the feet. A still picture is not a size; it is the separate option before the speaker.

Is it a talking bust or a speaker? If it is a speaker, just say speaker.
I don't know what rungs is.

02-08-2026

An illustration shows one thing only

You make people think that you have two buttons… this is not the case. Don't mix the problems.

No unrelated button, control or badge in the frame, and never a control that no longer exists on the live page.

02-08-2026

A studio page is a cookbook

This is a practical manual, not a report nor a manifest… our model is a cook book, should be all very concrete.

Titles name dishes, sections are recipes, and no words about ourselves.

05-08-2026

A capability anyone can use needs a door on the front page

I don't see prominently in the studio index page either 'make your own speaker'. It should be linked to the homepage. People should see it.

A top-menu link is not visibility. A card on the front door is.

05-08-2026

A section is a door, not a container

When a capability has several routes, the front page of the section is the choice itself: a question, then one card per route, each opening its own page, with everything common left behind on the front page, once. The choice must be visually big: a table of rows reads as reference, three large cards read as a decision.

We should start from the current speaker page, and then you have the three choices.

The full record, including the production judgements: the motion criteria · source criteria.md.

The nine rules a page passes before he sees it

Agreed 06-08-2026, drawn from his corrections on the eR school pages.

  1. Baseline UX is assumed, never requested: the whole card is clickable, hover is visible, links work.
  2. Compact beats wide: cards a third of the page, not half, but real air between a title and its content.
  3. Numbers are almost never the message: small, grey, or absent. Nobody cares that there are 164 of something.
  4. Colour carries meaning, one hue per section family. Decoration carries nothing, so no separator line that adds nothing.
  5. One name per notion, once per page: no brand appearing twice, no two sections with near-same titles, sibling pages visible in the navigation, internal menus labelled as menus, meta information a whisper.
  6. Titles precise, not evocative: "Good UI/UX", never "What makes a good service".
  7. Missing content shown honestly: a tab saying "to be filled later" beats a hidden gap.
  8. The builder's eye is the linter, not Frank's: this list plus the five-second cover-the-text test run before any page opens in his browser.
  9. Look-choices come as three options rendered in the real page, one marked recommended.

Source of record: franks-baseline-ux.md.