Skip to content

/style-tune

/style-tune is the explicit slash-command form of the style-tune skill. The skill also auto-triggers on natural-language phrases (“warmer button”, “more elevated cards”), so you rarely need to type the slash command — but it’s available when you want to be explicit about scope.

/style-tune <subject> <modifier(s)>
/style-tune button softer warmer
/style-tune primary "tone down"
/style-tune card "more elevated"
/style-tune input sharper

Or, equivalently, just write the intent in chat:

Make the button feel softer and warmer. Tone down the primary color a touch. More elevated cards.

The skill edits one of two layers:

LayerTargets
Theme rolesprimary, accent, danger, warning, info, success, brand
Component tokensbutton, card, alert, dialog, input, nav

These match the canonical mappings in the style-tune skill:

ModifierTarget tokensEffect
warmer--*-bg, --color-*Hue shift toward amber (≈ +15–30°)
cooler--*-bg, --color-*Hue shift toward blue (≈ −15–30°)
softer--*-radiusRadius × 1.5 (min 4px)
sharper--*-radiusRadius × 0.5 (min 0)
larger / bigger--*-font-size, --*-padding-*× 1.125
smaller--*-font-size, --*-padding-*× 0.875
bolder--*-bg / --color-* chromaChroma × 1.2
subtler / muted / tone down--*-bg / --color-* chromaChroma × 0.8
more elevated--*-shadowNext shadow step up
flatter--*-shadowNext shadow step down (or removed)
  1. Identify the subject and modifiers, then route to the theme or component layer.
  2. Locate the relevant theme files or component SCSS.
  3. Compute adjustments — colours via oklch_shift.py, spatial tokens via canonical multipliers.
  4. Apply edits with validation:
    • Theme changes are pre-validated for WCAG contrast in a temp directory; failures roll back the entire batch.
    • Component edits also run a WCAG pre-check on the affected token against its typical background role, and preserve var() wrappers and fallbacks.
  5. Re-validate the file structure and surface drift hints.
  6. Print a summary table — modifier, token, old value, new value, status.