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

@cruglobal/cornerstone-design-system

v0.4.1

Published

Design tokens and primitives for the Cornerstone Design System.

Downloads

1,577

Readme

Cornerstone Design System

Design tokens and primitives for Cru Global's Cornerstone design system. Ships CSS custom properties, SCSS variables, ESM/CJS JavaScript, and TypeScript declarations for the Cru and FamilyLife (FL) brands across light and dark themes.


Using Cornerstone

1. Install

npm install @cruglobal/cornerstone-design-system

2. Import CSS

Import the baseline ref tokens and the file that matches your brand and theme. Apply data-brand and data-theme attributes to your root element to activate the right variables.

<!-- HTML root element -->
<html data-brand="cru" data-theme="light">
/* CSS or JS entry point */
@import "@cruglobal/cornerstone-design-system/css/ref.css";
@import "@cruglobal/cornerstone-design-system/css/cru-light.css";

| Brand | Theme | File | | --- | --- | --- | | Cru | Light | css/cru-light.css | | Cru | Dark | css/cru-dark.css | | FamilyLife | Light | css/fl-light.css | | FamilyLife | Dark | css/fl-dark.css |

For dynamic theme switching, import all mode files you need and toggle the data-theme attribute at runtime.

3. Use tokens in CSS

Tokens follow a three-layer naming convention. In most cases, use sys (semantic) tokens in your components:

.my-button {
  background-color: var(--sys-color-primary);
  color: var(--sys-color-on-primary);
  border-radius: var(--sys-number-border-radius-medium);
  font-size: var(--sys-number-font-size-body-medium);
}

Token layers:

| Prefix | Purpose | When to use | | --- | --- | --- | | --ref-* | Raw primitives (hex colors, unitless values) | Only when building custom sys aliases | | --sys-* | Semantic aliases per brand/theme | Primary choice for component styles | | --cmp-* | Component-specific tokens | When styling a specific Cornerstone component |

4. JavaScript / TypeScript

Resolved token values are available as named exports for use in JS-based styling (e.g. React Native, runtime style calculations):

// ESM
import { RefColorCruBlue500 } from '@cruglobal/cornerstone-design-system';

// Per-mode tokens
import * as cruLight from '@cruglobal/cornerstone-design-system/js/cru-light';

TypeScript declarations are included automatically.


Icons

Material Sharp

Cornerstone uses the Material Symbols Sharp icon set. Add the Google Fonts stylesheet to your app:

<link rel="stylesheet"
  href="https://fonts.googleapis.com/css2?family=Material+Symbols+Sharp:opsz,wght,FILL,[email protected],100..700,0..1,-50..200" />

Use icons with the material-symbols-sharp class:

<span class="material-symbols-sharp">home</span>
<span class="material-symbols-sharp">arrow_forward</span>
<span class="material-symbols-sharp">favorite</span>

Browse the full catalog at fonts.google.com/icons.

Cru Ministry Icons

Custom Cru ministry topic SVG icons ship with this package under libraries/cru-icons/:

node_modules/@cruglobal/cornerstone-design-system/libraries/cru-icons/<icon-name>.svg

Reference them in <img> tags or inline them as SVG. With a bundler that supports SVG imports (Vite, webpack with file-loader):

import bibleStudyIcon from '@cruglobal/cornerstone-design-system/libraries/cru-icons/bible-study.svg';

Get set up faster with Claude Code

If you're using Claude Code, Cornerstone ships a plugin with two commands. Install it once:

/plugin marketplace add CruGlobal/cornerstone-design-system
/plugin install cornerstone@cru

Then, from within your project:

  • /onboard — personalized setup instructions for your framework and build tooling.
  • /design-review — audit any UI against Cornerstone token standards, Nielsen's usability heuristics, and WCAG 2.2 AA.

Note: /pull-tokens is an internal command for syncing tokens from Figma into this repository. It is not part of the consumer plugin.


Contributing to Cornerstone

The following sections are for contributors to this repository.

Prerequisites

The /pull-tokens command syncs design tokens from the Figma source file and requires the Figma plugin for Claude Code.

  1. Run /plugins in Claude Code to open the plugin marketplace
  2. Search for Figma and install it
  3. Authenticate with your Figma account when prompted
  4. Restart Claude Code

Commands

npm run validate       # lint the token tree (exits 1 on any error)
npm run build          # compile tokens → build/ via Style Dictionary
npm run version        # consume changesets → bump package.json + write CHANGELOG.md
npm run release        # publish to npm (runs automatically via release.yml)
npx changeset          # interactively add a changeset before merging a PR
npx changeset status   # preview what the next version bump would be

build/ is gitignored. Built artifacts live only in the published npm package.

Token architecture

Tokens are organized in three layers with strict aliasing rules:

tokens/
  ref.json          # _ref.*  — raw primitives
  sys/
    cru-light.json  # _sys.*  — semantic aliases per brand × theme
    cru-dark.json
    fl-light.json
    fl-dark.json
  cmp/
    *.json          # _cmp.*  — component-level aliases

All files use W3C DTCG format ($type / $value). See CLAUDE.md for full details on aliasing rules, the build pipeline, and changeset conventions.