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

tenet-ui

v0.3.0

Published

Tenet Design System — a small, realistic in-house design system (tokens + React components) used to demo the design-system skill.

Readme

Tenet Design System (tenet-ui)

A small, deliberately private design system (design tokens + React components) built for the talk demo. The model has never seen it — so generating compliant code requires the skill, not training-data recall. "Tenet" is a placeholder brand; rebrand freely.

It ships the same machine-readable artifact shapes a real DS does, so the skill's ingest is realistic and transfers to any design system.

Install

npm install tenet-ui
# peer deps:
npm install react react-dom

Usage

Import the stylesheet once at your app root, then use the components. Without the stylesheet, every component's var(--token) is undefined and the UI renders unstyled.

import 'tenet-ui/styles.css';            // tokens (light + dark) + component styles
import { Button, Table, FormControl, TextInput } from 'tenet-ui';

export function Example() {
  return (
    <FormControl required>
      <FormControl.Label>Email</FormControl.Label>
      <TextInput type="email" block />
    </FormControl>
  );
}

Dark mode

Tokens are CSS custom properties scoped to a data-color-mode attribute (light is the default). Switch the whole tree by setting it on a wrapper (or <html>):

<html data-color-mode="dark"> … </html>

No component code changes for theming — the semantic tokens re-resolve.

What's in the box

| Source | Lives in | Built artifact (what ingest reads) | |--------|----------|--------------------------------------| | Design tokens | tokens/tokens.json (source) | dist/tokens.json (flat, resolved light+dark) + dist/tokens.css (themed CSS vars) | | Component API | src/components/*/*.tsx + *.docs.json | generated/components.json (prop catalog) | | Guidelines | guidelines/*.md | per-component usage rules |

Components: Button, Stack, Card, TextInput, Textarea, Select, Checkbox, Radio/RadioGroup, Label, Table, FormControl.

Token model

  • Base (primitive) tokens — raw values: base.color.*, base.size.*.
  • Theme-agnostic semanticsspace.*, borderWidth.*, borderRadius.*, fontSize.*, fontWeight.*, control.*, shadow.*.
  • Themed semantics (light / dark) — fgColor.*, bgColor.*, borderColor.*.
  • CSS variable name = the token path joined with -, prefixed -- (e.g. bgColor.accent.emphasis--bgColor-accent-emphasis).

Components must only use semantic tokens — never raw hex/px. That rule is what the skill's audit enforces.

Scripts

npm run build          # build:js (tsup) + tokens + catalog + styles -> dist/ + generated/
npm run build:tokens   # tokens/tokens.json -> dist/tokens.{json,css}
npm run build:catalog  # src/**/*.docs.json -> generated/components.json
npm run typecheck      # strict tsc over the components

Publishing runs prepublishOnly (a full build) automatically.