Emil Kowalski proposes lint rules and failing CI checks for design systems
Emil Kowalski proposes enforcing design systems with lint rules, typed props, semantic tokens and failing CI checks. He also describes agent audits against documented design rules.

TL;DR
- Design-system misuse should fail builds, argues AI for UI instructor Emil Kowalski in his enforcement proposal.
- Tailwind has a concrete enforcement option: Kowalski links to a design-system linter for teams keeping utility classes.
- Written design rules can become an audit rubric: Kowalski suggests scoring a page out of 10 and reporting fixes.
The linter Kowalski links can enforce rules on third-party components without forks. His skills catalog also has a UI stress test for long names and unusual emails, plus an animation review that returns an approval or a block.
Lint rules and failing CI
Kowalski lays out four requirements for agents working inside a design system:
- Lint rules and strict, type-safe props to constrain component usage.
- CI checks that fail when a component is misused.
- Documentation explaining when and how each component should be used.
- Semantic tokens that express a token's role.
The build-breaking check is the sharpest part of the proposal.
Kowalski makes the case conditional: a team with strong design judgment, such as Linear, might not need a design system, he says in a follow-up. Teams trying to build quickly without that shared judgment may need one.
Tailwind lint errors
For teams retaining Tailwind, Kowalski points to @shadcn/lint.
The project's documented rules work with Tailwind v4 and do not require shadcn/ui:
no-restyle: catches unauthorized component restyling throughclassName.no-raw-colors: catches raw colors such asbg-pink-500.no-arbitrary-values: catches values such asp-[13px].no-inline-styles: catches inline styling.no-unknown-classes: catches classes Tailwind cannot generate, such asrounded-huge.require-static-classes: catches class construction the linter cannot read, such asbg-${color}.
A configured Button contract can reject className="p-4" and tell the agent to use its size prop. The error can list existing sizes and point to the component file, giving the agent a repair path grounded in the design system.
Oxlint support has a documented limit: it reads Vue and Svelte script blocks, not their templates.
Agent design audits
Kowalski also proposes using documented design rules as criteria for an agent-run review. His example produces:
- A page rating out of 10.
- A report identifying what matches the rules and what needs fixing.
For supplying the design-system context, he suggests design.md plus MCP, with skills as an optional extra.
19 UI skills
Kowalski's public catalog organizes 19 skills into five workflow groups, also visible in a shared screenshot:
- Before building: Animation Vocabulary, Pick a UI Library, Prototyping, Ask Emil.
- Building the interface: Design Engineering, Animate, Choreograph, Apple Design, Gestures, Mobile Native.
- Refining and reviewing: Animation Performance, Break UI, Review Animations.
- Whole-app work: Find Opportunities, Improve Animations, Remove Animations.
- Other skills: Animate Expo, Ask Sonner, Learn Taste.
The published installer is:
Demo recording with package-my-work
Kowalski also demonstrated /package-my-work as an update for AI for UI students. The skill handles:
- Recording at the appropriate resolution.
- Cursor and touch indicators, including their movement.
- Zooming into key details.
- Presentation techniques drawn from his own demo-making workflow.