Your Figma as a Portable AI Skill

In 2026, your team probably uses Claude Design for prototypes, Cursor for implementation, v0 for landing pages, Google Stitch for rapid UI concepts, maybe Codex for automation. Each tool has its own way to "set up your brand":

• Cursor wants .cursorrules

• v0 reads shadcn configs

• Codex reads CLAUDE.md

• Google Stitch / AI Studio reads design.md

• Claude Design has its own setup flow

You've uploaded your brand four times. They've each drifted in a different direction. Your design lead is in pain.

Meanwhile, there's one format every agentic AI tool can read: SKILL.md — Anthropic's open skills spec (90K⭐ on GitHub). Any agent that supports skills reads it natively. We output this as the primary artifact; all the tool-specific formats above are just wrappers around the same DNA.

There's a better way.

§1. The actual problem

Every AI tool in 2026 wants your brand. Each one reinvented the input format:

If you set up your brand inside each tool, you maintain 3-5 versions. Designer updates Figma → you manually update 3-5 tool configs. Every week. Forever.

This is the "vendor setup drift" problem. Nobody talks about it because it's only painful after you've committed to multiple tools.

§2. The fix: one skill, many tools

Instead of uploading to each tool separately, do this once:

You now have a public GitHub repo containing your design system, written in Anthropic's open SKILL.md format (90K⭐). This repo is:

• Portable — any AI tool that reads GitHub URLs can consume it

• Versionable — standard git workflow, your designer can re-run when Figma updates

• Ownable — the repo is yours, not locked in any vendor

• Open-spec — SKILL.md isn't proprietary. When the next AI tool launches, it'll read your repo too.

How each tool consumes it (today)

• Claude Design → paste repo URL into Link code on GitHub

• Cursor → clone the repo, .cursorrules file inside is read automatically

• Codex / Claude Code → npx skills --install your-name/your-skill

• v0 → point to the shadcn-compatible export (we output this too)

• Google Stitch / AI Studio → reference the design.md variant in your repo (we output this too)

• Any agent / future tool → fetch SKILL.md from the raw GitHub URL

One brand. Many tools. No drift.

§3. What designskills.xyz actually does

You could write a good SKILL.md by hand. It's not hard if you've read the spec. Maybe 2-4 hours per brand, if you know what you're doing.

Or paste a Figma URL, wait 30 seconds, click publish. That's what designskills.xyz does.

The 1,118 lines of extraction heuristics matter less than the time they save. HSL saturation classification, typography stack interpretation, component token relationships — all derived from your Figma file, written into a SKILL.md your AI tools can read cleanly.

You could absolutely build this yourself. It's an afternoon's work. I built this so I (and everyone else) didn't have to keep doing it.

§4. Who this is for — honesty section

If you only use one AI tool, this is overkill. Just use that tool's native brand setup and you're done.

If you use 2+ AI tools — or expect to in the next 6 months — having one portable repo saves real time and prevents drift.

If you're an agency with multiple client brands × multiple AI tools, this is a lifesaver. Each client gets their own repo. Version-controlled. Reusable.

§5. Try it

→ designskills.xyz

Free. No signup needed. One-click GitHub publish after you see the output.

If you try it and the conversion misses something specific about your brand, email me. This is still day-one territory for the Figma → SKILL.md heuristics and every brand helps sharpen them.

built in NYC. DMs / GitHub issues / email all open.