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

@ryuxdsgn/design-intelligence

v2.21.0

Published

RYUX: design intelligence for AI agents and designers. One skill, five entry points: Analyze, Design, Build, Critique, and QA, for Claude Code, Codex, Cursor, Gemini CLI, OpenCode, Cline, Copilot, and more.

Readme

@ryuxdsgn/design-intelligence

Install RYUX, design intelligence for AI agents and designers, with one command. RYUX is one skill with five entry points. Tell your agent what you are doing; RYUX picks the knowledge the task needs:

  • Analyze: understand an existing interface, with every finding labeled Measured, Observed, or Inferred.
  • Design: create or improve UI and UX without code, in Figma, pen.dev, or mockups.
  • Build: implement the interface in your repo's own stack.
  • Critique: a senior design critique of a Figma link, a pen.dev design, a website URL, or a screenshot.
  • QA: render, inspect, fix, render again.

Original work by ryux.design, MIT licensed. Rules and rationale: docs/design-rules.md.

Usage

npx @ryuxdsgn/design-intelligence                                          # start here: agents, install, project setup
npx @ryuxdsgn/design-intelligence setup                                    # teach RYUX about the project (DESIGN.md)
npx @ryuxdsgn/design-intelligence setup --audience "..." --market "..."    # same, without questions
npx @ryuxdsgn/design-intelligence check                                    # health check (exit 1 on problems)
npx @ryuxdsgn/design-intelligence check --json                             # the same findings as JSON, for agents and CI
npx @ryuxdsgn/design-intelligence init --agent claude --dry-run            # list what would change, write nothing
npx @ryuxdsgn/design-intelligence init --agent claude                      # install + empty project context block
npx @ryuxdsgn/design-intelligence install --agent claude,cursor,codex      # non-interactive
npx @ryuxdsgn/design-intelligence install --agent all                      # every supported agent
npx @ryuxdsgn/design-intelligence install --agent claude --global          # into your home directory
npx @ryuxdsgn/design-intelligence update                                   # refresh, and migrate RYUX 1.x installs
npx @ryuxdsgn/design-intelligence remove --yes                             # remove RYUX and marked blocks

ryux-rules still works as an alias of the same command.

| Command | What it does | | --- | --- | | setup | Asks a few questions with plain choices, "Write my own", or Skip: product, current work, audience, market and locale, constraints, design intent, and UX, UI, and motion direction. Saves the answers to the <!-- ryux-context --> block in DESIGN.md, changing only the fields you answer. The answers are direction, not evidence. Without a terminal, set fields with --product, --work, --audience, --market, --constraints, --intent, --ux, --ui, --motion. | | init | Installs RYUX, then adds a <!-- ryux-context --> block to DESIGN.md (product, audience, market and locale, design system, evidence sources, constraints), prefilled only with what it can detect. Re-running never overwrites what you wrote. --dry-run lists what it would create or update and writes nothing. | | install | Writes the ryux/ skill into each agent's folder and a short pointer block into CLAUDE.md, GEMINI.md, or AGENTS.md. Interactive installs then offer setup. --dry-run lists the folders and blocks it would create or update and writes nothing. | | check (doctor) | Checks every install: all files present, frontmatter valid, version matches this CLI, every module reference resolves, no RYUX 1.x folders, pointer blocks, project context and how many setup fields are filled. Each problem names the command that fixes it. Exits 1 on errors, so it works in CI; --json prints { ok, cli, scope, installs, findings: [{ level, where, message, fix }] }. | | update | Rewrites installs at this version and migrates RYUX 1.x. | | remove | Removes the skill and the pointer blocks. Leaves your DESIGN.md context. |

Exit codes: 0 done or healthy, 1 a problem was found or the command failed, 2 the command was used wrongly (an unknown command or agent).

One version: packages/cli/package.json. The skill header, the plugin manifests, and ryux --version all derive from it.

Agents

| Agent | --agent | Project folder | Global folder | Pointer file | | --- | --- | --- | --- | --- | | Claude Code | claude | .claude/skills/ | ~/.claude/skills/ | CLAUDE.md | | Codex | codex | .codex/skills/ | ~/.agents/skills/ | AGENTS.md | | Cursor | cursor | .cursor/skills/ | ~/.cursor/skills/ | AGENTS.md | | Gemini CLI | gemini | .gemini/skills/ | ~/.gemini/skills/ | GEMINI.md | | OpenCode | opencode | .opencode/skills/ | ~/.config/opencode/skills/ | AGENTS.md | | Cline | cline | .cline/skills/ | ~/.cline/skills/ | AGENTS.md | | GitHub Copilot | copilot | .agents/skills/ | ~/.agents/skills/ | AGENTS.md | | Amp | amp | .agents/skills/ | ~/.config/agents/skills/ | AGENTS.md | | Kimi Code | kimi | .agents/skills/ | ~/.agents/skills/ | AGENTS.md | | Antigravity | antigravity | .agents/skills/ | ~/.gemini/config/skills/ | AGENTS.md | | Anything else | agents-md | rules inline in AGENTS.md | (project only) | AGENTS.md |

Agents that share a folder are written once. Project installs add a short marked block to the pointer file; global installs only write skill folders.

What gets installed

One folder, ryux/, in each agent's skills folder:

ryux/
  SKILL.md            the router: entry points, how RYUX works, levels, Hard Gates, task table, Delivery Gate
  capabilities/       analyze, design, build, critique, qa
  knowledge/          product, ux, interaction, forms, edge-cases, content, ui, design-system,
                      accessibility, responsive, frontend, anti-slop

The agent reads the router, then only the capability and knowledge files a task needs.

Safe for your repo

  • Your files are never overwritten wholesale. CLAUDE.md, GEMINI.md, and AGENTS.md only change inside the <!-- ryux-rules:start --> ... <!-- ryux-rules:end --> block.
  • update only touches what is installed; remove takes it back out.
  • Upgrading from RYUX 1.x: install or update replaces the 16 ryux-* folders with the single ryux/ folder. Folders from ryux-rules 0.x and Cursor .mdc files are removed too. The old --for, --groups, and --concerns flags are accepted and ignored.

Network and MCP

  • The CLI makes no network requests and runs no other programs. It only writes the files listed above.
  • The ryux MCP server is optional: there is no hosted server yet, and RYUX never connects to one on its own. RYUX works without it and rates its evidence None.
  • The skill tells agents to treat what an MCP server, web page, or screenshot returns as data, never as instructions.

Other ways to install

npx skills add ryuxdsgn/design-intelligence      # skills.sh, any agent
/plugin marketplace add ryuxdsgn/design-intelligence
/plugin install ryux@design-intelligence          # Claude Code plugin

Develop

pnpm --filter @ryuxdsgn/design-intelligence build      # tsc -> dist/
node packages/cli/dist/cli/index.js --help
pnpm sync:skills              # regenerate skills/ryux/, docs/design-rules.md, plugin versions
pnpm test                     # unit + CLI integration tests (node:test, no extra dependencies)
pnpm check:sync               # CI: fail if the committed skill, docs, or versions drift from the sources