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

@by-sixteen/prism-cli

v0.5.7

Published

Sync design tokens between CSS and Figma variables in real-time

Downloads

376

Readme

prism-cli

Sync design tokens between CSS and Figma variables in real-time.

Quick Start

# In your project directory
npx prism-cli init
npx prism-cli start

Then open the Figma plugin — it will guide you through initial setup.

Commands

| Command | Purpose | |---------|---------| | prism start | Start bridge + watcher together (recommended) | | prism init [name] | Scaffold Prism in the current directory | | prism watch | Watch tokens.css and sync to Figma | | prism bridge | Start WebSocket bridge server only | | prism bootstrap from-css | Create Figma variables from an existing CSS file | | prism bootstrap from-figma | Generate a CSS file from Figma variables | | prism bootstrap from-template | Scaffold from a built-in template then push to Figma | | prism ingest | Extract colours from Figma, generate missing state variants |

Bootstrap

One-time setup to connect your existing tokens to Figma:

# Push an existing tokens.css to Figma
npx prism-cli bootstrap from-css --tokens tokens.css --collection "Tokens" --mode Light

# Generate tokens.css from Figma variables
npx prism-cli bootstrap from-figma --collection "Tokens" --mode Light --output tokens.css

# Scaffold from the minimal template (22 tokens: colours, input, button)
npx prism-cli bootstrap from-template --name minimal --collection "Tokens"

The bridge must be running for bootstrap to work:

npx prism-cli bridge   # in one terminal
npx prism-cli bootstrap from-css   # in another

Or use prism start which runs both together.

Configuration

prism.config.js in your project root:

export default {
  project: {
    name: 'my-project',
    type: 'webapp'  // webapp | marketing | library
  },
  tokens: {
    file: './tokens.css',
    format: 'hex'  // hex | oklch
  },
  theme: {
    mode: 'light',  // light | dark | both
    primaryColor: '#3b82f6'
  },
  components: ['button', 'input'],
  bridge: {
    url: 'ws://localhost:3055',
    port: 3055,
    channel: 'my-project'
  },
  figma: {
    collection: 'Tokens',
    mode: 'Light'
  }
};

How It Works

  1. tokens.css is your single source of truth for design tokens
  2. prism start runs the bridge (WebSocket relay) and watcher (file monitor) together
  3. The Figma plugin connects to the bridge and syncs variables bidirectionally

Changes to tokens.css are pushed to Figma automatically. Changes to Figma variables are written back to tokens.css.

Migrating from Legacy Scripts

If you previously used npm run bridge + npm run watch:

# Old workflow
npm run bridge   # Terminal 1
npm run watch    # Terminal 2

# New workflow
npx prism-cli start

Your existing prism.config.js continues to work unchanged.

License

MIT