# UDS Usage Best Practices — Compiled Reference
> **Note:** This document is a compiled reference for AI agents and LLMs. It
> contains all quick-reference tables and critical rules expanded inline. For
> individual component or token details, read the corresponding
> `rules/react-{name}.md` or `rules/core-{name}.md` file.
---
## Table of Contents
1. [Critical Rules](#1-critical-rules)
2. [MCP Tools](#2-mcp-tools)
3. [Component & Hook Quick Reference](#3-component--hook-quick-reference)
4. [Token Quick Reference](#4-token-quick-reference)
5. [Typography](#5-typography)
6. [Icons](#6-icons)
7. [Theme Variants](#7-theme-variants)
8. [Common Mistakes](#8-common-mistakes)
9. [Figma-to-Code Workflow](#9-figma-to-code-workflow)
10. [Post-Build Verification](#10-post-build-verification)
---
## 1. Critical Rules
### ALWAYS
- Use UDS React components — never rebuild from raw HTML/CSS.
- Map every design element to a UDS React component whenever possible. If no
matching UDS component exists, implement a custom component using UDS design
tokens primarily.
- Read the component's rule file before using it in code.
- For bullet lists and rich text content, primarily use the `Text` component
with markdown string syntax — it automatically renders ordered lists
(`1. ...`) as `BulletIndex`, unordered lists with `[c]` marker (`- [c] ...`)
as `BrandCheckmark`, and plain unordered lists (`- ...`) as styled bullets.
- For brand logo assets, do NOT use the `Icon` component — brand logos need
exact Figma dimensions, not icon sizing. Instead, wrap a native `` tag
inside a `