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

@getdesign/cli

v0.1.3

Published

Generate production-ready design.md specs from live websites in your terminal.

Downloads

570

Readme

@getdesign/cli

Generate production-ready design.md specs from live websites in your terminal.

@getdesign/cli captures a rendered landing page, analyzes its visual system, and writes a Cursor-ready design.md with colors, typography, layout, components, motion, and implementation guidance.

Usage

DAYTONA_API_KEY=... OPENAI_API_KEY=... bunx @getdesign/cli https://cursor.com
bunx @getdesign/cli https://linear.app --out design.md
bunx @getdesign/cli --url https://example.com --site-name Example --out ./designs

The binary runs on Bun. Install Bun first if bunx is not available: https://bun.sh/docs/installation.

When --out is omitted, the CLI writes to a deterministic local run folder: ./getdesign-runs/<slug>/design.md. This keeps generated files out of the repo root while avoiding confusion with the package name.

Options:

  • --url <url> or positional <url>: source URL to analyze.
  • --site-name <name>: override the detected site name.
  • --out <path>: write markdown to a file or directory. File paths are written exactly; existing directories or paths ending in / receive design.md. Without --out, output is written to ./getdesign-runs/<slug>/design.md.
  • --daytona-api-key <key> / DAYTONA_API_KEY: Daytona key for this run.
  • --openai-api-key <key> / OPENAI_API_KEY: OpenAI key for this run.
  • --text-only-fallback: continue with CSS/text-only output if visual capture is unavailable.

Progress is streamed to stderr as concise phase updates (crawl, capture, visual, describe, extract, synthesize, render) so stdout and generated files stay clean.

For tests or embedding, import runGetdesignCli from ./runGetdesign.ts and pass argv, env, cwd, or now instead of relying on global process defaults.

  • Web · getdesign.app
  • API · api.getdesign.app
  • CLI · @getdesign/cli
  • SDK · @getdesign/sdk

MIT © getdesign