packages/eclipse/README.md
Eclipse is Prisma's comprehensive design system built with Tailwind CSS and design tokens from Figma.
For complete documentation, examples, and interactive demos, visit:
Eclipse Design System Documentation
pnpm add @prisma/eclipse
Use Tailwind v4 PostCSS plugin in the app (or re-export a shared config):
// postcss.config.mjs
export default {
plugins: {
"@tailwindcss/postcss": {},
},
};
Initialize Tailwind once in the consuming app, then import Eclipse styles:
/* app global.css */
@import "tailwindcss";
@import "@prisma/eclipse/styles/globals.css";
import { Button } from "@prisma/eclipse";
export function App() {
return <Button variant="ppg">Click me</Button>;
}
Eclipse uses an app-owned Tailwind setup:
tailwindcss once.@prisma/eclipse/styles/globals.css) provides tokens, utilities, and @source directives.This avoids duplicate base/utilities output and keeps CSS generation in one place.
Do not import tailwindcss from multiple library stylesheets. Only import it from the app entry stylesheet.
Recommended pattern:
@import "tailwindcss";
@import "@prisma/eclipse/styles/globals.css";
/* other library/theme css */
eclipse/
āāā src/
ā āāā components/ # React components
ā āāā lib/ # Utilities (cn, etc.)
ā āāā styles/ # Global CSS
ā āāā tokens/ # Design tokens
ā āāā index.ts # Main entry
āāā .templates/ # Component templates
āāā ARCHITECTURE.md # Architecture overview
āāā GETTING_STARTED.md # Setup guide
āāā TOKENS.md # Token documentation
āāā TROUBLESHOOTING.md # Common issues
For maintainers working on Eclipse itself:
When adding new components or tokens, please refer to the documentation files above and ensure changes are reflected in the main documentation site.
For questions or issues, please reach out to the Prisma design team or open an issue on GitHub.