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

designmaxxing

v0.1.2

Published

Pixel-perfect UI reverse engineering toolkit — extract design tokens, components, and layout from any web app

Downloads

301

Readme

designmaxxing

Pixel-perfect UI reverse engineering toolkit. Extract design tokens, components, and layout from any web app and turn them into actionable design system assets.

Quick Start

npx designmaxxing extract https://stripe.com/payments

Installation

# Global
npm install -g designmaxxing

# Per-project
npm install --save-dev designmaxxing

# Claude Code integration
npx designmaxxing install-claude

CLI Reference

extract <url>

Navigate to a URL with a headless browser and extract design data.

designmaxxing extract https://example.com [options]

| Option | Default | Description | |--------|---------|-------------| | --modules <list> | all | Comma-separated modules: visual,typography,layout,components,assets,animations,behavior,framework,network | | --breakpoints <list> | 375,768,1024,1280,1536 | Comma-separated viewport widths | | -o, --output <dir> | ./designmaxxing-output | Output directory | | --auth-cookies <file> | — | Path to cookies JSON for authenticated pages | | --selector <css> | — | Limit extraction to elements matching CSS selector | | --full-page | true | Extract entire page (not just viewport) | | --no-headless | — | Run browser in headed mode | | --timeout <ms> | 30000 | Navigation timeout in milliseconds | | --wait-for-selector <css> | — | Wait for this selector before extracting |

tokens <dir>

Generate design tokens from extracted data.

designmaxxing tokens ./designmaxxing-output [options]

| Option | Default | Description | |--------|---------|-------------| | --format <type> | all | json, css, tailwind, scss, or all | | -o, --output <dir> | Same as <dir> | Output directory for token files |

report <dir>

Generate a visual HTML (or Markdown) design system report.

designmaxxing report ./designmaxxing-output [options]

| Option | Default | Description | |--------|---------|-------------| | --format <type> | html | html or markdown | | --open | — | Open report in browser after generation | | --no-screenshots | — | Skip embedding screenshots |

verify <original-url>

Visual regression comparison between the original site and a rebuild.

designmaxxing verify https://original.com --rebuild https://my-rebuild.com [options]

| Option | Default | Description | |--------|---------|-------------| | --breakpoints <list> | 375,768,1024,1280,1536 | Comma-separated viewport widths | | --threshold <ratio> | 0.02 | Max acceptable pixel diff ratio (0–1) | | -o, --output <dir> | ./designmaxxing-verify | Output directory |

cleanup [dir]

Remove extraction output directories.

install-claude

Install the /designmaxxing skill and AI agents into Claude Code.


Programmatic API

import { extractAll } from 'designmaxxing'

const manifest = await extractAll({
  url: 'https://example.com',
  modules: ['visual', 'typography', 'layout'],
  breakpoints: [375, 768, 1280],
  output: './my-output',
  headless: true,
  fullPage: true,
  timeout: 30000,
  viewport: { width: 1280, height: 800 },
})

console.log(manifest.results) // { visual: 'visual.json', typography: 'typography.json', ... }

Claude Code Integration

After running designmaxxing install-claude, the /designmaxxing skill is available in Claude Code.

/designmaxxing https://stripe.com/payments

This orchestrates four agents in sequence:

| Agent | Role | |-------|------| | extractor | Runs the CLI and captures all design data | | analyzer | Reads the extraction output and identifies the design system | | reconstructor | Generates components matching the original | | verifier | Runs designmaxxing verify and reports diff results |


Configuration

Create .designmaxxingrc in your project root:

{
  "breakpoints": [375, 768, 1024, 1280, 1536],
  "modules": ["visual", "typography", "layout", "components", "assets", "animations", "behavior"],
  "output": "./designmaxxing-output",
  "headless": true,
  "fullPage": true,
  "timeout": 30000,
  "viewport": { "width": 1280, "height": 800 }
}

See .designmaxxingrc.example for the full annotated reference.


Output Structure

designmaxxing-output/
├── manifest.json          # Links all results + metadata
├── visual.json            # Colors, shadows, borders, spacing
├── typography.json        # Type scale, font faces
├── layout.json            # Grid/flex configs, breakpoints
├── components.json        # Component inventory with states
├── assets.json            # Asset inventory (fonts, images, SVGs)
├── animations.json        # Transitions and keyframes
├── behavior.json          # Scroll behavior, forms, events
├── framework.json         # Tech stack detection
├── network.json           # API endpoints observed during load
├── tokens.json            # Generated design tokens
├── tokens.css             # CSS custom properties (:root {...})
├── tokens.tailwind.ts     # Tailwind theme extension
├── tokens.scss            # SCSS variables
├── report.html            # Visual HTML design system report
├── analysis.md            # Markdown summary
└── screenshots/
    ├── breakpoint-375.png
    ├── breakpoint-768.png
    └── breakpoint-1280.png

Troubleshooting

Playwright not installed

npx playwright install chromium

Auth-gated pages

Export your session cookies from the browser (e.g. using a browser extension), save as cookies.json, then:

designmaxxing extract https://app.example.com --auth-cookies cookies.json

SPA not rendering

designmaxxing extract https://example.com --wait-for-selector ".main-content"

CORS font blocking

Expected — font URLs are still captured in typography.json, but the font files themselves won't download. This is normal.

Slow extraction

Limit to only the modules you need:

designmaxxing extract https://example.com --modules visual,typography

Requirements

  • Node.js ≥ 18
  • Chromium (auto-installed by Playwright on first run)