expo-design-system · pproenca — скилл для Claude Code: дизайн-система Expo
Скилл expo-design-system для Claude Code помогает строить и проверять общие компоненты Expo и React Native для веба и iOS. Подключается при работе с токенами, темами и повторно используемым интерфейсом.
MIT 156 установок ★ 227 обновлён 2026-08-15
npx skills add pproenca/dot-skills --skill expo-design-system -a claude-codeЧто делает expo-design-system
Скилл задаёт правила для дизайн-системы Expo и React Native: от структуры токенов и тем до API компонентов с вариантами и слотами. Он помогает сохранять общие компоненты для веба и iOS, не заводить отдельную веб-таблицу стилей и переиспользовать уже существующие элементы.
Для стилей используется Unistyles v3; анимации и жесты работают через Reanimated и Gesture Handler, списки — через FlashList, а поверхности для рисования — через Skia. Нужны Expo SDK 53+, React Native 0.81+ и New Architecture. Скилл также задаёт правила проверки PR и управления изменениями дизайн-системы.
Какие задачи решает
- собрать токены цветов, типографики и отступов в единую тему
- спроектировать API компонентов на вариантах и слотах
- сохранить одинаковое поведение компонентов в вебе и iOS
- проверить PR на локальные токены и сырые стили
Примеры запросов агенту
- Создай тему Unistyles с токенами для цветов, типографики и отступов.
- Переработай API кнопки: используй варианты и слоты вместо произвольных стилей.
- Проверь компонент календаря на соответствие дизайн-системе и работе в вебе и iOS.
Как установить expo-design-system
1Через Skills CLI (Vercel)
npx skills add pproenca/dot-skills --skill expo-design-system -a claude-code2Вручную: положить файлы
~/.claude/skills/expo-design-system/SKILL.mdПапка скилла целиком; для одного проекта — .claude/skills/expo-design-system/
1Через Skills CLI (Vercel)
npx skills add pproenca/dot-skills --skill expo-design-system -a codex2Вручную: положить файлы
.agents/skills/expo-design-system/SKILL.mdДля всех проектов — ~/.agents/skills/
1Через Skills CLI (Vercel)
npx skills add pproenca/dot-skills --skill expo-design-system -a cursor2Вручную: положить файлы
.cursor/skills/expo-design-system/SKILL.mdCursor читает и .agents/skills/, и .claude/skills/
1GitHub CLI
gh skill install pproenca/dot-skills skills/.experimental/expo-design-system2Вручную: положить файлы
.github/skills/expo-design-system/SKILL.md1Через Skills CLI (Vercel)
npx skills add pproenca/dot-skills --skill expo-design-system -a gemini-cli2Командой платформы
gemini skills install https://github.com/pproenca/dot-skills --path skills/.experimental/expo-design-systemВручную: положить файлы
.devin/skills/expo-design-system/SKILL.mdСтарый путь .windsurf/skills/ тоже читается
Через Skills CLI (Vercel)
npx skills add pproenca/dot-skills --skill expo-design-system -a opencodeClaude.ai
Упакуйте папку в zip и загрузите в Settings → Capabilities → Skills
По шагам, с командами для каждой платформы: Как установить скилл в Claude Code: пять способов
Вопросы об expo-design-system
Как установить expo-design-system в Claude Code?
Выполни npx skills add pproenca/dot-skills --skill expo-design-system -a claude-code. Файл скилла находится по пути ~/.claude/skills/expo-design-system/SKILL.md.
Что делает expo-design-system?
Помогает создавать и поддерживать дизайн-систему для Expo и React Native: токены, темы и API общих компонентов с поддержкой веба и iOS.
Что нужно для работы expo-design-system?
Проект должен использовать Expo SDK 53+, React Native 0.81+ и New Architecture. В рекомендациях также используются Unistyles v3, Reanimated, Gesture Handler, Skia и FlashList.
Исходный текст
SKILL.md · MIT
--- name: expo-design-system description: Airbnb-DLS-aligned design system engineering for Expo / React Native apps targeting both web and native iOS, built on Unistyles v3, Reanimated, Skia, and FlashList. Use whenever building, reviewing, or refactoring shared UI — design tokens, theming, variant-driven component APIs, typography, spacing, cross-platform web/iOS parity, native-feel performance, or complex surfaces like calendars and drawing canvases (examples use a clinic app). Covers token architecture, theming, component API contracts (variants over style props), web/iOS parity (Unistyles `_web` hover/focus/cursor, Platform splits, one shared theme), the Unistyles styling engine, and governance. Trigger even when the user does not say "design system" but is creating or changing reusable React Native components, tokens, theme code, or making a component behave natively on both web and iOS. Teaches how to BUILD the design system; pair with expo-react-native-coder for features and expo-ios-hig for iOS native-feel decisions. --- # Airbnb DLS Expo React Native Design System Best Practices Opinionated, strict design system engineering for Expo / React Native apps on the New Architecture, targeting both web and native iOS. Contains 63 rules across 11 categories, prioritized by impact. Derived from Airbnb's Design Language System (DLS), the Unistyles v3 documentation, and the React Native ecosystem (Reanimated, Gesture Handler, Skia, FlashList, Expo SDK). The styling engine is Unistyles v3; the component API follows the Airbnb DLS pattern of variant props over style escape hatches. ## Mandated Architecture Alignment This skill is the **infrastructure layer** — it teaches how to BUILD the design system itself, the React Native counterpart to `ios-design-system`. All code examples follow the same non-negotiable constraints: - Feature modules import `@clinic/design-system` + `domain`; never another feature's internals - The design system owns the Unistyles theme (tokens, breakpoints) and exports a curated public surface - Reuse before you build: read the index, extend a variant, promote on the second use — never a parallel local component - Components expose variant and slot props (Airbnb DLS); no raw `style` escape hatch - Animation and gestures run on the UI thread (Reanimated worklets + Gesture Handler) - Lists use FlashList; the body-chart drawing surface uses React Native Skia - One source feels native on both web and iOS: Unistyles `_web` pseudo-states and `Platform` splits, never a forked web stylesheet - Targets the New Architecture (Fabric/JSI), Expo SDK 53+ / React Native 0.81+ ## Scope & Relationship to Sibling Skills | Sibling Skill | Its Focus | This Skill's Focus | |---------------|-----------|-------------------| | `ios-design-system` | The SwiftUI design system for the **same clinic app** | The Expo / React Native counterpart | | `expo-react-native-coder` | **Feature development** (screens, navigation, data fetching) | **Design system infrastructure** (tokens, components, theming) | | `expo-react-native-performance` | **App-wide performance** optimization | **Native-feel performance inside the design system** | | `react` | General **React** patterns | **Expo / React Native** design system specifics | | `expo-ios-hig` | **iOS native-feel** decisions (navigation, system controls, Liquid Glass) | **Cross-platform** token/component architecture + **web/iOS parity** | ## Clinic Architecture Contract (Expo / React Native) All guidance in this skill assumes the clinic modular architecture: - Feature modules depend on `@clinic/design-system` + `domain` only; the app target wires navigation (Expo Router) and dependency injection - The design system is a local package with a single public entry; raw token layers stay private - Token source of truth is the Unistyles theme; features never define local tokens - Server state uses TanStack Query: reads default to stale-while-revalidate, writes are optimistic and queued for offline sync - The New Architecture is required for Unistyles v3, Reanimated worklets, Skia, and FlashList v2 ## When to Apply Reference these guidelines when: - Setting up a design system for a new Expo / React Native app - Building token architecture (colors, typography, spacing, radius, elevation) in the Unistyles theme - Designing component APIs — variants, slots, controlled/uncontrolled state, refs, accessibility - Authoring component styles with Unistyles StyleSheet, variants, and dynamic functions - Building the calendar, treatment-note editor, or Skia body-chart drawing surfaces - Migrating ad-hoc styles to a governed token system - Reviewing PRs for raw colors, inline styles, leaked `style` props, or feature-local tokens - Tuning native feel — list virtualization, UI-thread animation, gestures, haptics, safe areas - Making a component render and feel native on both web and iOS — hover/focus/cursor, `Platform` splits, and safe-area/haptics divergences - Deciding whether to build new or reuse — checking the design system index, extending vs forking, or using a native/`@expo/ui` control instead of reimplementing one ## Rule Categories by Priority | Priority | Category | Impact | Prefix | Rules | |----------|----------|--------|--------|-------| | 1 | Token Architecture | CRITICAL | `token-` | 6 | | 2 | Theming & Adaptivity | CRITICAL | `theme-` | 5 | | 3 | Component API Contracts | CRITICAL | `api-` | 8 | | 4 | Cross-Platform Parity | CRITICAL | `platform-` | 5 | | 5 | Reuse & System Fit | HIGH | `reuse-` | 4 | | 6 | Styling Engine (Unistyles) | HIGH | `style-` | 6 | | 7 | Typography & Iconography | HIGH | `type-` | 5 | | 8 | Spacing, Layout & Safe Areas | HIGH | `space-` | 5 | | 9 | Native-Feel & Performance | HIGH | `perf-` | 7 | | 10 | Complex Domain Components | MEDIUM-HIGH | `domain-` | 6 | | 11 | Governance & Consistency | MEDIUM | `govern-` | 6 | ## Quick Reference ### 1. Token Architecture (CRITICAL) - [`token-three-layer-scale`](references/token-three-layer-scale.md) - Layer tokens as raw, semantic, and component scales - [`token-define-in-unistyles-theme`](references/token-define-in-unistyles-theme.md) - Keep the Unistyles theme as the single token source - [`token-no-raw-values-in-components`](references/token-no-raw-values-in-components.md) - Route every color and size through tokens - [`token-semantic-naming`](references/token-semantic-naming.md) - Name tokens by role, not by value - [`token-elevation-pairs`](references/token-elevation-pairs.md) - Tokenize elevation as surface and shadow pairs - [`token-avoid-over-abstraction`](references/token-avoid-over-abstraction.md) - Stop at three token layers ### 2. Theming & Adaptivity (CRITICAL) - [`theme-runtime-not-rerender`](references/theme-runtime-not-rerender.md) - Switch themes via the runtime, no re-render - [`theme-stylesheet-theme-arg`](references/theme-stylesheet-theme-arg.md) - Read theme from the StyleSheet argument - [`theme-adaptive-system`](references/theme-adaptive-system.md) - Follow the system color scheme by default - [`theme-breakpoints-responsive`](references/theme-breakpoints-responsive.md) - Use breakpoints, not Dimensions checks - [`theme-config-single-module`](references/theme-config-single-module.md) - One typed config module for themes and breakpoints ### 3. Component API Contracts (CRITICAL) - [`api-variants-over-style-prop`](references/api-variants-over-style-prop.md) - Express visual options as variant props - [`api-no-style-escape-hatch`](references/api-no-style-escape-hatch.md) - No raw style prop on components - [`api-compound-variants`](references/api-compound-variants.md) - Compound variants over per-combination components - [`api-slots-for-composition`](references/api-slots-for-composition.md) - Slot props over a prop per element - [`api-controlled-uncontrolled`](references/api-controlled-uncontrolled.md) - Support controlled and uncontrolled state - [`api-forward-ref`](references/api-forward-ref.md) - Forward refs from leaf components - [`api-accessibility-in-contract`](references/api-accessibility-in-contract.md) - Require accessibility props in the contract - [`api-aschild-polymorphism`](references/api-aschild-polymorphism.md) - Offer asChild instead of wrapper nesting ### 4. Cross-Platform Parity (CRITICAL) - [`platform-web-pseudo-states`](references/platform-web-pseudo-states.md) - Add web hover, focus, and cursor to interactive components - [`platform-guard-native-only`](references/platform-guard-native-only.md) - Guard native-only APIs behind Platform checks with web fallbacks - [`platform-divergence-split`](references/platform-divergence-split.md) - Isolate platform differences behind one component API - [`platform-input-model`](references/platform-input-model.md) - Design for pointer and touch, never hover-only - [`platform-shared-theme-parity`](references/platform-shared-theme-parity.md) - One theme for web and native, with a known divergence map ### 5. Reuse & System Fit (HIGH) - [`reuse-inventory-first`](references/reuse-inventory-first.md) - Read the design system index before writing any style - [`reuse-extend-not-fork`](references/reuse-extend-not-fork.md) - Extend a shared component with a variant, don't fork a local one - [`reuse-promote-on-second-use`](references/reuse-promote-on-second-use.md) - Promote a pattern to the system on its second use - [`reuse-platform-component-first`](references/reuse-platform-component-first.md) - Reach for a native control before reimplementing one ### 6. Styling Engine (Unistyles) (HIGH) - [`style-stylesheet-create`](references/style-stylesheet-create.md) - StyleSheet.create over inline objects - [`style-variants-api`](references/style-variants-api.md) - Variants over ternary style arrays - [`style-dynamic-functions`](references/style-dynamic-functions.md) - Dynamic functions for prop-driven values - [`style-no-inline-array-merge`](references/style-no-inline-array-merge.md) - No inline array merges in lists - [`style-withunistyles-third-party`](references/style-withunistyles-third-party.md) - Theme third-party components with withUnistyles - [`style-press-states-from-variants`](references/style-press-states-from-variants.md) - Press and disabled states as variants ### 7. Typography & Iconography (HIGH) - [`type-scale-tokens`](references/type-scale-tokens.md) - Define a named typography scale - [`type-respect-font-scaling`](references/type-respect-font-scaling.md) - Respect OS font scaling - [`type-text-component-wrapper`](references/type-text-component-wrapper.md) - Route text through one typed component - [`type-font-loading-expo-font`](references/type-font-loading-expo-font.md) - Load fonts before first paint - [`type-icon-registry`](references/type-icon-registry.md) - Centralize icons in a typed registry ### 8. Spacing, Layout & Safe Areas (HIGH) - [`space-spacing-scale`](references/space-spacing-scale.md) - Use a spacing scale on a 4pt grid - [`space-safe-area-insets`](references/space-safe-area-insets.md) - Apply safe-area insets at screen edges - [`space-touch-targets`](references/space-touch-targets.md) - Size touch targets to at least 44 points - [`space-gap-over-margins`](references/space-gap-over-margins.md) - Use gap over per-child margins - [`space-radius-tokens`](references/space-radius-tokens.md) - Tokenize corner radius by role ### 9. Native-Feel & Performance (HIGH) - [`perf-flashlist-for-lists`](references/perf-flashlist-for-lists.md) - FlashList over ScrollView lists - [`perf-reanimated-ui-thread`](references/perf-reanimated-ui-thread.md) - Animate on the UI thread - [`perf-gesture-handler`](references/perf-gesture-handler.md) - Gesture Handler over PanResponder - [`perf-expo-image`](references/perf-expo-image.md) - Load images with expo-image and caching - [`perf-memoize-list-items`](references/perf-memoize-list-items.md) - Memoize rows and callbacks - [`perf-haptics-key-actions`](references/perf-haptics-key-actions.md) - Add haptics on confirmations and toggles - [`perf-defer-offscreen-work`](references/perf-defer-offscreen-work.md) - Defer work past transitions ### 10. Complex Domain Components (MEDIUM-HIGH) - [`domain-calendar-virtualization`](references/domain-calendar-virtualization.md) - Virtualize the appointment calendar by day - [`domain-note-editor-autosave`](references/domain-note-editor-autosave.md) - Offline-first debounced note autosave - [`domain-bodychart-skia-canvas`](references/domain-bodychart-skia-canvas.md) - Draw body charts on a Skia canvas - [`domain-bodychart-gesture-paths`](references/domain-bodychart-gesture-paths.md) - Capture strokes via gestures and shared values - [`domain-compose-from-primitives`](references/domain-compose-from-primitives.md) - Build domain components from primitives - [`domain-optimistic-writes`](references/domain-optimistic-writes.md) - Render optimistic UI for writes ### 11. Governance & Consistency (MEDIUM) - [`govern-design-system-package`](references/govern-design-system-package.md) - Package the design system with one entry - [`govern-lint-no-raw-values`](references/govern-lint-no-raw-values.md) - Lint against raw colors and inline styles - [`govern-prevent-local-tokens`](references/govern-prevent-local-tokens.md) - Prevent feature-local tokens - [`govern-storybook-catalog`](references/govern-storybook-catalog.md) - Catalog component variants in Storybook - [`govern-naming-conventions`](references/govern-naming-conventions.md) - Enforce one naming convention - [`govern-incremental-migration`](references/govern-incremental-migration.md) - Migrate to tokens incrementally ## How to Use Read individual reference files for detailed explanations and code examples: - [Section definitions](references/_sections.md) - Category structure and impact levels - [Rule template](assets/templates/_template.md) - Template for adding new rules ## Reference Files | File | Description | |------|-------------| | [references/_sections.md](references/_sections.md) | Category definitions and ordering | | [assets/templates/_template.md](assets/templates/_template.md) | Template for new rules | | [metadata.json](metadata.json) | Version and reference information |
© pproenca · MIT · pproenca/dot-skills
Похожие скиллы
Все скиллы по теме «Фронтенд и UI» →Сначала — expo-design-system от других авторов.