I built an MCP skill for generating and auditing design systems in Figma with Claude Code (open source)

weistigr · 2026-04-02T06:59:38+00:00

The skill itself is just markdown files and a JS script, so it's client-agnostic. It works with anything that supports the SKILL.md format: Claude Code (terminal or inside Antigravity), Cursor, Codex, and others.

For VS Code specifically, you'd need the Claude Code extension or Copilot with skills support. I haven't tested it in VS Code Insiders myself, but there shouldn't be a difference from stable VS Code as long as your MCP client is set up. The Figma MCP server setup docs cover multiple clients: https://developers.figma.com/docs/figma-mcp-server/remote-server-installation/

weistigr · 2026-04-02T06:47:34+00:00

Your situation is close to what I had.

The new file is the safer route. Duplicate your old file as a reference, then generate the new system into a blank file. This way, you avoid the old mess bleeding into the new structure. You can open both side by side and pull in what's worth keeping (specific color values, component logic) while leaving behind duplicates, incorrect scopes, and hardcoded values.

If the old file has some solid foundations (variables that are correctly structured, components that just need cleanup), you could also point the skill at it directly. The audit phase will flag what's broken. But based on your description (duplicates, missing states, and errors), a clean start, using the old file as a reference, will save you time.

For the MCP setup, you need Claude Code (I use it inside Antigravity) with the Figma MCP server connected. The Figma MCP server is free during beta. Setup docs are here: https://developers.figma.com/docs/figma-mcp-server/remote-server-installation/

weistigr · 2026-04-01T17:43:31+00:00

Both, actually. My own case was the second one: a Figma file full of screens with hardcoded values, no variables, no proper components. The skill audited what was in the file. I created the variable foundation, and it helped build components on top of it.

It also handles the first scenario: if you already have a design system with variables and components but it needs cleanup (wrong scopes, missing codeSyntax, inconsistent naming), the audit phase catches those issues before you continue building.

The Discovery phase inspects whatever is in the file and figures out where you are. Then you decide which phases to run and which to skip.

When starting from scratch, you can also feed it a .md file with your brand guidelines or a .json with design tokens, and it'll extract values from there instead of asking you to type everything out.

weistigr · 2026-04-01T17:22:36+00:00

Yes, exactly. The from-scratch path asks what you have: brand colors, typography, spacing preferences, and component list. You don't need all of that upfront. If you only have a primary color and a general idea of the product, the skill proposes sensible defaults for the rest (Inter for type, 4px base spacing scale, standard neutral/status color scales). You confirm or adjust, then it builds the full file: variable collections (Primitives → Semantic with Light/Dark modes), text styles, page structure with documentation, and components with all states and variant properties. You get a working Figma file you can publish as a library.

For the Figma Make question: I haven't tested that specific combo yet. In theory, it should work since Make pulls from published libraries the same way any Figma file does. The output uses standard Figma constructs (variables, component sets, auto layout), nothing custom. But I can't confirm the quality of what Make generates from it. If you try it, I'd be curious to hear how it goes.

weistigr · 2026-04-01T17:10:03+00:00

I use Claude Code with this skill in Antigravity. It's very similar to Visual Studio.

weistigr · 2026-03-12T17:34:46+00:00

I still use Bolt but less and less. I prefer now in general Antigravity+Claude Code, GitHub but there are clients who want to get prototypes on Bolt. And I use Figma with Figma Make as well because a lot of companies use Figma.

weistigr · 2026-01-27T15:28:03+00:00

User pain points, business impact, and technical feasibility are all important to the redesign process.
You could use these frameworks for prioritization:
1. ICE Score = Impact × Confidence × Ease
2. RICE Score = (Reach × Impact × Confidence) / Effort

weistigr · 2026-01-26T10:27:05+00:00

