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

bem-wind

v0.2.2

Published

Install the BEM-Wind Claude skill — write semantic BEM CSS using Tailwind @apply directives.

Readme

BEM-Wind

A Claude Code skill for writing UI CSS the BEM-Wind way — semantic, prefixed BEM component classes composed entirely from Tailwind utilities inside @apply directives, backed by design tokens. Keep Tailwind's design system; get the utility soup out of your markup.

npx bem-wind add-skill --global

That installs the skill into ~/.claude/skills. Then ask Claude to style or convert a component — it loads automatically when the work matches — or invoke it explicitly with /bem-wind.

What it does

It teaches Claude to write CSS like this — semantic class names in your markup, @apply in your stylesheet:

<button class="ds-button ds-button--primary">Get started</button>
.ds-button {
  @apply inline-flex items-center justify-center px-4 py-2 rounded-lg;
  @apply transition-colors duration-200;
  @apply focus:outline-none focus:ring-2 focus:ring-blue-500 focus:ring-offset-2;

  &--primary {
    @apply bg-blue-500 text-white hover:bg-blue-600 active:bg-blue-700;
  }
}

…instead of the same utilities scattered inline across every component.

The method in five rules

  1. Everything inside @apply — compose from Tailwind utilities; no raw CSS properties.
  2. Prefix every class with a 2–4 character project prefix (ds-, app- — your choice).
  3. BEM naming[prefix]-block__element--modifier.
  4. Prefer standard Tailwind values — reach for arbitrary bracket values only when the design truly needs one.
  5. No utilities in markup — components carry semantic class names only.

It's design-system-agnostic: one structural method, any visual identity, swapped via a theme layer.

Install options

npx bem-wind add-skill            # ./.claude/skills (this project — commit it to share with your team)
npx bem-wind add-skill --global   # ~/.claude/skills (all your projects)
npx bem-wind add-skill --force    # overwrite an existing install

Or copy skill/bem-wind/ into a .claude/skills directory manually.

Install as a Claude Code plugin

This repo is also a Claude Code plugin marketplace, so you can install the skill without leaving Claude Code:

/plugin marketplace add tarynstark/bem-wind
/plugin install bem-wind@bem-wind

The skill then loads as part of the plugin (invoke it via /bem-wind). Both paths ship the same skill — use npx for a plain file install, or the plugin for in-app management (enable/disable/update).

What's in the skill

  • SKILL.md — the methodology: the five rules, authoring components, converting utility-heavy HTML, tokens & theming, and a review checklist.
  • reference/examples.md — card, input, dropdown, modal, tooltip, grid, animation, and theme patterns.
  • reference/tokens.css — a drop-in design-token scaffold (reprefix and theme it per project).

License

MIT © Taryn Stark