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

stable-frontend

v1.0.3

Published

Frontend architecture and stability guidelines for AI coding agents in React and Next.js

Readme

stable-frontend

npm version

Frontend architecture and stability rules for code generation in React and Next.js projects.

Overview

When coding agents generate frontend code, they frequently skip input validation, error states, accessibility tags, and testing. stable-frontend sets up structured engineering guidelines and folder conventions in your repository to keep generated code consistent and production ready.

Rules are organized as a modular index to minimize context window usage. Instead of loading an entire ruleset on every prompt, the main index directs tools to read only the guidelines relevant to the active task.

Usage

Run the setup command in the root of your project:

npx stable-frontend

Generated structure:

├── AGENTS.md                  # Main rule index and router
├── CLAUDE.md                  # Claude Code instructions
└── .agents/
    └── rules/
        ├── 01-architecture.md # Feature-based structure and colocation
        ├── 02-validation.md   # Schema validation and form lifecycles
        ├── 03-data-fetching.md# Async states and component boundaries
        ├── 04-testing.md      # Testing pyramid and edge case checklists
        ├── 05-performance.md  # Accessibility, Core Web Vitals, and SEO
        └── 06-security.md     # Authentication, XSS defense, and data isolation

Adding Rules

To add a new rule:

  1. Create a template folder under src/templates/rules/ with a prompt.md and index.ts.
  2. Register the template in src/templates/rules/index.ts.
  3. Run npm run build.

See CONTRIBUTING.md for detailed guidelines.

Community

Contributions, issues, and feature proposals are welcome. Please read CODE_OF_CONDUCT.md before participating.