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

@specdrive/cli

v0.1.2

Published

SpecDrive CLI — frontend spec-driven development

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

anuraghqanuraghq

Keywords

Readme

@specdrive/cli

SpecDrive CLI — frontend spec-driven development for Flutter, Next.js, and React Native.

Kiro-style workflow: requirements → gap-analysis → design → tasks → implement → review

Install

npm install -g @specdrive/cli
# or run without global install
npx @specdrive/cli --help

Quick start

cd your-frontend-project

spec init --stack flutter          # or nextjs | react-native
spec create "Product Review Screen" --quick

# Or gated workflow
spec create "Product Review Screen"
spec approve requirements --spec product-review-screen
spec gap-analysis --spec product-review-screen
spec approve gap-analysis --spec product-review-screen
spec design --spec product-review-screen
spec approve design --spec product-review-screen
spec tasks --spec product-review-screen
spec implement --spec product-review-screen --next

CLI vs MCP

| Mode | Who generates specs | API keys | |------|---------------------|----------| | CLI | SpecDrive calls free LLM (Gemini → Groq → Ollama) | GEMINI_API_KEY in shell profile | | MCP | Cursor/Claude host AI | Your IDE API key |

For Cursor/Claude, use @specdrive/mcp instead.

Environment

export GEMINI_API_KEY="your-key"    # free at https://aistudio.google.com
export FIGMA_TOKEN="figd_..."       # optional, for Design2Code integration
export SPECDRIVE_LLM_OFFLINE=1        # template-only mode (no AI)

Commands

| Command | Description | |---------|-------------| | spec init | Initialize .specdrive/ in project | | spec create | Create a new feature spec | | spec gap-analysis | Compare requirements vs codebase | | spec design | Generate design.md | | spec tasks | Generate tasks.md | | spec implement | Show next task context (--auto-figma for UI) | | spec review | Review code against design.md | | spec doctor | Check project health | | spec figma | Figma → code via Design2Code |

Links

License

MIT