Domino UI Design System Skill
Architecture
Domino apps use FastAPI (Python backend) + Ant Design 5.x (frontend via CDN, no build step). Avoid inline styles and JS — use statically referenced CSS/JS files. Output errors to stdout.
CDN Setup
Include in HTML <head>:
Use React.createElement() (aliased as h) — no JSX, no build step:
Domino Theme
Wrap the app in ConfigProvider with this theme:
Top Navigation Bar
Height: 44px, Background: #2E2E38, Text: #FFFFFF. Use the Domino logo (height 32px). Primary actions on right. Only add nav items with real destinations.
Domino Logo: Reference assets/domino-logo.svg from this skill's directory (e.g. .claude/skills/domino-ui-design/assets/domino-logo.svg). The SVG is white text on transparent background, designed for the dark nav bar.
Charts (Highcharts)
Domino API Integration
Authentication
Re-acquire the access token on every API call (it expires quickly):
API Base Paths
Two separate APIs with different base paths:
Do NOT add /api/ prefix to v4 platform endpoints.
Environment Variables (available in Domino)
DOMINO_API_HOST, DOMINO_PROJECT_ID, DOMINO_PROJECT_NAME, DOMINO_PROJECT_OWNER
Do not add mock/fake data if the API isn't working. Prompt user to set env vars.
Running the App
Use relative URLs (not absolute) — Domino's nginx proxy modifies the root URL.
UX Design Rules
For detailed UX principles, writing guidelines, component patterns, and review checklists, read references/ux-design-rules.md [blocked].
Key rules to always follow:
- Empty states must be actionable — answer: What is this? Why is it empty? What can I do?
- Error messages must be human-readable with guidance on what to do next
- Disabled elements must explain why they're disabled (tooltip)
- Truncated table text must have tooltips
- Icon-only buttons must have tooltips
- Use sentence case for UI text (not Title Case)
- No exclamation points in UI copy
- Side panels should overlay, not push/crush main content
- Checkboxes should use positive framing — checked = ON/enabled, never checked = OFF/disabled
UX Review
When reviewing a Domino app UI, read references/ux-design-rules.md [blocked] and check against the review checklists. Classify issues as High/Medium/Low severity.
Documentation Reference
Before writing or verifying any API call, use the cluster swagger to confirm current endpoint paths and field names. Use public docs for workflow context and field explanations.
Get the cluster base URL: $DOMINO_API_HOST (injected by Domino into every workspace, job, and app).
This skill uses two swagger docs:
Public API (covers /api/ endpoints — v1, v2, beta — no auth required):
Governance API (covers /api/governance/v1/ endpoints, requires bearer token):
Public docs (workflow context and field explanations):

