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

@adres/ai-dls-blueprint

v1.0.1

Published

Overlay Adresx DLS-aware AI skills and the dls-mcp server onto any project.

Readme

@adres/ai-dls-blueprint

Overlay Adresx DLS-aware AI skills and the dls-mcp server onto any project, so AI coding assistants generate UI that uses the real Design Language System — real components, tokens, and brand themes — instead of inventing lookalikes.

This is a workflow layer, not an app skeleton. Scaffold your app first (create-next-app, Vite, etc.), then run the installer on top.

Run it

# from a clone
npm install
npm start          # interactive installer (tsx index.ts)

# or, once published
npx @adres/ai-dls-blueprint

The installer asks four things: which AI clients, how to reach the MCP server (hosted HTTP or local stdio), a default brand/theme, and whether to commit the blueprint files or gitignore them.

What it installs

  • Skills (single source in templates/skills/) stamped into each selected client:
    • Claude Code → .claude/skills/ (invoke /dls-screen), plus CLAUDE.md
    • Cursor → .cursor/skills/ (invoke by name), plus .cursor/mcp.json
    • Codex / Copilot → .agents/skills/ (invoke $dls-screen), plus AGENTS.md
  • Rules — .dls/dls-rules.md, the five non-negotiable DLS rules every UI change follows.
  • MCP config — the adresx-dls server wired into each client's config format.

Skills

  • dls-setup — pick the default brand/theme and confirm MCP connectivity
  • dls-screen — build a screen/feature from real DLS components
  • dls-component — add or replace one component with its correct contract
  • dls-prototype — Figma link, brief, or PRD/use-case bundle → real DLS project scaffold (with a review gate before commit)
  • dls-review — read-only check of code for DLS drift
  • dls-doctor — read-only blueprint health check

Architecture

Each skill is authored once under templates/skills/<name>/SKILL.md. The installer copies that single source into whichever client folders you pick, so the adapters never drift. To add or change a skill, edit the template and re-run the installer.

Security

The HTTP transport authenticates with a Bearer token read from $DLS_MCP_TOKEN. The installer never writes the token into config — set it in your environment. Do not commit tokens.