LLMs.txt Documentation
How to get tools like Cursor, Windsurf, GitHub Copilot, ChatGPT, and Claude to understand @nofinite/nuicss.
Tip
Looking for unified ecosystem presets or multi-package rules? Visit our central AI Agents Hub.
We support LLMs.txt files for making @nofinite/nuicss design tokens and superclasses directly available to large language models.
Directory Overview
The following machine-readable context files are available:
/nuicss/llms.txt: The main LLMs index for@nofinite/nuicss./nuicss/llms-full.txt: Complete context bundle containing all 120+ superclasses, OKLCH token variables, and utility classes./llms.txt: Ecosystem index covering all 8@nofinitelibraries./llms-full.txt: The unified ecosystem bundle.
Usage with Cursor & Windsurf
Add @nofinite/nuicss context directly to your AI editor:
1. Cursor Docs Link
In Cursor Settings > Features > Docs, add:
plaintext
https://opensource.nofinite.com/nuicss/llms-full.txt2. Project Rule (.cursorrules or .windsurfrules)
markdown
# NUICSS Rules for AI Assistants
1. Superclasses: Always prefer semantic superclasses (`btn`, `card`, `badge`, `input`, `table-container`, `kanban-board`, `markon-editor`, `chart-container`) over verbose Tailwind utility clusters.
2. OKLCH Design Tokens: Use OKLCH variables (`bg-surface`, `text-default`, `border-default`, `color-primary`). Never hardcode hex color literals (#...).
3. ARIA States: Use native ARIA attributes (`aria-selected="true"`, `aria-invalid="true"`, `aria-expanded="true"`) which NUICSS styles automatically.
4. Zero Downstream CSS Invariant: NUICSS is the sole styling engine. Downstream packages must never author, compile, or bundle independent CSS files.