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

@konradreyhe/promptm

v1.2.0

Published

Individualize AI coding prompts for your projects. Install as Claude Code slash commands.

Readme

promptm

npm version Tests License: MIT Node.js

16 battle-tested AI coding prompts, installed as slash commands in Claude Code. Type /kickoff, /debug-rootcause, /security-audit and get structured, opinionated workflows.

Optionally individualize them per project — generic "read the codebase" becomes specific "read src/app.module.ts, CLAUDE.md, and check tsconfig.json."

Table of Contents

Quick Start (30 seconds, no API key)

npx @konradreyhe/promptm install-generic .

That's it. Open Claude Code in your project and type /kickoff.

What You Get

| Command | What it does | |---------|-------------| | /kickoff | Start session — read everything, understand context first | | /debug-rootcause | Find the REAL cause. 5 WHYs technique. Fix cause, not symptom | | /feature-build | Structured feature implementation with incremental steps | | /code-review | Pre-commit quality gate with security checklist | | /verify-thorough | Be 100% sure. Trace every path. Trust nothing | | /security-audit | Full OWASP Top 10 mapped security review | | /refactor | Safe restructuring — characterization tests first, small steps | | /test-write | Write comprehensive tests. Happy path, edge cases, error cases | | /performance | Profile first, optimize second. Never guess the bottleneck | | /deploy-checklist | Pre-deployment validation. Every time. No exceptions | | /housekeeping | Cleanup, organize, consolidate — leave it better | | /research-investigate | Deep dive, brainstorm, plan with all context | | /quick-task | Small focused task, no heavyweight protocol | | /architect | Design before you build. Constraints first, then options, then decide | | /think-plan | Deep reasoning, plan with checkpoints, self-correct, adapt as you go | | /low-context-handover | Emergency context save when running low |

Every template supports $ARGUMENTS — pass context directly:

/debug-rootcause TypeError in UserService.create()
/feature-build add dark mode toggle
/refactor extract auth logic from UserController

Three Ways to Use

1. Generic (no API key)

npx @konradreyhe/promptm install-generic .

Installs all 16 templates as-is. Works great for any project.

2. Individualized (no API key needed)

npm install -g @konradreyhe/promptm
promptm scan .
promptm generate myproject
promptm install myproject

If you have Claude Code installed, generate auto-detects it — no API key, no flags. Prompts get tailored to your project's stack, files, and conventions.

3. Individualized via API (bulk operations)

mkdir -p ~/.promptm && echo "ANTHROPIC_API_KEY=sk-ant-..." > ~/.promptm/.env
promptm generate myproject
promptm install myproject

Uses Claude API directly. Faster for many projects (5 templates in parallel). Falls back to Claude Code automatically if no key is set.

How Individualization Works

promptm scans your project (package.json, folder structure, CLAUDE.md, configs) and sends that context + each template to Claude. Supports Node.js, Python, Go, Rust, Java (Maven/Gradle), C# (.NET), and Docker. Generic instructions become project-specific.

Real example — /debug-rootcause reproduction step:

Generic template:

## Step 2: Reproduce It
- Find the exact steps to trigger the issue
- Find the minimal reproduction
- Document the reproduction steps

After individualization (from a real project — React + Remotion + Express):

## Step 2: Reproduce It
- Find the exact steps to trigger the issue
- Find the minimal reproduction
- Document the reproduction steps

Project-specific reproduction workflow:
  # For video generation issues
  npm run dev                    # Open Remotion Studio
  npx remotion render video/index.ts CompositionName output/test.mp4

  # For web UI issues
  cd web && npm run dev          # Start frontend

  # For API issues
  npm run api:dev                # Start Express server

  # For test failures
  npm test                       # Run Vitest

The generic template is 113 lines. The individualized version is 191 lines — all project-specific commands, file paths, and gotchas. Across 16 templates, that's hundreds of lines of context your AI assistant would otherwise have to figure out each session.

All Commands

promptm install-generic [path]  # Instant setup – no API key needed
promptm templates               # List all 16 templates
promptm scan <path>             # Auto-detect & register project
promptm generate <project>     # Individualize via API or Claude Code
promptm install <project>      # Install as slash commands
promptm refresh <project>      # Rescan + regenerate + install (one step)
promptm install-all             # Install into all projects
promptm regenerate-all          # Refresh all after template changes
promptm list                    # List registered projects
promptm stats                   # Overview dashboard
promptm rescan <project>       # Re-scan (preserves manual edits)
promptm update <project>       # Update context fields
promptm copy <proj> <tmpl>     # Copy prompt to clipboard
promptm show <proj> <tmpl>     # View in terminal
promptm diff <proj> <tmpl>     # Compare original vs individualized
promptm new-template <name>    # Create custom template scaffold
promptm remove <project>       # Delete project

Custom Templates

promptm new-template my-workflow
# Edit templates/my-workflow.md
promptm regenerate-all --template my-workflow
promptm install-all

Keeping Prompts Up to Date

When your project evolves (new deps, new files, new conventions):

promptm refresh myproject    # rescan + regenerate + install in one step

Or for all projects:

promptm regenerate-all -y && promptm install-all

Troubleshooting

"command not found: promptm"

Global install didn't link properly. Use npx instead:

npx @konradreyhe/promptm install-generic .

Or reinstall globally:

npm install -g @konradreyhe/promptm

"No API key and Claude Code not found"

For generate, promptm needs either:

  1. An Anthropic API key in ~/.promptm/.env, or
  2. Claude Code installed and accessible via claude in your terminal

If you just want the templates without individualization, use install-generic instead.

Slash commands don't appear in Claude Code

Make sure you ran install (or install-generic) in the right project directory. Claude Code reads from .claude/commands/ relative to your project root.

ls .claude/commands/    # should list .md files

Templates look generic after install-generic

That's expected. install-generic copies templates as-is. For project-specific prompts, use scan + generate + install.

FAQ

Do I need an API key? No. install-generic works with zero configuration. For individualization, promptm auto-detects Claude Code — no API key needed unless you want parallel generation via the API.

Does this work with Cursor / other AI editors? The slash commands are specific to Claude Code's .claude/commands/ convention. The template markdown files themselves work anywhere — copy and paste them into any AI assistant.

How much does individualization cost? About $0.01–0.02 per template (16 templates ≈ $0.15–0.30 total per project). One-time cost unless you regenerate.

Can I edit individualized prompts after generation? Yes. They're plain markdown in .claude/commands/. Edit freely. Running install again will overwrite them, so keep custom edits in a separate copy if needed.

Requirements

  • Node.js 18+
  • Claude Code (for using slash commands)
  • Anthropic API key (optional — only for API-based individualization)

Contributing

See CONTRIBUTING.md for development setup and guidelines.

Security

See SECURITY.md for reporting vulnerabilities.

License

MIT — see LICENSE.