design-tokens

This is a pnpm monorepo that publishes three independently-versioned packages for Kong UI design systems.

Packages

Package	Description	Version
@kong/design-tokens	Konnect design tokens
@kong/stylelint-plugin-design-tokens	Stylelint plugin for Kong design token rules
@kong/eslint-plugin-design-tokens	ESLint plugin for Kong design token rules

Getting Started

Install dependencies from the repo root:

pnpm install

Workspace Scripts

Script	Description
pnpm build	Build all packages
pnpm lint	Lint all packages
pnpm typecheck	Typecheck all packages
pnpm sandbox:design-tokens	Open the Konnect tokens sandbox
pnpm commit	Create a conventional commit

Building a single package

pnpm --filter @kong/design-tokens build

Contributing

See each package's README for token structure, development workflow, and contribution guidelines.

This repo uses Conventional Commits. Run pnpm commit to create a guided commit message.

Releases are managed by lerna-lite in independent mode — each package is versioned and published automatically.

Committing Changes

This repo uses Conventional Commits.

Commitizen and Commitlint are used to help build and enforce commit messages.

It is highly recommended to use the following command from the repo root in order to create your commits:

pnpm commit

This will trigger the Commitizen interactive prompt for building your commit message.

Enforcing Commit Format

Lefthook is used to manage Git Hooks within the repo.

• A commit-msg hook is automatically setup that enforces commit message standards with commitlint
• A pre-push hook is used that runs eslint before allowing you to push your changes to the repository

Additionally, CI will use commitlint to validate the commits associated with a PR in the Lint and Validate job.

Agentic reviewer

View the reference for the /muthur agentic reviewer

Approvals

• All pull requests require review and approval from authorized team members.
• Automated approvals through workflows are strictly prohibited.
  • There is an exception for automated pull request approvals originating from generated dependency updates that satisfy status checks and other requirements.
• Protected branches require at least one approval from code owners.
• All status checks must pass before a pull request may be merged.

Package Publishing

Packages are published automatically via lerna-lite in independent mode. Releases are triggered by conventional commits on main, alpha, and beta branches.