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

grimorio

v0.1.2

Published

Design system infrastructure CLI — analyze components, generate specs, validate implementations, and expose your design system via MCP

Downloads

20

Readme

grimorio

The CLI for grimorio — analyze components, manage specs, validate implementations, and bridge design with development.

This is the only public package in the monorepo. It orchestrates all other packages.

Install

npm install -g grimorio

Commands

grimorio init

Scaffolds the project: creates grimorio.config.ts, specs/ directory, and tokens.json.

grimorio add <name>

Creates a component spec. Auto-detects built-in presets by name.

grimorio add Button                    # uses "button" preset → full spec
grimorio add Select -d "Country picker" # preset + custom description
grimorio add CustomWidget              # no matching preset → improved skeleton
grimorio add --list-presets            # list available presets

Built-in presets: button, input, select, checkbox, dialog, card, avatar, badge, tabs, textarea.

grimorio spec:infer <file>

Infers a spec from a component source file via static analysis (no AI).

grimorio spec:infer src/components/Button.tsx
grimorio spec:infer src/components/Modal.vue -o specs/modal.json

grimorio validate

Validates all components against their specs and design tokens.

grimorio validate
grimorio validate --level strict
grimorio validate --watch              # re-validate on file changes

grimorio figma:import <url>

Imports component specs from Figma deterministically (no AI). Maps Figma component properties to props, variants, slots, and token mappings.

grimorio figma:import "https://figma.com/design/ABC/..." --component Button

Requires a Figma API token (--token, FIGMA_TOKEN env var, or figma.token in config).

grimorio figma:validate <url>

Validates a Figma component against an existing spec. Reports differences in props, variants, token mappings, slots, anatomy, states, and events.

grimorio figma:validate "https://figma.com/design/ABC/..." --component Button

grimorio tokens:list / tokens:validate / tokens:export

List, validate, and export design tokens. See root README for full details.

grimorio mcp:serve

Starts the MCP server — the AI-friendly entry point. Exposes 16 tools, 2 resources, and 4 prompts.

Configuration

grimorio.config.ts:

export default {
  specs: "./specs/**/*.json",
  tokens: "./tokens.json",
  components: "./src/components/**/*.{tsx,vue}",
  validation: {
    level: "standard",
  },
  figma: {
    // token: 'figd_...',
  },
};

Programmatic API

The package exports defineConfig for type-safe configuration:

import { defineConfig } from "grimorio";

export default defineConfig({
  specs: "./specs/**/*.json",
});

Dependencies

  • citty — CLI framework
  • c12 — Configuration loading
  • consola — Logging
  • tinyglobby — File globbing
  • grimorio-core, grimorio-analyzers, grimorio-validators, grimorio-mcp

Structure

src/
├── commands/
│   ├── init.ts              # grimorio init
│   ├── add.ts               # grimorio add (with preset auto-detect)
│   ├── spec-infer.ts        # grimorio spec:infer
│   ├── validate.ts          # grimorio validate (with --watch)
│   ├── figma-import.ts      # grimorio figma:import
│   ├── figma-validate.ts    # grimorio figma:validate
│   ├── tokens-list.ts       # grimorio tokens:list
│   ├── tokens-validate.ts   # grimorio tokens:validate (with --watch)
│   ├── tokens-export.ts     # grimorio tokens:export
│   └── mcp-serve.ts         # grimorio mcp:serve
├── figma/
│   ├── client.ts            # Figma REST API client + URL parser
│   └── mapper.ts            # Figma properties → ComponentSpec mapper
├── utils/
│   ├── formatting.ts        # Validation result formatting
│   ├── tokens.ts            # Token path resolution
│   └── glob.ts              # File pattern matching
├── config.ts                # GrimorioConfig type + c12 loader
├── main.ts                  # CLI entry point (citty)
└── index.ts                 # Public API (defineConfig)