In case it helps, here's the typical utils config I rock with in most of my projects: gist.github.com/mark-tomlins...
06.03.2026 09:31
👍 0
🔁 0
💬 0
📌 0
In case it helps, here's the typical utils config I rock with in most of my projects: gist.github.com/mark-tomlins...
Good question!
All of them need to be defined in the config because sugarcube can't know in advance which CSS property you want.
If you want utils that are not token-based (e.g. `.absolute`), you can extend sugarcube with a unocss preset like this:
sugarcube.sh/docs/utiliti...
You're not the first person to have run into that! And even I've been like 'hey where's my utils' a couple of times 🤣.
That is certainly high praise - thank you. And thanks for using it.
😂 Let's help you the old fashioned way!
1. `npx @sugarcube-sh/cli init` to get you setup
2. `npx sugarcube generate` to generate your styles
3. Import the generated CSS files wherever you import the rest of your styles.
Let me know if that gets you sorted!
Appreciate it, Jesse. When I was designing this, CSS-first was one of about four non-negotiables. No proprietary syntax, no CSS-in-JS, none of it. Just CSS.
Your Personal Design Systems idea sounds great and not very far from what I'm trying to do here. Hope to see it.
A design system, titled "Set.studio: Pattern Library" with a sidebar of navigation, broken into design tokens, CSS, components and regions. The open pattern is the "BrandSlide", which shows a red slide, titled "Ready, set, go!". In the footer of the slide, it says "Design and development partnership proposal, February 2026", followed by next and previous slide links.
POV you've got a new major version of your internal design system software and @sugarcube.sh to test and a proposal to make.
CSS is the best design tool innit.
Thank you and right back at you: builtbyfield.com is so clean.
Hello, world.
Sugarcube is now available for use.
sugarcube.sh
Check it out on GitHub
github.com/sugarcube-sh...
Or on @npmx.dev
npmx.dev/org/sugarcub...
Thanks for following along :)