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

clipper-css

v0.5.2

Published

Clipper is a simple Tailwind framework for building pages without fighting CSS and drowning in utility classes.

Readme

Clipper

Clipper is a simple Tailwind framework for building pages fast without fighting CSS. It is designed for designers and developers alike: semantic markup by default, token-driven styling, and just enough utilities to stay productive.

You can start with clean HTML and only add utilities when they actually help.

Quick start

The best way to install clipper is to run it in a freshly installed framework project with Tailwind installed. Clipper currently supports Astro and SvelteKit.

Astro

SvelteKit

After installation, run this in your project folder:

npx clipper-css

The installation is user-friendly and won't overwrite anything without your permission. You can run it multiple times to update clipper to the latest version (will only overwrite clipper.css in that case).

After installing, the root page will display a demo of Clipper's features.

Core idea in one example

The section is the fundamental building block. Put these directly below main. The rest is pretty much self-explanatory.

<body>
  <header class="header-sticky"></header>
  <main>
    <section id="intro">
      <h1>Hello Clipper</h1>
      <p class="readable">Start semantic, then add only the few utilities you really need.</p>
      <div class="row">
        <a href="/primary" class="btn">Primary action</a>
        <a href="/secondary" class="btn btn-outline">Secondary action</a>
      </div>
    </section>
  </main>
  <footer></footer>
</body>

Spacing (the fluent part)

Spacing is tokenized and fluid via clamp(). Use Clipper spacing utilities between 4xs to 4xl as normal tailwind classes. base is in the middle.

Example:

<div class="gap-sm">
  <span>First item</span>
  <span>Second item</span>
  <span>Third item</span>
</div>

Change spacing tokens in variables.css and rhythm updates everywhere.

Colors

Colors are also tokenized in variables.css, with semantic tokens so theme decisions stay centralized and dark mode works properly. Built-in tokens that can be used directly on the utility classes:

Base colors

background
foreground
accent
accent-foreground
muted
muted-foreground

Primary color

primary (incl. 50-900)
primary-foreground
primary-hover
primary-muted

Other

link
link-hover
link-underline
link-underline-hover
border

Example:

<span class="bg-accent-foreground">First item</span>

Typography

Headings are semantic first (h1..h5). If a heading needs a different visual size, apply the display class directly:

<h3 class="h2">Semantically h3, visually h2</h3>

Body text stays stable while header sizes (and spacing) scale fluidly.

List of utility classes

| Class | Function | | --------------- | --------------------------------------- | | row | flex-row with sensible defaults | | readable | Max-width for readable text | | full-width | Break children out of max page width | | page-width | Restore max page width to inner content | | trim-top | Trim padding and margin of first child | | trim-bottom | Trim padding and margin of last child | | trim | Trim padding and margin of both | | header-sticky | Simple sticky header |

List of components

Clipper includes three generic reusable primitives, compatible with dark mode, purely for "getting started" convenience. They can be replaced by any UI framework or custom styles.

| Class name | Function | | ----------------- | -------------------------------------- | | btn | You guessed it! | | card | You guessed that too | | badge | You guessed right three times in a row | | btn btn-outline | Outline button version |

Where to edit what

  • variables.css → tokens (color, type, spacing)
  • components.css → reusable components (.btn, .card, .badge)
  • clipper.css → framework definitions - usually no need to change this file! Will be updated if npx clipper-css is run multiple times.

Skills and instructions for AI

The installations comes with an instructions file for AI Agents, copied to .github/instructions/clipper.instructions.md and a skill called clipper-convert-website for converting websites to Clipper, copied to .github/skills/clipper-convert-website/SKILL.md.

Design philosophy

Clipper is intentionally small and unobtrusive. Use Tailwind classes or a UI component framework whenever you need, Clipper won't stand in your way.

If you can express it semantically, do that first. If you need control, use tokens/utilities. If it repeats, make it a component.

Get in touch

Please suggest fixes etc on Github. Improvements can surely be made.