Once a designer can summon a screen from a prompt, the danger is not that they will fail to produce. The danger is that they will produce everything that can be produced, and call that progress.
This note is the other half of they told you to code. Taste without refusal is only preference. Direction is a list of things that will not exist, written while you still have nerve.
Infinite generation makes weak taste harder to hide. Too many options is a coward's shelter. Both of those already sit in this body of work. Here they become a studio rule for people who were pushed toward code and still do not love it.
Observation first, then a no
Before you open an editor, watch one real use. A receptionist on a bad laptop. A founder forwarding a PDF because the tool is too proud. A guest who cannot find the door. Write what you saw in Morning Pages, not in a ticket.
If you cannot name the friction in a sentence a stranger would recognize, you are not ready to build. You are ready to decorate a fear.
Opinion is the sentence after observation: this should exist as X, and not as Y. Direction is the calendar: this week we build X, and we will not touch Y even if the model offers it for free.
Designers already know this in layout. Cropping is a no. Hierarchy is a no. A quiet secondary button is a no wearing a smaller type size. Code is the same crop, with a higher chance of shame if you refuse a feature someone else would have shipped.
A practical refuse-list
Use this as a wall, not as purity.
Do not build a platform. A platform is what you call a sketch when you are afraid it is small. One generator with three controls is a form. A platform is a career postponement.
Do not build login in week one. Identity is a swamp. If the work needs a person, use a link, a local file, a printed code. Authentication is other people's appetite.
Do not rebuild Figma, Notion, or Linear. You will lose, and you will train yourself to hate making. Clone work is how people who dislike code prove they were right to dislike it.
Do not add AI because the category expects AI. If the observation was "the button is in the wrong place," a model will not forgive the composition. AI gets better inside a product loop, not as a sticker.
Do not keep a backlog of unshaped moods. Shape Up's betting table exists so ideas die in public. Write three pitches. Bet one. Let the rest go cold. See appetite, not estimates.
Do not automate a judgment you have not practiced by hand. Testing as theater, analytics as morality, agents as staff: all of these skip the sitting. UX and testing are seeing methods. Sit first.
What to build instead
Build the smallest repeating unit of the observation.
If the observation was a poster that cannot vary, build a loop and three sliders. If it was a room that cannot be read, build a diagram that a stranger can walk. If it was a checkout that lies, build one honest state: empty, error, done.
That is clear form you can use and feel. It is also enough code. Anything past that should have to win a new appetite.
Node graphs help here because sprawl is visible. When the patch looks like spaghetti, you are looking at a personality problem, not a library problem. Clean the drawing. Node graphs are already programs.
Direction is a date with yourself
Cameron's Artist Date is assigned play. Give refusal the same appointment. Once a week, alone, list what you will not build for the next cycle. Put it next to the Morning Pages. If the list is empty, you are still hiding in options.
The Censor will say you are not technical enough to refuse. Ignore it. The people who cannot refuse are the ones drowning in generated UI. Your dislike of code can be a compass if you let it point at formlessness, not at yourself.
How you know the no was right
A week later, the thing you did build can be used without a tour. The thing you refused does not haunt you. You can still describe the observation in one sentence. You are not performing a stack on LinkedIn.
If the no was fear, it will itch. Then you reshape, not binge. Circuit breaker, then a smaller pitch. That is direction, not delay.
They told you to code so you would stop blocking engineers. The adult version is: you block the wrong product before it wastes a cycle. That is the job. Syntax was never the job.