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

@coveord/plasma-llms

v60.2.1

Published

LLM-friendly documentation for the Plasma design system

Readme

@coveord/plasma-llms

LLM-friendly documentation for the Plasma design system, Coveo's Mantine-based component library.

Inspired by Mantine's llms.txt guide, this package generates static documentation files optimised for consumption by AI tools and large language models.

What's included

| File | URL | Purpose | | --------------------------- | ---------------------------------------------------- | ---------------------------------------------------------------------------- | | llms.txt | https://plasma.coveo.com/llms.txt | Index of all components (compact, llmstxt.org format) | | llms-full.txt | https://plasma.coveo.com/llms-full.txt | All component docs concatenated into a single file | | llms/components/Button.md | https://plasma.coveo.com/llms/components/Button.md | Per-component reference (props, sub-components, design guidelines) | | llms/content/Voice.md | https://plasma.coveo.com/llms/content/Voice.md | Per-guideline reference for user-facing content | | plasma-skill.md | https://plasma.coveo.com/plasma-skill.md | Portable AI agent skill with Plasma conventions and lookup guidance |

Using Plasma with AI coding agents

See the canonical AI Coding Agents guide for skill installation, MCP server configuration, and the documentation lookup workflow.


Development

Regenerating docs

pnpm turbo run build --filter=@coveord/plasma-llms

This reads the hand-maintained .md files from src/components/ and src/content/, copies them to dist/llms/ (stripping frontmatter), and assembles llms.txt, llms-full.txt, and plasma-skill.md.

Set PLASMA_BASE_URL to override the base URL (default: https://plasma.coveo.com):

PLASMA_BASE_URL=http://localhost:6006 pnpm build

Updating component docs

Each component has a hand-maintained src/components/ComponentName.md file. These are the source of truth for all LLM-facing documentation.

When a component's API changes, use the internal plasma-component-docs skill to update the spec. It knows the expected format and conventions. You can also edit the files manually.

Adding a new component

  1. Create src/components/NewComponent.md with YAML frontmatter and Markdown content. Use the plasma-component-docs skill to generate the initial spec.
  2. Run pnpm build to regenerate the dist outputs

How it works

  1. src/build.ts reads all *.md files from src/components/ and src/content/, parses YAML frontmatter, and copies body content to dist/llms/
  2. src/llms-txt.ts builds the index from component and content guideline metadata
  3. src/llms-full-txt.ts concatenates all component and content guideline docs into one file
  4. src/skill.md is the source for the AI agent skill served as plasma-skill.md; the build replaces its {{BASE_URL}} placeholders

Do not edit generated files in dist/ manually.