Skip to content

StyleSeed

v2.1.1 Feature

This release adds 3 notable features for engineering teams evaluating rollout.

✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

ai-coding ai-design ai-ui claude-code claude-design claude-skills
+14 more
cursor design-judgment design-system design-tokens nextjs radix-ui react react-components shadcn shadcn-ui tailwindcss typescript ui-design vibe-coding

Summary

AI summary

Updates What We Added, What Went Wrong, and text-sm across a mixed release.

Full changelog

Critical: Tailwind v4 Font Size Anti-Patterns

Documented from a real production incident. If you tokenize font sizes as CSS variables, Tailwind v4 will break your UI.

What Went Wrong

  • text-[var(--text-sm)] → Tailwind interprets as color, not font-size → color: 13px (invalid)
  • --text-* CSS variables → conflict with Tailwind v4's internal --text-* namespace
  • Changing --font-size in theme.css → breaks all rem-based spacing (icons, nav, buttons)

What We Added

  • CLAUDE.md: Font Size Anti-Pattern section with 3 ✗ and 1 ✓ pattern
  • DESIGN-LANGUAGE.md: CRITICAL warning after typography rules
  • Prohibited Practices: explicit rules against font-size tokenization
  • /ss-lint: New check that detects text-[var(-- pattern automatically

The Rule

✓ ALWAYS: text-[36px], text-[18px], text-[13px]  (explicit px)
✗ NEVER:  text-[var(--text-sm)]                    (CSS variable)
✗ NEVER:  --text-sm: 13px in theme.css             (Tailwind conflict)

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track StyleSeed

Get notified when new releases ship.

Sign up free

About StyleSeed

All releases →

Related context

Beta — feedback welcome: [email protected]