skills
patricknlewis/skills
Claude Code skills that bridge design tools and code — Figma extraction, design system mapping, and more.
Instalação
npx convez-ai patricknlewis/skills1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
README
A tradução para o português deste README ainda está na fila.
Patrick Lewis — Claude Skills
A small marketplace of Claude Code skills I use in my design and product work. Install any of them in two commands.
Install
In Claude Code, add the marketplace once:
/plugin marketplace add patricknlewis/skills
Then install the skill you want:
/plugin install extract-figma-design-md
That's it. Updates arrive automatically when I push new versions — or run /plugin marketplace update to refresh on demand.
Skills
extract-figma-design-md
Turns any Figma design system into a spec-compliant DESIGN.md — the plain-text, AI-readable source of truth for a design system. It pulls colors, typography, spacing, radii, and every component (with variants) out of Figma via the Figma MCP, interviews you about the decisions Figma can't export (brand voice, semantic color meaning, do's and don'ts, light/dark modes), and writes a clean DESIGN.md you can hand to any AI agent so its prototypes match your system.
Built so a non-designer can prototype against your design system and get output that actually looks right.
Requires: a connected Figma MCP server (remote mcp.figma.com or the Figma desktop app's Dev Mode MCP).
Run it by saying: "Make a DESIGN.md from my Figma file: " — or just mention design.md and paste a Figma link.
write-project-summary
Writes a portfolio project summary — the single-page writeup that documents one product, sitting between a quick blurb and a full case study (500–900 words). It has two modes: interview mode generates a short set of questions when the source material is thin (answer by voice memo, transcript, or text), and drafting mode writes the summary once the material exists. It enforces structure (opening, features, strategic decisions, learnings) and a fabrication guard so nothing — metrics, learnings, roles — gets invented from inference.
Built so the summary shows how a designer thinks, with the product as evidence, not a press release.
Run it by saying: "Write up [product] for my portfolio" — or "draft the [product] page" / "help me document this project."
critique-from-a-boring-designer
Gives a structured design critique the way a thoughtful senior designer would — not a generic heuristics audit. It runs a short intake (goal, stage, known-rough areas), then works deliberate passes (does it work → is it complete → does it say the right things → is it considered), gating which passes run by design stage so an exploration isn't critiqued like a shipping candidate. Notes name consequences over preferences, are tiered by severity, and capped to the few that matter. Built on Cap Watkins' The Boring Designer. Its one hard rule: it never proposes an alternative design — it names the problem and leaves the solving to you.
Run it by saying: "Critique this" / "review my design" — and share a screen, a flow, or a flow plus a reference screen.
Notes
- This repo is itself the marketplace; no install step beyond the two commands above.
- Skills install under your
~/.claude/directory and are namespaced (e.g.extract-figma-design-md:extract-figma-design-md) to avoid collisions.
License
MIT