The first skills a design builder should learn

By Imran Sheikh · 2026-11-12 · Design builders · 4 min read

Key points

  • Learn to read code before you try to write it.
  • Git makes experiments safe and mistakes cheap.
  • Taste is the bottleneck, so train it on purpose.

Designers who want to build ask me where to start. They expect a list of languages and frameworks. I give them a different list. Four skills carry most of the weight, and none of them is a programming language.

The four are reading code, using git, prompting agents and training taste. Learn them in that order and you can ship real changes within weeks. Skip one and you will feel the gap quickly.

Skill one: read code

Reading comes before writing. An agent can write plenty of code for you. It cannot tell you whether the code is right for your product. You need enough literacy to look at a change and say yes or no.

You do not need to read everything. Learn to find your way around. Where do screens live. Where are the shared components. How are colors and spacing defined. What does a function name tell you about what it does.

  • Open a component and find its props, its state and its markup.
  • Trace one value from where it is set to where it is shown.
  • Find the design tokens and see how they are used.
  • Read a diff line by line and say what each change does.

Ask an agent to explain what you are reading. Then check its answer against the code. Over time you will catch the places where it gets things wrong. That is when you are really reading.

Skill two: use git

Git is the safety net that makes everything else possible. Branches let you try a bold idea without risk. Commits let you step back. Pull requests let other people see what you did before it lands.

Learn a small set of commands and use them daily. Make a branch. Look at what changed. Commit with a clear message. Push. Open a pull request. Pull the latest changes. That covers most days.

The habit that pays off most is committing often. Agents can change a lot of files in one pass. If something goes wrong, a recent commit is your way back. Commit before every big request and you will never be stuck.

Writing good commit messages and pull request descriptions is also design work. You are explaining a decision to the next person. Say what changed and why. Keep it short.

Skill three: prompt agents well

Prompting an agent resembles briefing a talented new teammate who knows nothing about your product. Give context. Point at the files that matter. State the outcome you want and the limits you need respected.

Good prompts name the existing pattern. Use the Button component in this folder. Follow the spacing tokens. Match how the settings screen handles errors. The agent works best when it has something real to imitate.

  • State the goal in one sentence.
  • Name the files or components to use.
  • List the constraints, such as tokens, accessibility and device sizes.
  • Ask for a small change, then review it before asking for the next.
  • Tell it what to leave alone.

Keep a notes file in the repo with your conventions. Agents read it at the start of a session. It turns your taste and your rules into something the tool can follow. When the agent makes a mistake twice, add a line to the file.

Skill four: taste, the real bottleneck

Once building is fast, the limiting factor is judgment. Can you tell a good screen from an acceptable one. Can you spot the small wrongness in an animation. Can you say what a screen is missing. That is taste, and it is the part no agent supplies for you.

Taste is trainable. It grows from looking at a lot of good work and asking why it works. It grows from making things and comparing them side by side. It grows from critique, both given and received.

  • Collect work you admire and write down what makes it good.
  • Compare two versions of every screen before you settle.
  • Play or use the best products in your category every week.
  • Ask a trusted person to tell you what feels off.
  • Practice cutting. Remove one thing from every screen and see if it improves.
Agents widen what you can make. Taste decides what you should.

A simple order of practice

Spend your first two weeks reading. Open a real codebase and explain it to yourself. Spend the next week on git until the commands feel boring. Then start making small changes with an agent, and review every one.

Taste runs underneath all of it. Treat every change as a chance to judge the result honestly. If the screen is only fine, say so, and make another pass.

Track your progress with a simple habit. At the end of each week, write down one thing you read, one git problem you solved, one prompt that worked and one screen you improved by cutting something. Four lines are enough. After a month you will have a record of real growth, and you will see which skill needs more attention.

What to skip at first

You can leave deep framework knowledge for later. You can leave build tooling and deployment pipelines to the engineers. You will pick up what you need as you go. The goal is to be useful in a real repo quickly. Becoming a full stack developer is a different goal, and you can skip it.

We run the studio on this idea. Designers work in the client’s codebase from day one, with engineers close by. The learning happens in the work, and the work ships.

Journal · Book a call · Home