What problem does it solve? Contributors to the ThemeKit SwiftUI design system need to build new atoms, molecules, and organisms that stay stateless, brand-neutral, and fully token-fed, but generic SwiftUI advice (MVVM, ViewModels, hardcoded colors) conflicts with the library's house rules. This Skill encodes the exact architectural conventions so new components compose, theme, localize, and mirror RTL correctly from the start. ## Core Features & Use Cases - House rules enforcement: Six non-negotiable rules covering stateless value-type views, init-for-content plus chainable copy-on-write modifiers for appearance, and token-only colors, radius, spacing, and typography. - Copy-pasteable patterns: Reference templates in references/patterns.md for an atom with semantic style enums, a molecule with locale-aware formatting, and a style-driven organism using protocol + configuration + type erasure. - Slots and chrome styles: A canonical slot vocabulary (header, footer, leading, trailing, label, indicator) and the ChromeStyle pattern letting host design systems own paint while ThemeKit keeps behavior and accessibility. - Use Case: When asked to add a new Badge variant or build a SeatMap organism under Sources/ThemeKit/Components, the Skill produces code that reads the theme from the environment, supports Dynamic Type, localizes strings, and passes the PR checklist. ## Quick Start Ask the AI to create a new ThemeKit component, for example: "Add a Tag atom to ThemeKit with semantic styles and chainable modifiers following the library conventions."