AI & LLM Support
Oxide UI is built with AI-assisted development in mind. This page explains how the docs are structured for LLM consumption and how to get the most out of AI coding tools when using Oxide UI.
Machine-readable files
| File | Purpose | URL |
|---|---|---|
llms.txt | Compact index of all pages and components | /llms.txt |
llms-full.txt | Full HTML source of every component variant | /llms-full.txt |
handoff.txt | Full project context for resuming AI sessions | /handoff.txt |
All files are plain text, served without authentication, and formatted for direct AI ingestion.
Resuming a project session
If you're using an AI coding assistant to build with Oxide UI and want to continue in a new chat, see the Resume / Handoff → page for a ready-to-use prompt and instructions.
Using with AI coding assistants
With Claude, Cursor, or Copilot Chat
Paste the relevant component source from llms-full.txt into your chat context:
Here is the Oxide UI Button component source:
[paste from /llms-full.txt]
Now create a "Save changes" button using the primary variant with a checkmark icon.System prompt for new projects
This project uses Oxide UI for its component library.
Oxide UI is a dark-mode-only Tailwind CSS component library for Nuxt.
Component reference: https://oxide-ui.dev/llms-full.txt
Design tokens: zinc-950 background, #D40C37 accent, zinc-100 text.
Interactive components use Headless UI v1 for Vue (@headlessui/vue).
Always use inline Tailwind classes — no custom CSS files.Structured metadata
Every page includes Schema.org SoftwareApplication JSON-LD, semantic HTML headings, and a sitemap at /sitemap.xml.
Color previews
Anywhere a color value appears in backtick code — like #D40C37 or rgba(212, 12, 55, 0.5) — a small swatch renders inline automatically.