pattern-enforcement

You enforce design system consistency by loading user-declared patterns from a JSON file at session start. The Skill applies these patterns as hard constraints during component generation, CSS edits, and layout changes, reporting violations with pattern IDs and rule texts.

UI pattern drift happens when component generation and CSS edits lack automated constraint validation. Without an enforcement mechanism caching locked design patterns at session start, interface decisions gradually deviate from the established design system rules.

You validate UI code changes against locked design patterns by activating the enforcement Skill during any modifications touching components, CSS, or layout. It caches declared patterns at session start and surfaces violations with pattern IDs and corresponding rule texts.

Yes, the design-reviewer agent integrates directly with pattern enforcement. The Skill automatically applies locked design patterns as constraints when the design-reviewer agent runs, ensuring all UI reviews validate against your declared pattern rules.

Yes, you need a .claude/design-patterns.json file containing your declared patterns. The Skill reads this JSON file at session start, caches the patterns for the active session, and uses them to enforce constraints across all UI development commands.

Yes, color-scheme validation is supported as an optional feature within the pattern enforcement workflow. When enabled, the Skill validates color choices against your declared design patterns during component generation and CSS modifications.