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

@crimsonsunset/cursor-config

v1.1.3

Published

Shared Cursor rules configuration

Downloads

38

Readme

@crimsonsunset/cursor-config

Shared Cursor rules configuration package. Automatically installs standardized Cursor rules to any project.

Installation

npm install -D @crimsonsunset/cursor-config

That's it! The .cursor/rules/ directory will be automatically created in your project root with all rule files.

What it does

  • Creates .cursor/rules/ directory in your project root via postinstall script
  • Merges with existing rules - only installs rules that don't already exist
  • Contains comprehensive development guidelines and best practices
  • Works with Cursor's latest .mdc rule format

Rules included

Auto-Applied Rules

  • large.mdc - Comprehensive development standards (auto-applies to all conversations)

Manual Rules (use @rulename)

  • starter.mdc - New codebase onboarding protocol (@starter)
  • performance.mdc - Performance optimization guidelines (@performance)
  • security.mdc - Security best practices (@security)
  • testing.mdc - Test strategy and debugging (@testing)
  • backend.mdc - API design and backend practices (@backend)

Manual installation

If you prefer not to use the postinstall script:

npm install -D @crimsonsunset/cursor-config --ignore-scripts

Then manually copy the rules:

mkdir -p .cursor/rules
cp node_modules/@crimsonsunset/cursor-config/.cursor/*.mdc .cursor/rules/

Updating

To get the latest rules:

rm -rf .cursor/rules
npm reinstall @crimsonsunset/cursor-config

Releasing

Version Management

# Patch version (bug fixes, rule improvements)
npm version patch

# Minor version (new rules, significant updates)
npm version minor

# Major version (breaking changes)
npm version major

Publishing Process

  1. Test locally first:

    # Test in another project
    npm pack
    cd ../test-project
    npm install ../cursor-config/crimsonsunset-cursor-config-X.X.X.tgz
  2. Publish to npm:

    npm publish
  3. Verify publication:

    npm view @crimsonsunset/cursor-config

Release Checklist

  • [ ] Test installation in clean project
  • [ ] Verify all .mdc files are included in package
  • [ ] Check postinstall script works correctly
  • [ ] Update version in package.json
  • [ ] Publish to npm
  • [ ] Test installation from npm registry

Troubleshooting Releases

  • 403 Forbidden: Version already exists, bump version first
  • Missing files: Check .npmignore and package.json files array
  • Postinstall fails: Test script locally with node scripts/install.js

License

MIT