emcn-design-review

Audit UI code against the emcn design system for conformance.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/tunacosgun/sim --skill emcn-design-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: emcn-design-review
Source: https://github.com/tunacosgun/sim/tree/main/.agents/skills/emcn-design-review
Command: npx skills add https://github.com/tunacosgun/sim --skill emcn-design-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Align UI code with the emcn design system to prevent deviations in components, tokens, and patterns across the project.

Core Features & Use Cases

  • Validate components are imported from the emcn barrel, ensuring consistent usage
  • Enforce CSS variable token usage and design-token conventions across styles
  • Audit PRs and code changes for conformance to design-system rules and provide actionable feedback

Quick Start

Review the current PR scope against the emcn guidelines and propose fixes.

Frequently Asked Questions about emcn-design-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit UI code for design system conformance during a PR review?

Auditing UI code for design system conformance involves checking component imports against barrel exports and enforcing CSS variable token usage. This detects styling deviations and provides actionable feedback to align frontend codebases with established design rules.

What are design tokens and how do they enforce UI consistency in frontend code?

Design tokens are CSS variables that enforce UI consistency by standardizing styling practices across frontend codebases. Auditing token usage ensures components conform to design system rules, preventing visual deviations and maintaining unified patterns.

Can I use this to check component imports and styling across my frontend codebase?

Yes, you can check component imports and styling across any frontend codebase. The audit applies broadly to detect deviations in component imports and styling practices, ensuring barrel exports and token-based CSS variables are used correctly.

Why should I use barrel exports for UI components in my design system?

Using barrel exports for UI components ensures consistent usage and conformance within the design system. Auditing imports prevents deviations by centralizing component access, simplifying token-based styling validation and maintaining architectural integrity across the project.

What is the best way to enforce CSS variable token conventions in frontend code?

The best way to enforce CSS variable token conventions is to audit UI code against design-system rules. This detects non-conforming styling practices and provides actionable feedback to replace hardcoded values with standardized design tokens.