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

@magicpatterns/helix-shadcn-demo

v0.0.6

Published

Shadcn-based design system preset for Tailwind CSS

Readme

@magicpatterns/helix-shadcn-demo

This is an example design system package showing off:

  • A custom NPM package being bundled and consumed by Magic Patterns
  • A custom MCP server that exposes existing Storybook files + custom guidelines

This is an opinionated set up for what we've seen working well in terms of production codebases + external AI agents. The two important pieces here are:

Context on Component Usage: Context and examples on how an agent should use your custom design system. The more the better! The implementation in this example is a custom MCP server, but there are many ways to go about this. Other solutions include:

  • Directly leveraging Storybook's MCP Server add-on
  • Parsing the NPM package when context is bundled in to skip needing to host a MCP server

NPM Package: This helps Magic Patterns use the exact same components your production web app might be using. It also helps the code be more "production-ready", in that it'll be using the same exact props / composition as you would find in the codebase. Magic Patterns uses this to render the preview of a prototype in a Vite app.

Demo Codebase Overview

/guidelines
  # Inside here, you can put .md files that will be automatically exposed as context in the MCP
  # You can put anything in here including product context!
/mcp
  # This is where the MCP server lives
  # This MCP server actually scrapes the rest of the codebase to find stories and guidelines and exposes it in a toolset described in MP_DS_MCP_SPEC.md
/recipes
  # This is where extra resources on how to compose components, common layout patterns, and otherwise important documentation on how components should be used lives
/src
  # Where the design system components live

Running the demo

The MCP is automatically hosted on Render. Any changes pushed to main will automatically deploy to Render in 5-10 minutes. The MCP currently is designed to automatically parse stories in the codebase to use as context. For example, if you create a new component with a story, the MCP when deployed will automatically include that information.