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

claytone

v0.3.0

Published

Design engine scaffolder for AI coding assistants.

Downloads

12

Readme

Claytone

A CLI that scaffolds a design engine for AI coding assistants. Run it in any project to generate a structured Claude Code configuration that teaches Claude how to work within your design system.

What it generates

your-project/
├── CLAUDE.md                          # Project-level rules for Claude
├── .claude/
│   ├── rules/
│   │   ├── design-tokens.md           # Token authority and ban list
│   │   ├── component-naming.md        # Naming conventions
│   │   └── spacing-layout.md          # Spacing and layout constraints
│   ├── memory/
│   │   └── design-decisions.md        # Design decision log (optional)
│   └── hooks/
│       └── pre-tool-use.sh            # Pre-write validation hook (optional)
└── src/styles/tokens.css              # Design tokens (CSS custom properties)

All files are tailored to the design preset you select during setup.

Install

npm install -g claytone

Or run directly with npx:

npx claytone init

Usage

Navigate to your project root and run:

claytone init

You'll be prompted for:

  • Project name — defaults to the current directory name
  • Design preset — the design system to base your guardrails on (e.g. Notion)
  • Memory files — whether to scaffold a design decisions log
  • Hooks — whether to include a Claude Code pre-tool-use hook stub

To skip prompts and use defaults:

claytone init --yes

Presets

Each preset encodes a real, tested design system as Claude Code guardrails — tokens, rules, and philosophy all in one.

| Preset | Description | | ---------- | ------------------------------------------------------------------- | | Notion | Inter type, warm near-black palette, 4px grid, minimal decoration | | Vercel | Geist type, high-contrast monochrome, 8px grid, technical precision |

Development

# Install dependencies
npm install

# Build
npm run build

# Build in watch mode
npm run dev

# Type check
npm run typecheck

# Test locally
npm link
claytone init

Project structure

src/
├── cli.ts                    # Binary entry — Commander program root
├── commands/init.ts          # init command handler
├── prompts/                  # @clack/prompts interactive flow
├── generators/               # File writers (orchestrator + per-output generators)
├── templates/                # Markdown/shell template files
│   ├── claude-md.md          # CLAUDE.md template ({{projectName}}, {{presetSection}}, …)
│   ├── rules/                # Base rule files (static markdown)
│   ├── memory/               # Design decisions log template
│   └── hooks/                # Hook stub
├── presets/                  # One directory per preset (notion, vercel, …)
│   └── <name>/
│       ├── index.ts          # Assembles PresetDefinition from files
│       ├── tokens.css        # CSS custom properties
│       ├── claude-md-section.md
│       └── augmentations/    # Preset-specific rule additions
├── types/index.ts            # ProjectConfig and PresetDefinition interfaces
└── utils/                    # fs helpers, logger, interpolate, load-template

Adding a preset

  1. Create src/presets/<name>/ with tokens.css, claude-md-section.md, and any augmentations/*.md
  2. Create src/presets/<name>/index.ts that assembles a PresetDefinition using loadTemplate()
  3. Register it in src/presets/index.ts