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

promptos-cli

v1.0.0

Published

PromptOS CLI — prompt refinement for AI coding assistants

Readme

PromptOS CLI

The PromptOS CLI is an interactive wrapper that helps you refine your natural language prompts into highly structured, context-rich prompts before passing them to your favorite AI coding assistant (like Claude, Gemini, Cursor, etc.).

Setup Instructions

  1. Ensure the PromptOS Backend (phase-1-backend) is running.
  2. Navigate to the CLI directory:
    cd phase-2-cli
    npm install
  3. Set up your environment variables:
    cp .env.example .env
    (Ensure PROMPTOS_API_BASE_URL points to your running backend, usually https://prompt-os-dusky.vercel.app)

Authentication (Development)

Because the full frontend dashboard is not yet deployed, you can use the built-in development authentication flow to get started immediately.

  1. Open a new terminal and navigate to the backend to generate a test token:
    cd phase-1-backend
    python generate_test_token.py
  2. Copy the output JWT token.
  3. Inject the token into your local CLI keychain:
    cd phase-2-cli
    node index.js dev-login <YOUR_TOKEN>

Usage

You can run the CLI using node index.js (or you can link it globally with npm link to just type promptos).

1. Interactive Refinement (Default)

Asks you a few targeted questions to extract context (files, errors, expectations) before assembling the final prompt.

node index.js ask "fix the auth bug"

2. Auto-Run with an AI Tool

You can automatically pass the refined prompt to another CLI tool (e.g. claude or gemini).

node index.js run claude "build a navbar"

Shortcuts available:

node index.js claude "build a navbar"
node index.js gemini "build a navbar"

3. Custom Conversation Modes

Control how interactive the refinement process is:

  • --basic: Limits the AI to a maximum of 3 questions.
    node index.js run claude "fix the database schema" --basic
  • --skip: Skips the interactive questions entirely. It takes your raw prompt, structures it automatically (0-shot), and immediately passes it to the tool.
    node index.js run claude "write a regex for emails" --skip

4. Check Your Usage Stats

View your token savings, time recovered, and session history:

node index.js stats

Testing Your Environment

To quickly verify that your CLI, backend, and authentication are correctly hooked up, run the built-in diagnostic test tool:

node test-cli.js