cardeo/rapid-design-system

Rapid Design System (RDS) is a methodology document for product teams that need a design system but want to avoid building something heavy or slow. It describes a practical approach: start with the theme settings your existing UI library already provides, use design tokens to capture shared decisions, and only build custom components when nothing existing can be made to work. The core argument is that most teams overshoot. They write custom components, create elaborate processes, and end up with a system so complex it slows down the product work it was meant to support. RDS proposes starting lighter: configure what you have, validate choices at runtime, and establish clear rules about who can change what. The boundary between a token change and a new component is treated as a deliberate governance decision rather than something each developer resolves differently. The methodology is written to work with any major React component library. Material UI, Radix, shadcn, Ant Design, Chakra, and Mantine are all mentioned as compatible starting points, as are custom internal UI kits. There is no code to install. The entire repo is a set of Markdown documents organized into sections covering topics like Token vs Component, Component Readiness Audit, Runtime First, and Composition Over Abstraction. A separate section addresses how AI coding tools should interact with the system without generating speculative or out-of-scope components. The README also references a companion decision-making framework called SWARM, described as optional. SWARM provides a structured thinking loop for moments when a team is uncertain about the next design decision. RDS defines what to do, SWARM covers how to think through the choice. If you are a designer, PM, or developer trying to bring some order to a product team's UI without setting up a formal design system from scratch, this repo is a starting point for thinking through the trade-offs.