Components for high-stakes screens
Copy-paste React for surfaces where being wrong is expensive. Every chart is SVG-only, every colour is a token, and every file is yours after install.
Everything a dense screen already needs
Nine categories, built to be composed rather than configured. Pick a shelf and the registry hands you the files.
npx shadcn@latest add \ https://ssych.com/r/react-templates.json # the files land in your tree — yours to edit, # reading your tokens, with no chart runtime
Built like the screens it is for
SVG-only charts
Every chart is hand-drawn SVG. No Recharts, no chart runtime in your bundle, nothing to version against.
Tokens, never hex
Every colour reads a CSS token, so a component dropped into your app wears your palette on arrival.
The files are yours
The registry hands you TypeScript source into your own tree. Edit it, delete it; there is no package to fight.
Dark-first, both themes
Designed on near-black, and every token pair resolves in light. Flip the class and the screen follows.
Composed, not configured
Small parts with real props instead of one component with forty options. Screens are compositions.
Whole screens included
The dashboards are the same parts composed, published as pages you can lift wholesale.
Whole screens, not just parts
7 dashboards showing the components composed. The page composes and never edits them, which is the whole discipline.
The balance-first book on one ruled grid: holdings, history and share-of-total composed from six library components, with the page composing and never editing them.
Questions, answered
Through the shadcn CLI: one command per category, and the registry serves the files straight into your tree. No account, no package.