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

@rich-apis/cursorrules

v1.0.1

Published

Professional .cursorrules templates for Next.js, FastAPI, and React Native projects

Readme

@rich-apis/cursorrules

Professional .cursorrules templates for Cursor AI. One command to set up battle-tested AI coding rules for your project.

More templates and vibe coding tips: t.me/vibecodingtips_original

Quick Start

# Copy a template to your project
npx @rich-apis/cursorrules init nextjs
npx @rich-apis/cursorrules init fastapi
npx @rich-apis/cursorrules init react-native

That's it. Open your project in Cursor and the rules are active.

Available Templates

| Template | Stack | Highlights | |----------|-------|------------| | nextjs | Next.js 14+, TypeScript, Tailwind | App Router, Server Components, Server Actions, Zod validation | | fastapi | Python 3.11+, FastAPI, Pydantic v2 | 3-layer architecture, async, SQLAlchemy 2.0, Alembic | | react-native | React Native / Expo, TypeScript | React Navigation, Zustand, React Query, FlashList |

What's Inside

Each template defines:

  • Tech stack expectations so the AI uses the right libraries
  • Code style rules (naming, structure, patterns)
  • Architecture guidelines (where logic lives, layering)
  • Performance best practices specific to the framework
  • Security rules the AI must follow
  • Testing expectations and patterns

CLI Usage

# List all templates
npx @rich-apis/cursorrules list

# Initialize a template
npx @rich-apis/cursorrules init <template>

# Help
npx @rich-apis/cursorrules --help

Programmatic Usage

const { getTemplate, listTemplates } = require('@rich-apis/cursorrules');

// Get template content
const rules = getTemplate('nextjs');

// List available templates
const templates = listTemplates();
// [{ id: 'nextjs', name: 'Next.js', description: '...' }, ...]

Customization

The templates are starting points. After running init, edit .cursorrules to match your project:

  • Add your specific libraries and versions
  • Adjust architecture rules to your codebase
  • Add project-specific conventions
  • Include domain terminology

Why .cursorrules?

Cursor AI reads .cursorrules from your project root to understand your coding standards. Without rules, the AI guesses. With good rules, it writes code that fits your codebase from the first try.

More Resources

License

MIT