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

@lukeda/nofi

v0.0.2

Published

Low-fidelity mockups for agents. Pug structure, Tailwind layout, instant comparison boards.

Readme

nofi

Let your agent sketch before it builds.

Pug + Tailwind → low-fidelity mockups → choose a layout → build it.

Agent skill · Source format · Themes · Playground · GitHub

Choose a design for one screen. Four sign-in layouts with identical content: Acme, welcome text, email, password, Sign in, and Forgot password. Compare a centered form, split layout, contained card, and wide form.

Four layouts for the same sign-in screen

Open HTML · Board source

Wireframe several screens. Explore sign-in, projects, settings, and checkout together to establish the structure of an app.

Sign-in, projects, settings, and checkout wireframes

Open HTML · Board source

Made for agents

Ask your agent:

Use nofi to sketch six different layouts for a project dashboard. Render a comparison board and let me choose before implementing it.

The single nofi skill covers writing the mockups, rendering them, and retaining the selected source for implementation. Layouts use familiar Pug and Tailwind. Themes provide deliberately basic buttons, inputs, typography, and image placeholders.

main.flex.flex-col.gap-4.p-8
  h1 Welcome aboard
  p Make room for your next idea.
  input(placeholder="Email address")
  button Create account

Give your agent nofi

Install the skill:

npx skills add lukeda/nofi --skill nofi

Ask your agent to use nofi to sketch layouts and render a comparison board. The skill handles source files, rendering, and keeping your chosen layout for implementation.

The renderer runs through npx:

npx --yes @lukeda/nofi board board.yaml -o board.html

For PNG output, install Chromium once with npx --yes @lukeda/nofi setup.

Agent setup · Local development · Contributing

Compare options

A board can give reusable Pug files names and shared settings:

viewport: [640, 480]
theme: wireframe
columns: 2
items:
  - file: sidebar.pug
    name: Sidebar navigation
  - file: topbar.pug
    name: Top navigation

The CLI accepts a board file or YAML on stdin through a heredoc. Items can reference files or contain inline pug; --stdout returns HTML without creating output files. HTML is standalone; PNG export uses Chromium. See the board commands.

The examples include six dashboard layouts, four login layouts, two settings layouts, and two checkout flows. The browser playground includes all of them, with editable source, viewport controls, and themes. Try it in the playground.

Why this approach?

  • Familiar source: declarative Pug and Tailwind utilities, without a new layout language.
  • Focus on structure: compare navigation, hierarchy, and density before polishing visuals.
  • Theme-aware: semantic colour utilities adapt the same source to different themes.
  • Portable handoff: retain the selected Pug alongside the implementation brief.

Library API · Theme authoring

Inspired by PlantUML Salt, Balsamiq, and Mermaid.

MIT licensed.