Skip to content

microsoft/power-platform-skills / plugins/mobile-apps/skills/design-system

design-system

Flagged

Creates the Tamagui brand system for an Expo/React Native Power Apps mobile app, including design-system.md, tokens.ts, and an HTML gallery.

references/vibe/design-bundle-schema.md

View on GitHub
# `## Design Direction` block schema

This file documents the exact shape of the `## Design Direction` markdown block that the internal `/design-system` style picker can write into `native-app-plan.md`. Downstream agents (`screen-planner`, `screen-builder`) read this block conditionally — if present, its values become defaults for per-screen design fields.

## Location in the plan

Inserted between `## Native Capabilities` (or `## Connectors`) and `## Design`. If `## Design` is absent, inserted before `## Screens`.

```
## Project
## Data Model
## Native Capabilities
## Connectors
## Design Direction       ← here
## Design                  ← (inherits/cascades from Direction)
## Screens
## Generated Services
```

## Block format

```markdown
## Design Direction

**Picked:** <Inspection | SaaS | Product | Hybrid (...)>
**Reference apps:** <comma-separated list>
**Picked at:** <ISO 8601 timestamp> (via /design-system style picker)

direction: <inspection | saas | product | hybrid>
surface: <strong-cards | subtle-depth | editorial>
background: <dark-slate | cool-gray-light | warm-cream | rich-dark>
palette: <named bundle, e.g. "slate + safety-orange">
typography: <"sans-only" | "display-headings + sans-body">
heading_font: <font name>
body_font: <font name>
body_size: <pt>
heading_letter_spacing: <em or 0>
list_style: <card-with-status-stripe | row-with-chevron | sentence>
density: <sparse | comfortable | comfortable-to-dense>
motion: <none | subtle | liberal-tasteful>
status_saturation: <full | desaturated | monochrome-plus-accent>
empty_state: <icon-sentence-bigbutton | icon-explanation-ghostbutton | type-led>
primary_action_shape: <rectangular | rectangular-bottom-pinned | pill>
primary_action_position: <bottom-pinned | top-right-or-in-flow | in-flow-or-bottom-center>
accent_color: <human-readable name (#hex)>
tone: <direct | professional | conversational>

> Downstream agents (`screen-planner`, `screen-builder`) MUST use these values
> as defaults for their own per-screen Surface / Density / List style / Motion
> fields unless a per-screen spec explicitly overrides.
```

## Hybrid bundles

Hybrids document their composition in the `Picked:` line and the bundle dimensions show the merged values:

```markdown
**Picked:** Hybrid (Product base + Inspection data density)
**Reference apps:** Linear (visual), ServiceTitan (density)

direction: hybrid
surface: editorial              # from Product
background: warm-cream          # from Product
palette: cream + sage           # from Product
typography: display-headings + sans-body  # from Product
list_style: card-with-status-stripe       # from Inspection (overrides Product's "sentence")
density: comfortable-to-dense   # from Inspection
motion: subtle                  # custom (between Product's "liberal" and Inspection's "none")
status_saturation: full         # from Inspection (data density needs status visibility)
... (rest from Product)
```

## How `screen-planner` uses this block

The planner's per-screen spec template (`agents/screen-planner.md` Step 4) includes these design fields:

- `Density mode` (sparse / comfortable / dense)
- `Surface style` (flat / subtle-depth / strong-cards / editorial)
- `Visual emphasis` (one phrase)
- `Restrained or expressive`
- `Animations` (per-event)

When `## Design Direction` is present, the planner pre-fills these fields from the bundle:
- `Density mode` ← `density`
- `Surface style` ← `surface`
- `Animations` ← derived from `motion`

A per-screen spec can still override (e.g., a celebration screen explicitly opts into `expressive` even in a `restrained` direction). Overrides are explicit annotations, not silent.

## How `screen-builder` uses this block

The builder reads the block once at Step 1 (after reading its assigned screen spec) and applies these defaults when choosing row/component patterns and writing components. Samples remain code/API references only:

- `list_style` → which list pattern family to adapt from the user/spec/design context; do not copy a `shared/samples/` layout with renamed fields
- `motion` → which entries from the animation vocabulary are allowed
- `tone` → button labels, error copy, empty-state copy
- `status_saturation` → which pill style to use
- `primary_action_shape` + `primary_action_position` → button placement and shape
- `empty_state` → which empty-state template to use
- `accent_color` → resolved into `$accentBase`

If `## Design Direction` is absent, the builder uses today's defaults from `mobile-design-philosophy.md` and `screen-templates.md`.

## Conditional reading (the play-out contract)

Both planner and builder use a single conditional check at the top of their workflow:

```text
Read native-app-plan.md
If "## Design Direction" section exists:
  Parse the bundle into a config object
  Use config values as defaults for design decisions
Else:
  Use existing industry-inferred defaults
```

This is the only integration point between the internal style picker and the rest of the system. If `## Design Direction` is absent, existing agents fall back to the `Else` branch automatically.

## Validation rules

- All bundle keys are required when the block exists (no partial bundles)
- `direction` value MUST be one of: `inspection`, `saas`, `product`, `hybrid`
- Color values MUST include a hex code in parentheses if a name is given
- `Picked at` MUST be a valid ISO 8601 timestamp
- `Reference apps` MUST be non-empty (at least 2 reference apps for clarity)

If the block is malformed, downstream agents should treat it as missing and fall back to the `Else` branch. They should NOT attempt to parse around errors.

## Re-running the style picker

Each `/design-system --reskin` run that uses the style picker REPLACES the existing `## Design Direction` block (does not append). The previous direction is logged in `memory-bank.md` under `## Design history` so the team has an audit trail.

If the user re-runs after screens have been built, `/edit-app` should be the next step to regenerate affected screens with the new direction's defaults.
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall