design system builder

Design Community

Skill notes

When to use

Right after nextjs-scaffold has set up the project When user wants to change the whole site's visual direction When restyling an existing site to a new mood

When NOT to use

User wants one-off style changes (just edit the file directly) User has a detailed design spec from a designer (follow that instead)

Inputs

From site-plan.md: mood (one of 8 - see references/palettes.md) vertical (for font fine-tuning)

Output

Updated files: src/app/globals.css - palette + typography + spacing tokens src/lib/constants.ts - brand colors as constants (optional) Design tokens documented in a comment block

1. Warm luxury

Palette: cream #FDF8F0, gold #C9A96E, charcoal #2C2418, taupe #D4C5B2 Fonts: Bodoni Moda (display) + Inter (body) Feel: fine dining, spa, boutique

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Design
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Read mood from site-plan.md

If no mood picked, ask `AskUserQuestion` with the 8 options. Show preview colors.

02
Step 2: Update globals.css

Replace the `@theme inline` block with the palette for the chosen mood. Keep the structure from `nextjs-scaffold/templates/globals.css.template`. Do NOT touch the force-override `!important` rules at the bottom.

03
Step 3: Update layout.tsx fonts

Replace the `next/font/google` imports to match the mood's font pairing. Use the `variable:` prop to wire them up to CSS vars.

04
Step 4: Add spacing + elevation tokens

In `globals.css`, add these tokens (8pt grid + 3-tier elevation):

05
Step 5: Add interactive state matrix

For each mood, document the state colors in globals.css comments:

06
Step 6: Reduced motion

Already handled in template globals.css. Verify `@media (prefers-reduced-motion: reduce)` block exists.

07
Step 7: Typography scale

Default scale for display fonts (mood-dependent): Hero: `text-5xl sm:text-6xl md:text-7xl lg:text-8xl` Section heading: `text-3xl md:text-4xl lg:text-5xl` Subsection: `text-xl md:text-2xl` Body: `text-base` (16px) with `leading-relaxed`

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.