Design System
Creates the Tamagui brand system for an Expo/React Native Power Apps mobile app...
Install
npx skills add microsoft/power-platform-skills --skill design-system -g -a claude-code -y- Repository
- microsoft/power-platform-skills1.1k
- Category
- Design
- Updated
- 4d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Creates the Tamagui brand system for an Expo/React Native Power Apps mobile app, including design-system.md, tokens.ts, and an HTML gallery.
Plugin check: Run
node "${PLUGIN_ROOT}/scripts/check-version.js"- if it outputs a message, show it to the user before proceeding.
Shared instructions: shared-instructions.md, read first.
Design System
Entry routing: use the shared App feature entry points preflight before the workflow below.
Before reading brand state, bind working_dir through
app-working-directory.md.
Use that root for every shell call and absolute file-tool path, including
history, rollback, previews, and runtime wiring in the referenced workflows.
Read-only --history / --diff and standalone brand generation without an app
remain here.
Source of truth for every screen built in a Power Apps mobile app. Produces three artifacts:
brand/design-system.md, full spec (palette, typography, spacing, components, negatives)brand/tokens.ts, importable Tamagui token exportbrand/design-system.html, deterministic visual gallery (zero LLM cost)
Design-system and Tamagui integration are complementary, not alternatives. /design-system owns user-facing brand/design decisions and preview artifacts; /create-mobile-app Step 9b applies references/tamagui-integration.md as internal implementation plumbing so those decisions become Tamagui tokens, aliases, and provider props. The old separate tamagui-design-system skill existed before this split was clear; keeping it separate made users choose implementation details and added prompt surface. Do not reintroduce it as a user-invocable skill.
