The craft behind the queue

You hold the highest audit score in the queue. What did you actually do?

Focus order first, then colour. The contrast pass takes ten minutes and fixes the score more than any clever markup does.

Your challenge entry swapped a spinner for a skeleton. Why?

A spinner is a promise. The skeleton is the truth — the page is going to look like that in 400 ms, so show it.

What do you cut when a brief asks for more motion?

The second animation. There is almost always one that carries the meaning and one that carries the ego.

How do you keep loader bundles that small?

I write the CSS before the component. If the state can live in a data attribute, it never needs a hook.

Your flip loader was picked apart by the judges on honesty. Fair?

Completely fair. I faked measured progress because it looked better. The bar that admits it does not know is the better component.

Advice for a first submission?

Ship the boring version with clean gates. A 78 with no warnings teaches you more than a 95 you cannot explain.

You write prompts like requirement documents. Why?

Because the model reads constraints better than adjectives. ‘Hero, 62 chars, two CTAs, no video’ beats ‘stunning modern hero’.

What do you do when a model fails a section?

I do not rewrite the prompt blindly. I find which constraint it dropped, then say that constraint twice, differently.

One line for someone who thinks prompt writing is not real work?

Then neither is writing a brief for a contractor. Same job: make the constraint unmistakable.