npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

designpull

v0.3.0

Published

Code in. Design out. Ship faster.

Readme

DesignPull CLI

npm version License: MIT Node.js Version CI

Code in. Design out. Ship faster.

DesignPull is a command-line tool that scaffolds design token files and writes them to Figma as live variables via Claude Code + Figma MCP Skills. Define your design system in markdown, sync to Figma, and generate production-ready components — all from your terminal.


What it does

  1. Scaffolds a complete design token system in a single markdown file (design-token.md)
  2. Writes tokens to Figma as variables (primitives, semantic tokens, typography) via Figma MCP Skills — no plugins, no manual copy-paste

Prerequisites

  • Node.js 20+nodejs.org
  • Claude Code CLInpm install -g @anthropic-ai/claude-code
  • Figma MCP Server — configured via Claude Code (see MCP Setup below)
  • Figma Personal Access Token — with file content (read) + edit access

Installation

npm install -g designpull

Or run locally:

git clone https://github.com/kuriouscreator/designpull
cd designpull
npm install
npm start

Quick Start

1. Initialize your design token file

designpull init

This generates:

  • design-token.md — your single source of truth for design tokens
  • .env — Figma credentials
  • .gitignore — ensures .env is not committed

Follow the interactive prompts to set up:

  • Project details (name, description, component library, styling approach)
  • Brand colors (primary, accent, secondary, dark, neutrals)
  • Typography (fonts)
  • Dark mode surface colors
  • Figma file URL and Personal Access Token

2. Sync tokens to Figma

designpull sync

This:

  • Parses design-token.md using a local deterministic parser
  • Creates 3 variable collections in Figma:
    • Primitives — raw values (colors, spacing, radii, etc.)
    • Semantic — intent-based aliases to primitives (Light/Dark modes)
    • Typography — type scale (Desktop/Mobile modes)
  • Writes all variables to your Figma file via Claude Code + figma-use skill

Requirements:

  • Figma MCP server configured in Claude Code
  • Valid FIGMA_ACCESS_TOKEN in .env
  • Edit access to the target Figma file

Options:

  • --dry-run — parse tokens and preview without writing to Figma

MCP Setup

DesignPull uses Claude Code to write variables to Figma via Figma MCP Skills (figma-use). You need to configure both:

Install Claude Code

npm install -g @anthropic-ai/claude-code

Set up Figma MCP Server

Follow Figma's official guide to configure the MCP server:

Figma Skills for MCP — Setup Guide

This enables the figma-use skill, which powers write-to-canvas. It can create frames, place components, set up variables, and arrange layouts directly in your Figma file.

Verify MCP is configured

claude mcp list

You should see figma (or similar) in the list.

(Optional) Add Chakra UI MCP

For better component generation hints:

claude mcp add chakra-ui -s user -- npx -y @chakra-ui/mcp@latest

Commands Reference

| Command | Description | Options | |---------|-------------|---------| | designpull init | Set up design-token.md and Figma connection | -o, --output <dir> | | designpull sync | Parse tokens and write to Figma variables | -o, --output <dir>, --dry-run | | designpull doctor | Check environment health (Node, Claude, MCP, credentials) | -o, --output <dir> |


design-token.md

This is your single source of truth. Edit it to change your design system, then run designpull sync to push updates to Figma.

Structure

  • Project — metadata (name, description, library, styling)
  • Primitive Tokens — raw values only (colors, spacing, radii, fonts, etc.)
  • Semantic Tokens — intent-based aliases to primitives (Light/Dark modes)
  • Typography Scale — font sizes, line heights, weights (Desktop/Mobile modes)
  • Component Token Map — which tokens each component uses

Token Architecture

Two-tier system:

  1. Primitives — raw values, no intent encoded
  2. Semantic — intent only, aliases to primitives, no raw values

Flow: Primitive → Semantic → Component

Components never reference primitives directly — they only use semantic tokens.

Rules

  1. Semantic tokens never contain raw values — aliases only
  2. Components never reference primitive tokens directly
  3. Light and dark semantic sets must have identical token paths
  4. Desktop and mobile type scales must have identical token paths
  5. body/md fontSize must be 16px in both breakpoints (accessibility)
  6. No hardcoded values survive into generated component code

How the sync works

design-token.md
  ↓ (local parser)
token-map.json
  ↓ (DesignPull CLI spawns)
Claude Code subprocess
  ↓ (figma-use skill)
Figma variables

DesignPull parses your design-token.md locally into a structured token-map.json, then uses Claude Code with the figma-use skill to write variables directly to your Figma file. The figma-use skill is part of Figma's official MCP server — no plugins or desktop bridge needed.


Troubleshooting

Figma MCP not configured

Error: Figma MCP server not found in your Claude Code config

Fix: Follow Figma's MCP setup guide and verify with:

claude mcp list

PAT errors

Error: Missing required values in .env: FIGMA_ACCESS_TOKEN

Fix:

  1. Go to figma.com → Account Settings → Security → Personal Access Tokens
  2. Create a new token with File content (read) scope
  3. Copy the token (starts with figd_)
  4. Open .env and set FIGMA_ACCESS_TOKEN=figd_your_token_here

You also need edit access to the target Figma file for the figma-use skill to write variables.


Parse validation failed

Error: Token map missing required collection: Primitives

Fix:

  • Check design-token.md for syntax errors
  • Ensure all three sections exist: Primitive Tokens, Semantic Tokens, Typography Scale
  • Review .designpull/failed-parse.json for debugging
  • File a bug at github.com/kuriouscreator/designpull/issues

Claude Code not installed

Error: claude CLI not found

Fix:

npm install -g @anthropic-ai/claude-code

Verify:

claude --version

Development

git clone https://github.com/kuriouscreator/designpull
cd designpull
npm install
node src/index.js --help

Run tests:

npm test

Folder Structure

designpull/
├── src/
│   ├── index.js        # Commander entry point
│   ├── init.js         # designpull init
│   ├── sync.js         # designpull sync
│   ├── doctor.js       # designpull doctor
│   ├── parser.js       # Local design token parser
│   └── utils.js        # .env parsing utility
├── test/
│   ├── parser.test.js  # Parser tests (30 tests)
│   ├── sync.test.js    # Sync tests
│   ├── init.test.js    # Init tests
│   └── doctor.test.js  # Doctor tests
├── package.json
├── .env.example
└── README.md

Environment Variables

See .env.example for the full list. Required:

  • FIGMA_FILE_URL — your Figma file URL
  • FIGMA_ACCESS_TOKEN — Figma Personal Access Token (starts with figd_)

Questions?


Contributing

We welcome contributions! Please see CONTRIBUTING.md for:

  • Development setup instructions
  • Code style guidelines
  • Testing requirements
  • Pull request process

License

MIT - see LICENSE for details