superpowers-sage:sage-design-system

Convert design references into Tailwind v4 tokens and Blade UI components.

13|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/hekivo/superpowers-sage --skill superpowers-sage-sage-design-system-hekivo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: superpowers-sage:sage-design-system
Source: https://github.com/hekivo/superpowers-sage/tree/main/skills/sage-design-system
Command: npx skills add https://github.com/hekivo/superpowers-sage --skill superpowers-sage-sage-design-system-hekivo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents Sage theme development from stalling by turning raw design references into a validated, end-to-end visual foundation (tokens, UI atoms, and layout structure) before implementing blocks or pages.

Core Features & Use Cases

  • Token-first design system foundation: convert design tool specs into Tailwind v4 @theme tokens and resources/css/design-tokens.css with traceability.
  • UI atoms + structural layouts: generate Blade UI components (atoms) and layout components (structure-only) so the rest of the theme can be built consistently.
  • Visual verification via kitchensink: create a kitchensink view and take a Playwright screenshot to validate that every component variant and layout renders correctly.
  • Design-to-code workflow guidance: follow phased instructions for token extraction, component implementation phases, and structural layout composition with guardrails.

Quick Start

Invoke /sage-design-system with your design tool URL or path (or use detect) and wait until the tokens file, the 5 UI atoms, the 5 layout components, and the validated kitchensink screenshot are present and committed.

Frequently Asked Questions about superpowers-sage:sage-design-system

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert Figma design references into Tailwind v4 theme tokens?

You can convert Figma design references into Tailwind v4 theme tokens by extracting design specs into a `resources/css/design-tokens.css` file with full token traceability for your Sage theme.

What is the best way to set up a design system for a Sage theme?

The best way to set up a Sage design system is to generate Blade UI component atoms and structural layouts, establish Tailwind v4 @theme tokens, and validate the visual rendering with a Playwright kitchensink screenshot.

Does this design system workflow require Playwright for visual validation?

Yes, Playwright is required to take screenshots of a generated kitchensink view, validating that every UI component variant and structural layout renders correctly before committing the visual foundation.

Can I resume a partially completed Sage design system setup if some files already exist?

Yes, you can resume a partially completed Sage design system setup because the workflow detects existing files and supports continuing from any partially completed phase without overwriting your progress.

How do I validate Blade UI component variants before building Sage theme pages?

You validate Blade UI component variants by generating a dedicated kitchensink view route, taking a Playwright screenshot to verify every component renders correctly, and requiring a dedicated commit before continuing architecture.

When do I need to establish a Tailwind v4 token foundation for Roots Sage development?

You need to establish a Tailwind v4 token foundation during initial Sage project setup or before any architecture and build work when design validation is missing, preventing theme development from stalling.