expo-design-system

Builds and audits design token themes and reusable components for Expo React Native apps.

16|1|Updated May 5, 2026
One-click install
npx skills add https://github.com/AIBiz-Automatyzacje/workspace-template-mobile --skill expo-design-system-aibiz-automatyzacje
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expo-design-system
Source: https://github.com/AIBiz-Automatyzacje/workspace-template-mobile/tree/main/.claude/skills/expo-design-system
Command: npx skills add https://github.com/AIBiz-Automatyzacje/workspace-template-mobile --skill expo-design-system-aibiz-automatyzacje

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Expo apps often accumulate visual drift: hardcoded hex colors, arbitrary spacing values, and inconsistent component APIs scattered across screens. This Skill establishes a single visual source of truth — a token theme (colors, spacing, typography, radius, shadows, motion) plus a small set of reusable components — and provides a grep-based audit to measure and fix drift in existing apps. ## Core Features & Use Cases - Token Theme Architecture: Defines where tokens live (src/theme/), what they cover (semantic platform colors, 4-point spacing grid, platform-mirrored type ramp, radius, boxShadow strings, motion durations), and rules like "every repeated visual value is a token". - Reusable Component Contract: Standardizes variants, sizes, pressed/disabled/loading states, and style-override merging for shared primitives, with explicit criteria for when a repeated view earns promotion into src/components/. - Design System Audit: A reference guide with grep checks, per-100-SLOC scoring rubric, incremental adoption plan, and templates for documenting or proposing components. - Use Case: When building a new Expo screen or reviewing an AI-generated one, run the self-critique pass (hierarchy, proximity, repetition, alignment) and move any escaped literal values into the theme instead of patching the screen. ## Quick Start Ask the AI to audit my Expo app for design system drift and create a token theme from the values it finds.

Frequently Asked Questions about expo-design-system

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

FAQPage Schema
How do I create a design token theme in an Expo app?

Place all tokens under src/theme/ with files for colors, spacing, typography, radius, shadows, and motion, re-exported through one index.ts entry point. Use a 4-point spacing grid, platform semantic colors via Platform.select, and a type ramp mirroring Apple text styles.

How do I audit an Expo app for design system drift?

Run grep checks for hardcoded hex colors, raw fontSize, non-scale spacing values, raw borderRadius, and legacy shadow props outside the theme directory. Score each category as escapes per 100 source lines, then migrate incrementally starting with typography.

When should I extract a view into a shared component?

Promote a view to src/components/ only when it appears in two or more screens, has a nameable role like Card or EmptyState, and its props API is smaller than its implementation. Move one step at a time and never extract speculatively.

Does this work with NativeWind or Tamagui instead of plain StyleSheet?

Yes, but you extend the existing styling library in its own idiom rather than adding a second token system. For Tailwind projects, tokens live in global.css as CSS variables while the same scales and naming apply.

Why should shadows use boxShadow instead of elevation in React Native?

Legacy shadow props and elevation are banned in favor of boxShadow strings, which work consistently across platforms. Define two or three elevation levels as tokens, such as card, raised, and overlay.