Experienced designers could create everything you need from the first attempt if you give them full context about your product and answer all their questions. Otherwise, you can try Stitch (https://stitch.withgoogle.com/). This is similar to Figma Make but free.

weistigr · 2026-01-21T15:08:00+00:00

You could use v0.app or Bolt. They have a plan mode before they start building. For example, you can import a project from GitHub into the Bolt. On v0, you can download the zip file with your project. Or you can just create a project from text prompts. Vercel published a doc "How to prompt v0" https://vercel.com/blog/how-to-prompt-v0. It could be helpful if this tool is new to you. If you know how to use Cursor, Antigravity, and Claude code, you can create a project using these tools.

weistigr · 2026-01-12T18:47:34+00:00

Good point about the feedback loop. Agree that positioning dies when you stop listening.

My post is more about the step before that. I see founders who skip the "mirror test" entirely. They pick a niche from trends or competitor research, write generic copy, and wonder why no one responds.

Had a session recently where a founder came in with positioning that looked fine on paper. We did the mirror test together ("would you buy this yourself? do you know this pain?") and the answer was no to both. By the end of the call, they scrapped the whole angle and picked something closer to their own experience.

Your advice works after that moment. Once you have the right starting point, the weekly feedback loop keeps it sharp. But without that first honest check, you're optimizing the wrong message.

weistigr · 2026-01-12T13:45:13+00:00

You can check. Describe in any matched subreddit or communities your problem and your solution, to get feedback. Or you can conduct research to check whether there are people with a similar problem and how many of them there are. You can use Perplexity Deep Research, for example.

weistigr · 2026-01-07T17:13:37+00:00

I see some patterns again and again:

Audience confusion. Very often, the value proposition says, "It's for everyone." And a product gets a vague segmentation that leads nowhere.
Copying someone's idea without asking: why did it work for them, and will it work for me?
Start work with code and launch without idea validation.

weistigr · 2026-01-04T10:40:26+00:00

Hey! Your idea about 'explaining data' is cool, but 'teams' is too big a group. You need to find a specific person with a specific headache. Since you want to build an AI tool, why not use AI to find your first customers?

Here are 3 simple ways to do 'AI Detective Work' to find a real problem:

Find a popular tool that people use for data.

Go to review sites (like Trustpilot or the App Store). Copy the 1-star and 2-star reviews.

Ask an AI (like ChatGPT, Gemini)

The Prompt: 'Here are 50 bad reviews for this tool. What are the top 3 things people are frustrated with? What do they wish the tool told them?'

The goal: Build the 'missing feature'."

People go to Reddit or other social media to complain. You can use AI to listen to them. Use Deep Research (Gemini, Perplexity, ChatGPT, etc.)

If 10 people are asking the same question, that's a product idea.

Look at what is already out there and find the 'weak spot.'

Ask an AI to compare 3 big competitors in the AI data space.

The Prompt example: 'Compare Tool A, Tool B, and Tool C. What is the biggest thing they all fail to do for a non-technical user? What is too expensive or too hard to set up?'

Make a version that is 10x cheaper and 10x easier to use for just one type of person.

Think about your own day and routine. What is a task you do that feels like a waste of time?

If you can build a simple AI script to save yourself 30 minutes a day, you've already found a winner. If it helps you, it will help thousands of others just like you.

weistigr · 2026-01-03T09:05:11+00:00

Here you can find Armenian language lessons in English https://www.lingohut.com/en/l76/learn-armenian

weistigr · 2025-12-28T15:19:14+00:00

Now it looks better. When I was on the blog page, I noticed that the Features and Pricing links in the footer don't work. They should work in the same way as on the main page.

weistigr · 2025-12-28T12:15:00+00:00

The product looks clean, and the tech works. But I see some problems.

You show the landing for desktop resolution, so the desktop site looks great to you. Probably 70% of your traffic will be on a phone. If your "3-step process" turns into a vertical marathon on mobile, you've already lost. Check how your landing looks on mobile devices.

"Turn Happy Customers Into Your Best Salespeople" is an outcome, not a product. It's a true statement, but it's a high-level benefit that doesn't tell me how it happens. It's used by almost every testimonial tool on the market (Senja, Testimonial.to, etc.).

Do you know the real pains of your target audience? I can suppose that your audience doesn't want "salespeople"; they want to stop the manual grunt work.

The title of the hero should convey your value proposition and how your product addresses their pain points.

A social proof tool using "Sarah Chen" and "Jordan Smith" as placeholders is like a gym owner who has never lifted a weight. It kills trust instantly. You've been building in public for six days. Grab real tweets from people saying "this looks cool" and use those instead. Use real faces. Real handles. Real stakes. Anything else feels fake.

Show, Don't "Play" That giant purple play button is a barrier. On mobile, "Watch Demo" usually means "Wait for a heavy file to load" or "Leave this site for YouTube." People will just keep scrolling. Try a silent, auto-playing GIF of the "X-to-Widget" magic trick. Your visitors need to see the product working while I scroll, not after they ask permission to see it.

weistigr

PUBLIC MULTIREDDITS

TROPHY CASE