Claude and MCP Filled My Framer Knowledge Gaps and Saved Me Time
I Used Claude to Add Motion, Refine Interactions, and Fix Technical Issues in My Framer Portfolio
5 min read
I Figured Out My Portfolio Had Some Crazy Bugs & I Didn't Have Much Time
| Context |
From my previous experience with MCP, I knew I could refine my Framer portfolio through some back-and-forth prompting. This time, speed mattered: recruiters could review it at any moment, and I had several changes to make quickly.
Polishing My Portfolio Started With Fixing Dead Links
| Design Problem |
One morning, right after I woke up, I saw a message from someone reviewing my portfolio: “It looks great, but I can’t open your case studies. They aren’t clickable.”
I froze. Oh my God, not again! I had fixed this bug only a week earlier. Even worse, I had applied for five jobs in the previous three days, and recruiters could check my portfolio at any moment.
I needed a quick fix, but I wasn’t fluent enough in Framer to find it myself. Then Claude came to mind.
I started Talking to Claude Through MCP
| Design Process |
The prompt started from my root & cause approach:
Through the MCP plugin, I explained the problem, what I expected to happen, and how the cards should behave across different breakpoints. After some back-and-forth, I figured out the problem and resolved it.
Checking Every Card and Button, One by One
| Test & Iteration |
I fixed the dead links and also made cards clickable again.
Learning From This Iteration Process
The whole back-and-forth, which took about 2 hours, taught me that the while using MCP, I should always check with eagle eyes after publishing every change I make. And that checking should have a user story behind it.
I should go through the journey like a user and never forget to check both desktop and mobile! Actually, I should take the role of a QA here!
Sometimes, the back-and-forth of applying a change and then debugging the after-effects of that change can be exhausting and stressful! But so far, this has been part of my experience working with MCP.
With every change, I almost hold my breath, hoping MCP hasn’t broken something that was already working. 😅 And then I need to stay persistent, check again, find the bugs, and fix them.
But I think this is it! Taking on the QA role while working with MCP is super super important.
Want to Contact?
I’d be happy to meet for a coffee or have a chat online.
+31-6 86 483 176
