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

brandsync-skills

v0.2.8

Published

BrandSync framework skill rules for Claude

Readme

Skills Repo

Framework-specific skill rules injected into Claude via MCP. These rules are context-agnostic and capture learned patterns from real testing sessions.

Structure

skills/         ← one file per framework
contributing/   ← templates and checklists for contributors
CHANGELOG.md    ← version history

How It Works

The MCP server fetches the relevant skill file at a pinned version tag and injects it into Claude's context alongside the HTML/CSS pattern. Claude follows these rules when converting patterns to the target framework.

Contributing

  1. Find a mistake Claude made during testing
  2. Use contributing/template.md to write the agnostic rule
  3. Branch off dev: git checkout -b fix/short-description
  4. Add the rule to the correct skill file and update CHANGELOG.md
  5. Open a PR into dev — use contributing/review-checklist.md to self-review first
  6. After validation on dev, a maintainer promotes to main and creates a new tag

Versioning

  • main = stable, what MCP server pins to
  • dev = integration branch
  • Tags: v0.1.0, v0.2.0, etc.
  • Each skill file has a version header: <!-- version: x.x.x | updated: date -->