MCP for designers
A plug that lets the AI see your actual tools. How I use it in Figma, GitHub and the browser.
Why a designer who does not code still uses it
I do not write code. Claude does. GitHub is how every change gets a save point, a safe branch to try it on, and a review before it ships.
I do not write code. Claude does, and I review it. What I do understand is git: a commit, a branch, a pull request. In Figma terms, a commit is a saved version, the same way Figma keeps every version you name in its history.
Claude edits fast and confidently, and it can be confidently wrong too. Without saved versions, checking its work would mean reading every line changed since the very start. With them, I look at one change at a time, and undo just that one if it is wrong.
A branch is like duplicating the whole page to try an idea: a copy of the project where you try something without touching what is live. This portfolio is the example I use every day: it lives on a branch called portfolio-v4, tried separately from an earlier portfolio-v3 and from main. I can judge a whole redesign side by side with what is actually published, with zero risk to the live site while I do it.
A pull request is sharing that branch for review before it merges back in, the same idea as sending a Figma file for comments before it goes to dev. A real one I have open right now: a bilingual website's Thai copy review, done with my own tool, Momo Copy Review. Every fix, 79 commits of them, sits in one pull request, waiting on the team. Nothing goes live until someone else looks, AI-written or not.
Two more plain words: Pages is free hosting for a small site, like turning a prototype link into something anyone can open. Momo Whisper's own site runs on it. Releases are downloadable versions, like exporting v1, v2, v3 of a file for people to grab.
My other small tools, PinPoint, UI Kit, Color Generator, Template Text Style, each get their own repo. A mistake in one never touches another, and I can undo any of them without thinking about the rest.
I do not feel bad that Claude writes the commits. My part is the habit around them: commit often, branch before trying something new, get a review before it ships.
Email me, or follow on LinkedIn where new notes land first. No newsletter, no pop-up, promise.