Arena

Arena by Dravensoft

One design system, in React and in Angular, from one contract.

MIT License · Token-driven design system for React, Angular and Tailwind.

What you get

Components with a contracted API. The same components under both framework names, rendering the same pixels, over one shared Tailwind layer. What a member is called, what it takes, what it defaults to and what it means are written in contracts/api/, and each layer's types and tables are generated from there, so the two layers cannot drift apart quietly. Every value a component draws resolves through a design token, so no hex and no bare pixel sits anywhere inside one.

Accessibility bound per component instead of audited per release. Each component declares which pattern it implements, most of them from the WAI-ARIA Authoring Practices: the roles it carries, the keys it answers, where focus lands, what dismisses it. A requirement it does not meet yet is recorded beside it with its reason, and bun run check:behaviour fails on the day a component stops answering the pattern it named.

A style kernel, which is what a project answers to look like itself. The questions about shape, space, weight and depth are Arena's; the answers are a style plugin the project writes, and the appearance Arena installs with is one such plugin rather than a floor under them. Palettes and fonts sit in an arena.config.json, which the arena command each package ships turns into the one stylesheet a package cannot carry: Arena carries the language and never the skin, and none of its own colours reach your build. A project that starts from an existing look takes a row of plugin-style-store/catalogue/INDEX.md: the catalogue lists style plugins measured on real products, one row each.

Metadata for a product that has to be found, which most products do not. The Angular layer writes the document from the routes it is handed, at @dravensoft/arena-angular/metadata: title composition, a description, a canonical and the og:* pair, with no route indexed until it says so. That import path is a second entry point, so a project that never asks for metadata never installs the router behind it. React writes no at all, and both layers publish the breadcrumb trail they draw in schema.org terms.

Why an agent can operate it

An API is a contract file rather than a paragraph, and so is the pattern a component binds and the role a style plugin answers; a gate holds the code, the documentation and the published packages to them. An agent handed this repository does not guess at Arena: it reads the contract that governs what it is about to write, and the gate tells it when it got it wrong.

That is also what makes the rules enforceable rather than aspirational. Each of these is decided in contracts/design/AGENTS.md and handed to a builder by skills/design/SKILL.md, which states each one in full and says which of them a gate reads your own sources for.

• Tokens are the only styling layer.
• Only a class of the vocabulary goes on an Arena component.
• Appearance is a class of the vocabulary, never a member.
• Danger is outline, never filled.
• One primary accent per view.
• No gradients, on any surface.
• No emoji, in product or in copy.
• Icons are Phosphor class-name strings, drawn by Arena's components or by ArenaIcon; a raw ph-* element paints nothing.
• Never wrap an Arena component in your router's own link.
• An anchor Arena draws splits its activations.
• A press that starts on a control keeps to that control.
• Two themes, dark first.
• A chart carries identity or meaning, never both.
• Copy is formal and direct, in the product's language.
• A required member absent is a caller bug.
• No render follows from whether you bound a listener or filled a slot.
• A few components answer with a method rather than a member.

Install

bun add @dravensoft/arena-react     # or @dravensoft/arena-angular

That is the whole install. Bun installs the peers a project lacks. A manager that installs no peer, Yarn among them, needs them named, as the commands in install.md do. No icon font is a peer: arena build writes the sprite that ArenaIcon draws from. install.md lists the commands per layer, and the layer page below says which peers each package declares.

Then run npx --no-install arena init (or pnpm exec arena init, or bunx --no-install arena init), which copies an example arena.config.json and wires the build scripts, and import what arena build writes. skills/design/references/install.md is where it starts, for React and for Angular, and it links the config and the command. The pages npm shows are an introduction and a table of questions that link the same references.

Over MCP

{

"mcpServers": { "arena": { "command": "npx", "args": ["-y", "@dravensoft/arena-mcp"] } } }

@dravensoft/arena-mcp is where the language travels. It serves the router, the references and every component document to an agent that speaks the Model Context Protocol, as resources and as tools, and the layer it serves is the one your project installed. The component packages carry the code, the stylesheets and the contracts your own markup answers to, and none of the prose.

A corpus and the components it describes are two packages and two version numbers, so they can disagree. arena_start reads the version of the Arena package in your project, compares it with the server's, and says so when the two differ. Where they do, the components are right and the text is old.

As a Claude Code plugin

/plugin marketplace add dravensoft-dev/arena

/plugin install arena@dravensoft /reload-plugins

Update

/plugin marketplace update dravensoft   # refresh the catalog: learns a new version exists

/plugin update arena@dravensoft # update the plugin you actually have /reload-plugins # apply it to the running session

A version means one commit. Each release is served from its git tag, with the marketplace entry pinning source.ref to vX.Y.Z.

As a standalone Agent Skill

Hand any agent skills/design/SKILL.md. It is the router, and it answers each question with one file. It routes over this tree, so an agent handed the file alone has the questions and reaches the answers by URL; one handed the clone or the plugin reaches them by path.

A component package is code, and the language reaches an agent by one of the three routes above. Install the MCP server, install the plugin, or hand over the skill, and the agent gets the guidelines, the contracts and every component's usage document, which is what turns "integrate Arena" into a task it finishes on its own.

See it

[arena.dravensoft.org](https://arena.dravensoft.org) carries the design guidelines, the kitchen sink, and a playground page for every component, with no clone and nothing to install.

The same pages come up locally with bun run demos, from the same list, and scripts/build/AGENTS.md says what a fresh clone has to build before they mean anything.

An agent reads [`llms.txt`](https://arena.dravensoft.org/llms.txt) first, which routes to the rules of the language and then to one corpus per framework, React and Angular. They are separate on purpose: every component ships under both names and the two documents are not interchangeable.

Dependencies

• Fonts are self-hosted, and no CDN request is made. Arena ships the Archivo / Familjen Grotesk / Spline Sans Mono .woff2 binaries in assets/fonts/, and contracts/design-generated/fonts.generated.css declares them with @font-face, so they load from the same origin as the page that reads them. A package consumer names their own three families in arena.config.json, where src is either a font file, which arena build cuts to what the product paints, or a stylesheet URL.
• Icons are [Phosphor Icons](https://phosphoricons.com) (MIT), and no icon font is bundled. Every component takes a Phosphor class string and draws the glyph through ArenaIcon, from the sprite arena build writes. A raw ph-* element needs @phosphor-icons/web installed by the project. See Iconography.

Which version am I getting

The two packages and the plugin do not always carry the same number, because a package publishes only when something it ships changed. skills/design/references/versioning.md explains what that means.

Latest project artifacts

• Repo/Claude Code plugin: 13.0.0
• npm React package
• npm Angular package
• npm contracts package

Where to go next

Which job is this? The two audiences read almost disjoint sets of these files, and starting on the wrong branch is how a short question turns into a long read.

Building something with Arena. skills/design/SKILL.md is the router. From it: frameworks/INDEX.md is every component in one read and frameworks/ /INDEX.md is the same list under your own framework's names, each component's .prompt.md is how to use that one, and skills/design/references/install.md is how to install it.

Working on Arena itself. AGENTS.md is the root of that branch, and everything below is reached through it.

• scripts/build/AGENTS.md: compile Arena for the first time, meaning what a machine has to already carry, what a fresh clone must build before bun run demos or bun run check mean anything, and why some generated files are tracked and some are not. Linux and macOS are the two supported platforms; on Windows the supported path is WSL2, with the clone in the Linux filesystem.
• frameworks/PACKAGING.md: the npm channel, meaning how the two packages are assembled from the tree in place, why a published Arena carries no skin, and what the consumer declares instea