Memorisely
Design Engineering

Your first pull request as a designer

Shipping a real UI fix to production, step by step.

Zander Whitehurst

7 min read

Your first pull request is a strange milestone. It is usually a tiny change, often just a few lines, and yet it feels enormous. For the first time, something you did is going to end up in front of real people, through the same process every engineer on your team uses.

This is a step by step walk through of shipping one small UI fix, from finding the bug to seeing it live. I have taken a lot of designers through this exact process, and the most common reaction at the end is "wait, is that it?"

Pick a tiny, visual fix

Your first PR should be boring on purpose. You want a change that is easy to see, easy to review and very unlikely to break anything. Good candidates include:

  • A typo or awkward piece of copy
  • An icon that is slightly misaligned
  • Inconsistent padding on a card
  • A missing hover state on a link

Avoid anything involving data, logic or forms for now. Save those for your fifth or sixth PR, once the process feels familiar.

Small visual fixes are easy to see, easy to review and very unlikely to break anything.

Talk to an engineer first

Before you touch anything, tell an engineer on your team what you are planning. Ask if there is anything you should know, like how the project is run locally or whether there is a naming convention for branches.

This does two things. It saves you from surprises, and it means someone is expecting your PR and is ready to review it kindly. Every engineer I have asked has been happy to help, and one of them now refers to me as "the padding guy", which I have decided to take as a compliment.

Get the project running on a branch

Clone the repository and get it running on your machine. Your team will usually have instructions in the README.md file. If not, ask your AI coding tool:

"Read this project and tell me how to run it locally."

Then pull the latest changes so you are working from the newest version:

git checkout main
git pull

Never work directly on main. Create a branch with a name that describes the fix:

git checkout -b fix-card-padding

You are now working in your own safe copy. Nothing you do here affects anyone else until you choose to share it.

Make the change

Open the project with Claude Code or Cursor and describe the fix precisely:

"On the pricing page, the cards have 20px padding but the rest of the site uses 24px. Update the pricing cards to use the same padding as the other cards. Do not change anything else."

That last sentence matters. AI tools sometimes like to tidy up things you did not ask for, and a small, focused change is far easier to review.

Check it in the browser

Open the page in your browser and check your fix. Then check around it. Look at the page on a phone sized screen. Look at other pages that use the same component. Make sure you fixed one thing and broke nothing.

Take a before and after screenshot while you are there. You will need them in a moment.

Review the diff yourself

Before anyone else sees your change, look at it yourself:

git diff

You should see only the lines you expected to change. If there are extra files or changes you did not ask for, ask your AI tool to undo them. Reviewing your own diff first is a habit good engineers have, and it makes a strong first impression.

A clean diff shows one changed line and nothing else, which makes review quick.

Commit and push

Save your change with a clear message and upload your branch:

git add .
git commit -m "Match pricing card padding to other cards"
git push -u origin fix-card-padding

The terminal will usually give you a link to open a pull request. Click it.

Write a helpful pull request

Your PR description does not need to be long. It needs to be clear:

  • What changed. One sentence describing the fix.
  • Why. One sentence on the reason, such as consistency with the rest of the site.
  • Screenshots. Before and after, side by side.

Engineers genuinely love screenshots in PRs. It means they can review the visual change in seconds rather than running the project themselves.

Three short parts, what, why and screenshots, are all a good first PR description needs.

Respond to feedback

Your reviewer may ask for changes. This is completely normal and not a sign you did anything wrong. Make the changes on the same branch, commit and push again, and the PR updates automatically.

Once it is approved, your reviewer or you will merge it. Depending on your team's setup, it might be live within minutes. I refreshed the production site about forty times after my first one, just to make sure it was really there.

Start with one fix this week

Find one tiny visual bug in your product today. Tell an engineer, create a branch, make the fix, check it in the browser and open a pull request with screenshots. The first one is the hardest. After that, it is just how you work. Our AI Design Engineering Bootcamp takes you from first PR to shipping whole features.

Keep reading

View all
View all

Optimize your AI for better experiences, not AI slop.

View all

AI Prototyping Skills

Prototype with AI using clean UI patterns and guardrails so flows feel product-grade, not generic template slop.

$99

AI UI Motion Skills

Motion and micro-interaction patterns that make AI-built UI feel designed, polished, and trustworthy in real products.

$99

Fix AI Slop Skills

Spot AI slop early and fix type, spacing, and components so your product looks intentional, not like a template.

$99

AI Responsive Design Skills

Responsive layout patterns for rails, sidebars, and breakpoints so AI-generated UI adapts cleanly from narrow to wide.

$99

AI Dark Mode Skills

Dark theme tokens, contrast, and surfaces that keep AI-generated UI readable and product-grade, not flat gray on black.

$99

AI Color Token Skills

Neutral and primary ramps with clear steps so AI palettes stay systematic, not a random set of accent hex codes.

$99
View all