@sarunyu/system-one 4.7.1 → 4.7.2

package/llms.txt

@@ -86,26 +86,15 @@ Two issues arise:
    `@layer base`. Let the library supply these — they resolve to standard
    white/dark/gray values that work correctly with the library's components.
 
-2. **Brand overrides must be in a separate file imported after the library**
-   — the library emits its design tokens as unlayered CSS. Any override in
-   `index.css` (even at the bottom) loses because the library is imported
-   after `index.css`. Put brand overrides in a dedicated file imported last:
+2. **Do NOT create a `theme-overrides.css`** unless the user explicitly asks
+   to change the brand color. The library's default P1 blue works out of the
+   box. An overrides file is only needed when a custom brand palette is
+   required — see the Theming section below.
 
-```css
-/* src/theme-overrides.css */
-:root {
-  --primary-action: #4f46e5;
-  --primary-action-hover: #4338ca;
-  --primary-action-active: #3730a3;
-  --font-sans: "Inter", system-ui, sans-serif;
-}
-```
-
-The `src/main.tsx` import order for Lovable:
+The `src/main.tsx` import order for Lovable (two lines only):
 ```tsx
 import "./index.css";                        /* Tailwind v3 layers first */
-import "@sarunyu/system-one/styles.css";     /* library — flat/unlayered CSS, beats any @layer */
-import "./theme-overrides.css";             /* brand overrides — last, so they win */
+import "@sarunyu/system-one/styles.css";     /* library — unlayered, beats any @layer */
 ```
 
 ## Dark mode

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sarunyu/system-one",
-  "version": "4.7.1",
+  "version": "4.7.2",
   "type": "module",
   "description": "A production-ready React design system built for AI-powered web generation tools (Figma Make, Lovable, V0). Tailwind CSS v4 + CSS custom properties for full theming support.",
   "keywords": [