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

@ternent/ui

v0.6.0

Published

A collection of Vue components and themes for ternent applications

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

ternentdevternentdevternebotternebot

Keywords

Readme

ternent-ui drop-in AI pack

This pack is designed to be copied directly into the ternent-ui package root.

What this gives you

  • a clear v2 architecture for src/primitives
  • strict AI governance docs
  • token and theming rules
  • primitive and accessibility rules
  • a pattern boundary so product UI does not leak into the core
  • ready-to-paste prompts for Codex or similar agents
  • templates for component specs and PR review
  • a concrete phased roadmap

Assumptions this pack makes

  • src/components/S* is legacy and should be frozen except for urgent maintenance
  • src/primitives/* is the future design-system source of truth
  • Tailwind is retained as the styling implementation layer
  • Ark UI is used selectively for interactive/a11y-heavy primitives
  • multiple branded themes remain a first-class requirement

Suggested first move

  1. Copy the contents of this pack into the ternent-ui repo.
  2. Commit the docs before any major refactor so AI has a stable contract.
  3. Start Codex with ai/prompts/00-master-system-prompt.md.
  4. Then run the prompts in order.

Suggested placement

  • src/design-system/docs/* should live exactly where provided.
  • ai/prompts/* and ai/templates/* can live at package root or be moved under .ai/ if you prefer.
  • plans/* can stay at package root or be copied into your internal docs area.

Recommended execution order

  1. ai/prompts/00-master-system-prompt.md
  2. ai/prompts/01-bootstrap-docs.md
  3. ai/prompts/02-button-hardening.md
  4. ai/prompts/03-form-primitives.md
  5. ai/prompts/04-choice-controls.md
  6. ai/prompts/05-dialog-and-overlays.md
  7. ai/prompts/06-navigation-and-disclosure.md

Grounding notes for this repo

This pack was written to match the current shape of ternent-ui as shared:

  • legacy src/components/S*.vue
  • new src/primitives/Button/*
  • token css under src/design-system/tokens.css
  • multi-theme setup under src/themes/*
  • existing token names like --ui-bg, --ui-fg, --ui-surface, --ui-primary, --ui-critical, --ui-ring

The docs intentionally allow a staged migration rather than forcing an immediate token rename.