expo-design-system

原文涵盖的主题

• Expo Design Systems
• References
• Adopt Before You Build
• The Theme
• Colors
• Spacing
• Typography
• Radius

Make every screen in an app draw from one visual source of truth: a token theme and a small set of reusable components. This skill defines where tokens live, what they cover, how reusable components are shaped, and when a repeated view earns promotion into the system. Sibling skills own the layers around this one: expo-native-ui - platform styling rules (HIG, semantic colors, controls, shadows syntax). Follow it for what values look native; follow this skill for where values live and how they're reused. expo-project-structure - folder skeleton for new apps. For Tailwind projects, keep tokens in global.css as CSS variables and follow the styling library's own setup guidance. The scales and naming in this skill still apply; only the storage format changes. Consult these resources as needed: In an app that already has screens, the first move is detection, not construction. Before writing any token file: 1. Look for a declared system. Check package.json for a styling library - NativeWind/Tailwind, Tamagui, Restyle, Unistyles, styled-components. Then look for a token file: theme.ts, src/theme/, constants/theme.ts, or constants/Colors.ts (the create-expo-app default). 2. If one exists, i

这里只展示节选，请以完整原文和当前要求为准。