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

@varium/core

v0.1.4

Published

Agent-driven UI variant generation and in-browser review for React apps

Readme

@varium/core

Varium is a React toolkit for agent-driven UI variant generation and in-browser review. It gives agents a clean way to generate multiple component directions, stage them in the real page, and ask the user to choose a winner before cleaning up the temporary review state.

Install

pnpm add -D @varium/core
npx @varium/core init

After install, import the picker from the package:

import { VariantPicker } from "@varium/core";
import type { VariantMap } from "@varium/core";

What init does

npx @varium/core init asks:

  • which framework the project uses
  • which agents should be configured for this repository

It then:

  • always installs the shared skill into .agents/skills/varium/SKILL.md
  • adds .claude/skills/varium/SKILL.md and .claude/commands/varium.md when Claude Code is selected
  • adds .opencode/commands/varium.md when OpenCode is selected

The .agents skill is always written so repos have a least-common-denominator setup even when agent-specific extras differ.

Typical workflow

  1. Ask the agent to use Varium.
  2. The agent generates a sibling ComponentName.variants.tsx file.
  3. The agent mounts VariantPicker in the real page.
  4. You review the variants in development.
  5. The agent asks you to choose one variant.
  6. The agent keeps the selected component and removes the temporary review state.

Commands

After init:

  • Claude Code: /varium make a testimonial section
  • OpenCode: /varium make a testimonial section
  • Codex and other .agents-compatible runtimes: use varium to make a testimonial section

Example

import { VariantPicker } from "@varium/core";
import { variants } from "@/components/Testimonials.variants";

export default function Page() {
  return (
    <main>
      {/* VARIUM:START slot="testimonials" */}
      <VariantPicker variants={variants} slot="testimonials" />
      {/* VARIUM:END */}
    </main>
  );
}

Requirements

  • Node.js 18+
  • React 18+
  • React DOM 18+

License

MIT