Skip to main content
This section gathers everything an AI agent needs to get up to speed on Sundial quickly and use it correctly.
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

Golden rules

  • Read tokens from context: context.colorTheme and context.textTheme. Never hardcode Color(0xFF…) or a TextStyle(fontSize: …).
  • Prefer semantic tokens (Semantic Colors) over ReferenceColors primitives.
  • Use accent.* tokens for persona-branded UI (Accent Colors).
  • Check the Components 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 — a compact, priority-ordered index of every page with descriptions (implementation pages first, design rationale last)
  • /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.
The design Philosophy 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.