> ## Documentation Index
> Fetch the complete documentation index at: https://design.slingshotai.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> This site documents Sundial 2.0, the design system of the Ash mobile app (Flutter). For implementing UI: use the Design System pages — color/typography tokens (foundations/*), Flutter theming (theming/*), and component APIs (components/*) — as your reference; every value there mirrors the Dart source in lib/design_system/. The Philosophy pages (philosophy/*) are design rationale written for humans: consult them when making design decisions, not for API lookups. Golden rules: never hardcode colors or text styles — read tokens via context.colorTheme and context.textTheme; prefer the 2.0 semantic names (contentPrimary, surfaceComponent, accentSolid…) over legacy contrast*/surface* getters and over SundialRef primitives; the accent is a single pale lavender solid that takes dark content — never use accent fills as text, icons, or borders (use contentAccent / borderSelected); brand surfaces are mode-invariant and pair with the contentOnBrand* inks; check lib/design_system/components/ before building custom widgets.

# For Agents

> Machine-readable resources and usage guidance for AI agents working with Sundial

This section gathers everything an AI agent needs to get up to speed on Sundial quickly and use it correctly.

> [!NOTE]
>
> **One-line orientation.** Implementing UI → use the **Design System** section (tokens, theming, components); every value mirrors `lib/design_system/` in the Ash app. Making design *decisions* → consult **Craft & Foundations** (rationale, not API). Never hardcode colors or text styles.

## Which section to use

| Task | Section |
| - | - |
| Implement a screen or component | Design System |
| Look up a color / type / spacing value | Design System → Foundations |
| Understand persona or brightness theming | Design System → Theming in Flutter |
| Choose a layout, or judge whether an element belongs | Craft & Foundations |
| Understand *why* a rule exists | Craft & Foundations |

## Golden rules

* Read tokens from context: `context.colorTheme` and `context.textTheme`. Never hardcode `Color(0xFF…)` or a `TextStyle(fontSize: …)`.
* Prefer **semantic** tokens ([Semantic Colors](https://design.slingshotai.com/foundations/colors/semantic.md)) over `ReferenceColors` primitives.
* Use `accent.*` tokens for persona-branded UI ([Accent Colors](https://design.slingshotai.com/foundations/colors/accent.md)).
* Check the [Components](https://design.slingshotai.com/components/styled-card.md) section (and `lib/design_system/components/`) before building a custom widget.

## Machine-readable formats

Every page on this site is available as clean Markdown for ingestion:

* [**/llms.txt**](https://design.slingshotai.com/llms.txt) — a compact, priority-ordered index of every page with descriptions (implementation pages first, design rationale last)
* [**/llms-full.txt**](https://design.slingshotai.com/llms-full.txt) — the entire documentation concatenated into a single file
* **Any page as Markdown** — append `.md` to its URL (e.g. `/foundations/colors/semantic.md`), or use the **Copy page** button at the top-right of any page to copy or view the Markdown source
* **Hosted MCP server** — this site exposes an MCP endpoint at `https://slingshot-ai.mintlify.io/mcp`, so agents can search and fetch pages as tools
* **Open in an assistant** — the Copy page dropdown can open the current page directly in ChatGPT, Claude, and other assistants

## Standing agent instructions

The site ships an instruction block (`docs.json` → `markdown.instructions`) that Mintlify injects into agent context automatically — it restates the section-routing and golden rules above, so a well-integrated agent receives them without reading this page.

> [!NOTE]
>
> The design [Philosophy](https://design.slingshotai.com/philosophy/overview.md) is deliberately kept in its own **Craft & Foundations** section, not mixed into the implementation reference — so agents pulling the Design System pages for an implementation task aren't distracted by design-rationale prose. Pull it in intentionally when you're making a design judgment.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.