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

@kern-system/design-system

v0.0.1

Published

Kern — tokens, components, and rules authored once, consumed everywhere.

Readme

Kern

The seed at the core. One source of truth — tokens, components, and rules authored once, consumed everywhere.

Kern is a design system built on W3C DTCG design tokens. Edit tokens/ and specs/ once — run npm run build — and every consumer updates automatically.

Four ways to consume

1. npm package (React + typed tokens)

npm i @kern-system/design-system
import { Button, Input, Card, CardHeader, CardBody, CardFooter } from '@kern-system/design-system';
import '@kern-system/design-system/css'; // or link build/css/variables.css in your HTML

<Card shadow="md">
  <CardHeader><h2>Sign up</h2></CardHeader>
  <CardBody>
    <Input id="email" label="Email" type="email" required />
  </CardBody>
  <CardFooter>
    <Button variant="primary" type="submit">Create account</Button>
    <Button variant="ghost">Cancel</Button>
  </CardFooter>
</Card>

Typed token constants:

import { tokens } from '@kern-system/design-system/tokens';

tokens.color.action.primary   // "#2563eb"
tokens.spacing[4]             // "1rem"

2. CSS drop-in (zero build step)

Copy build/css/variables.css into any project. All 116 tokens available as --kern-* CSS custom properties under :root.

<link rel="stylesheet" href="variables.css">
.my-button {
  background-color: var(--kern-color-action-primary);
  padding: var(--kern-spacing-2) var(--kern-spacing-4);
  border-radius: var(--kern-radius-md);
}

3. Tailwind preset

// tailwind.config.js
import kernPreset from '@kern-system/design-system/tailwind';
export default { presets: [kernPreset] };
<button className="bg-action-primary text-white px-4 py-2 rounded-md hover:bg-action-primary-hover">
  Click me
</button>

4. LLM Skill (progressive disclosure)

Copy the skill/ directory into your project's .claude/skills/ or reference it in your LLM context:

skill/
  SKILL.md              ← load this first (84 lines, all you need for basic use)
  references/
    tokens.md           ← full token catalog with alias chains
    components.md       ← all props, variants, a11y
    usage-rules.md      ← global principles + per-component do/don't

The model loads SKILL.md first (cheap context cost). References are loaded on demand.

5. Context bundle (paste-into-prompt)

Copy llm-context/context-bundle.md into any LLM prompt to give the model the full design system in one shot: all tokens, all specs, all rules, plus a complete end-to-end example.


Building from source

git clone https://github.com/kern-design/design-system
npm install
npm run build

Build output:

build/css/variables.css     CSS custom properties (--kern-*)
build/tailwind/preset.js    Tailwind theme extension
build/ts/tokens.ts          Typed token constants
skill/SKILL.md              LLM Skill entrypoint
skill/references/           Progressive disclosure reference files
llm-context/context-bundle.md  Single flat LLM context file

Build time: ~80ms.

Docs site

npm run docs:dev    # local dev server
npm run docs:build  # static build

Source of truth

| Source | Type | Edit? | | -------- | ------ | ------- | | tokens/*.json | W3C DTCG token files | ✅ Yes | | specs/*.spec.json | Component specifications | ✅ Yes | | components/ | React reference implementations | ✅ Yes | | build/ | Generated artifacts | ❌ Never — run npm run build | | skill/ | Generated LLM Skill files | ❌ Never — run npm run build:skill | | llm-context/ | Generated context bundle | ❌ Never — run npm run build:context |

Architecture

tokens/*.json ──┐
                ├─► scripts/build-tokens.mjs ──► build/css, build/tailwind, build/ts
specs/*.json ───┤
                ├─► scripts/build-skill.mjs ───► skill/SKILL.md, skill/references/*
                └─► scripts/build-context-bundle.mjs ──► llm-context/context-bundle.md

Versioning

Kern uses Conventional Commits and Changesets for automated versioning.

npx changeset        # describe your change
npx changeset version # bump versions
npx changeset publish # publish to npm

License

MIT