expo-design-system

Builds and audits token-based design systems for Expo React Native apps.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Taquit/Life-Manager --skill expo-design-system-taquit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expo-design-system
Source: https://github.com/Taquit/Life-Manager/tree/main/double_m_react/.agents/skills/expo-design-system
Command: npx skills add https://github.com/Taquit/Life-Manager --skill expo-design-system-taquit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Expo apps often accumulate design-system drift: hardcoded hex colors, arbitrary spacing values, raw font sizes, and inconsistent component APIs scattered across screens. This Skill establishes a single visual source of truth through a token theme and reusable component conventions, and audits existing apps for drift. ## Core Features & Use Cases - Token Theme Creation: Defines design tokens for color, spacing, typography, radius, shadows, and motion under a single theme entry point, using platform semantic colors that adapt to light and dark modes. - Reusable Component Conventions: Standardizes shared components with variant, size, state, and style-override props, plus rules for when a repeated view earns promotion into the shared component library. - Drift Auditing: Provides grep-based checks, a scoring rubric, and an incremental adoption plan to measure and fix hardcoded style values in an existing app. - Use Case: When building a new finance app screen, use this Skill to ensure the screen draws colors, spacing, and typography from the theme instead of introducing one-off literals, then run the audit to confirm no drift was introduced. ## Quick Start Ask the AI to set up a design token theme and reusable button component for your Expo app following the expo-design-system conventions.

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 design tokens under a single theme directory such as src/theme/ with files for colors, spacing, typography, radius, shadows, and motion, re-exported through one index entry point. Use platform semantic colors via Platform.select so values adapt to light and dark modes automatically.

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

Run grep-based checks for hardcoded hex colors, raw fontSize values, non-scale spacing numbers, 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, then spacing, then colors.

When should I extract a repeated view into a shared component?

Extract a view 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 it stepwise from inline JSX to a screen-local component to the shared components directory, never speculatively.

Does this work with NativeWind, Tamagui, or Restyle?

Yes, but the existing styling library remains the source of truth and is extended in its own idiom, token names, and config format. Never introduce a second token system beside an existing one, as that creates drift rather than adoption.

Why should screens avoid hardcoded colors and spacing values?

Hardcoded literals bypass the single source of truth, causing inconsistent corners, shadows, and accents across screens. Any visual value used twice belongs in the theme; only genuinely one-off adjustments may stay inline with an explanatory comment.