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

@codefromdesign/cfd

v0.7.7

Published

CLI + MCP server for CodeFromDesign — sync Figma-to-code pipeline results with Claude Code

Readme

cfd

CLI + MCP server for CodeFromDesign — sync Figma-to-code pipeline results with Claude Code.

Install

npm install -g @codefromdesign/cfd

Requires Node.js 18 or later.

Setup

  1. Get your API key from codefromdesign.com/settings
  2. Run:
cfd init <your-api-key>

This saves your config and registers the MCP server with Claude Code.

Usage

CLI Commands

cfd list                  # list all projects
cfd sync <job-id>         # sync project data to local workspace
cfd build <job-id>        # trigger website build
cfd status                # show config and engine health

With Claude Code

After cfd init, open Claude Code anywhere on your machine. It auto-connects to CodeFromDesign via MCP. Ask Claude to:

  • "List my CodeFromDesign projects"
  • "Sync project abc123 and start cleaning the frames"
  • "Compare frame 0 and show me the parity score"

Claude Code will iteratively refine each frame's HTML until it matches the Figma design, then assemble a production website.

How it works

codefromdesign.com → Go engine processes Figma design → Frame packages
                                                              ↓
cfd sync → downloads frames to ~/.codefromdesign/workspace/
                                                              ↓
Claude Code → reads screenshots, refines HTML, calls compare
                                                              ↓
cfd compare → engine screenshots HTML, diffs against Figma
                                                              ↓
repeat until parity > 95% → submit → build → production website

Development

npm install               # install dependencies
npm run dev -- --help     # run CLI from source via tsx
npm run build             # bundle with esbuild
npm run build:check       # type-check without emitting

Environment Variables

| Variable | Purpose | |----------|---------| | CFD_API_KEY | Override API key | | CFD_ENGINE_URL | Override engine URL (default: https://engine.codefromdesign.com) |

Files

| Path | Purpose | |------|---------| | ~/.codefromdesign/config.json | Configuration | | ~/.codefromdesign/workspace/ | Synced project data |