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

pds-stack

v3.0.3

Published

The design-first AI workflow for Product Designers who ship.

Downloads

445

Readme

⬡ PDS Stack

The design-first AI workflow for Product Designers who ship.

npm version license


Install

npx pds-stack install

Answer 7 questions. Get a complete AI agent system configured for your project in under 5 minutes.

Requires Node.js 18+ and Claude Code.


What is PDS Stack?

Every AI development framework treats design as a downstream artifact. You write code. Then you check if it looks right.

PDS Stack inverts this.

The designer's creative judgment is the system's quality gate — not one input among many. Before a single line of code runs, a Quality Brief must exist and be validated. This is not a formality. It is an architectural constraint the entire system enforces.


The agents

| Agent | Role | Trigger | |---|---|---| | RAY | Architect & Strategist — challenges ideas, writes tiered specs T1/T2/T3, creates ADRs | /ray | | BOB | Builder & Quality Director — generates Quality Brief (gate), implements via 6-step Ralph Loop | /bob | | ANALYZER | Product QA & CX — scores /20, enforces release gate, writes cumulative learnings | /analyzer | | EVE (discovery module) | Validates the problem before the brief — 5 questions max | /eve | | SHIP (delivery module) | Closes the loop post-verdict — release doc + KPI tracking | /ship |


What gets generated

your-project/
├── STACK.md                    ← Your stack config — read by all agents
├── CLAUDE.md                   ← Agent registry + hard constraints
│
└── agent-system/
    ├── agents/                 ← RAY, BOB, ANALYZER (+ EVE, SHIP if installed)
    ├── context/                ← client_vision.md, roadmap.md, design_guide.md
    ├── adr/                    ← Architecture Decision Records
    ├── specs/                  ← active/, shipped/, dropped/, epics/
    ├── learnings/              ← ANALYZER writes here, RAY reads here
    └── PROJECT_BRIEF_TEMPLATE.md

The Quality Brief

Before BOB writes a single line of code, it generates a creative contract:

[BOB] ⏸ Quality Brief — Feature F-001

Type: aesthetic
Direction: Minimal editorial card — hierarchy through spacing, not decoration.
The 3 words: Quiet · Deliberate · Grounded
Constraints: No gradients. No rounded corners beyond 4px.
Reference: Linear issue card · Vercel dashboard

Awaiting validation. No code before explicit approval.

Brief types (set in STACK.md): aesthetic · performance · content · architecture


STACK.md — your config

framework: nextjs
language: typescript
ui_lib: shadcn
strict_mode: true
line_cap: 150
motion_default: L0
quality_brief_type: aesthetic

modules:
  core: true
  discovery: false
  delivery: false
  design: true
  epic: false

language_agents: en    # en | fr

Quick start

# 1. Install
npx pds-stack install

# 2. Fill context files
#    agent-system/context/client_vision.md
#    agent-system/context/roadmap.md

# 3. Run RAY
/ray "I want to build [feature]"

# 4. Validate the spec, then run BOB
/bob "implement feature_[ID]"
# BOB generates a Quality Brief — approve it, then implementation begins

# 5. Run ANALYZER
/analyzer "evaluate feature_[ID]"
# Score /20 + learnings written automatically

Links


PDS Stack V3 · MIT License · Built by @aminelamine