oa-design

Implements the Open Analytics design language with type-checked React component recipes and CSS tokens.

132|5|Updated Aug 20, 2026
One-click install
npx skills add https://github.com/OpenLabs-so/oa-design --skill oa-design-openlabs-so
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oa-design
Source: https://github.com/OpenLabs-so/oa-design/tree/main/skills/oa-design
Command: npx skills add https://github.com/OpenLabs-so/oa-design --skill oa-design-openlabs-so

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires motion, react, tailwindcss, and includes references (resource) components.

What problem does it solve? Building a dashboard, SaaS app, or landing page that feels calm, dense, and native requires hundreds of coordinated decisions about color, radius, motion, and copy. This Skill encodes the complete Open Analytics design language—every hex code, spring constant, and radius lifted from the shipped product—so an agent can reproduce it exactly instead of guessing. ## Core Features & Use Cases - Token system: One ink color derives every neutral via color-mix percentages, with light and dark themes, a multiplied radius scale, and two-shadow elevation, installable as a single _root.css block. - Twelve component recipes: Squircle cards, pressing buttons, dropdowns, tab bars with traveling highlights, modals, measured-height multi-step dialogs, pixel-matched skeletons, notice strips, floating pills, toasts, header morphs, and scroll reveals—each with full type-checked React source embedded. - Motion vocabulary: Seven named springs (PANEL, LAYOUT, POP, POP_EXIT, BANNER, FLICK, CHART) cover the entire product, with rules for enter/exit asymmetry and reduced-motion support. - Use Case: Ask your agent to build a settings screen or analytics dashboard; it applies the squircle surface anatomy, fixed-height card grids, and plain-spoken copy voice so the result matches the Open Analytics look. ## Quick Start Use the oa-design skill to build a dashboard stats page with squircle cards, a tab bar, and skeleton loading states following the Open Analytics design language.

Frequently Asked Questions about oa-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a dashboard UI that matches the Open Analytics design?

Drop the skill's _root.css token block into your global stylesheet, then follow the numbered recipe for each component you need. Each recipe contains the full type-checked React source, usage examples, and the load-bearing details like fixed card heights and spring constants.

What components are included in this design system?

Twelve recipes cover squircle cards, buttons, dropdowns, tab bars, modals, multi-step dialogs, skeletons, notice strips, floating pills, toasts, header morphs, and scroll reveals. Each embeds the same type-checked source found in the components directory.

Does this design system work with Tailwind CSS and React?

Yes, the recipes assume React with Tailwind v4 and the motion package for springs. Every value is plain CSS numbers and spring constants, so the language can be ported to other stacks if needed.

How do I add dark mode support with these design tokens?

The _root.css file includes a .dark theme that re-inks the same recipe: border percentages rise by 2 points, semantic text moves from the 700 row to the 400 row, and the primary shifts to a brighter blue. Apply the dark class to switch themes.

When should I not use this design language?

If the project already has its own design system, that system wins; the skill explicitly instructs agents to use it only to fill gaps, not overwrite an existing identity. It is also opinionated toward calm, dense analytics-style interfaces.