NV NVIDIA Elements Catalog Starters Repo System Themes Getting Started Getting Started Installation CLI MCP Skills Lint Integrations Getting Started Angular Bundles CDN Custom Elements Eleventy Golang HTMX + Go Hugo Import Maps Lit Lit Library MCP Apps NextJS Nuxt Preact React SolidJS Svelte TypeScript Vue About What’s New Changelog Metrics Support Accessibility Contributions Requests Migration Foundations Overview Typography Iconography Themes Design Tokens Size & Space Objects Interactions Support Status Color Animation Fonts Layers Custom Layout Horizontal Vertical Grid Popovers i18n Visualization View Transitions DESIGN.md Elements Accordion Alert Avatar Badge Breadcrumb Button Button Group Card Chat Message Checkbox Color Combobox Copy Button Datagrid Integrations Column Action Column Alignment Column Fixed Column width Container Card Display Settings Footer Heatmap Keynav Multi Select Pagination Panel Detail Panel Grid Performance Placeholder Row Action Row Groups Row Sort Scroll Height Single Select Stripe Date Datetime Dialog Divider Dot Drawer Dropdown Dropdown Group Dropzone File Format Datetime Format Number Format Relative Time Forms Validation Actions Control Gauge Icon Icon Button Input Input Group Logo Menu Month Notification Page Page Header Page Loader Pagination Progressive Filter Chip Progress Bar Progress Ring Password Preferences Input Pulse Radio Range Resize Handle Search Select Skeleton Sort Button Sparkline Star Rating Steps Switch Tabs Tag Textarea Time Toast Toggletip Toolbar Tooltip Tree Week Patterns Authentication Browse Chat Dashboard Editor Empty States Heatmap Keyboard Shortcut Logging Media Navigation Onboarding Panel Responsive Search Subheader Trend Code Codeblock Monaco Input Diff Input Editor Diff Editor Problems Markdown Markdown CSS Utility Labs Responsive Layout Viewport Container Patterns Forms API Design Properties & Attributes Slots Registration CustomEvents Stateless Composition Styles Packaging Glossary Logs Internal Guidelines Agent Harness Agent Tooling Agent Ownership Documentation Examples TypeScript Testing Unit Testing Accessibility Testing Lighthouse Testing SSR Testing Visual Testing Troubleshooting Component Creation Internal Examples All Examples

NVIDIA Elements DESIGN.md

The official design system file for AI coding agents building NVIDIA Elements interfaces. It combines exact, machine-readable design tokens with human-readable guidance for typography, layout, component selection, accessibility, and operational UI patterns.

This file describes the NVIDIA Elements UI Design System. It does not represent a specification of NVIDIA marketing sites or NVIDIA corporate brand.
Download View on GitHub

What is DESIGN.md?

DESIGN.md is a portable format for describing a visual identity to coding agents. The file does not depend on a specific framework or agent. The open DESIGN.md specification combines YAML front matter for exact design tokens with Markdown prose explaining how and why to apply them.

The NVIDIA Elements file gives agents a compact contract for:

  • Semantic colors for canvas, surfaces, text, links, interaction, and status
  • Interface typography using Inter and Roboto Mono
  • Spacing and border-radius scales
  • Representative visual contracts for buttons, fields, cards, popovers, and status UI
  • Layout, elevation, component composition, accessibility, and do-and-don't guidance
  • Canonical links to maintained Elements components, tokens, CLI, and MCP tools

Download and use

Place the file at the root of a project where an AI coding agent can read it:

Then give the agent a direct instruction:

The file works as portable context on its own. For exact component APIs, examples, icon names, and project validation, combine it with the Elements MCP server, CLI, and agent skills.

Why use the official file?

Public DESIGN.md catalogs often infer a company's visual style from a marketing website. That can be useful for inspiration, but it does not represent the maintained component contracts, theme semantics, accessibility behavior, framework integrations, or operational UI patterns.

The official file stays connected to the implementation. When an Elements source token changes, the generated values change with it; when component guidance changes, the Elements team reviews this page and the repository artifact together.