> ## 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.

# Process

> Design rationale: reference-first design, building from parts, and iterating to a testable skeleton

## Start with reference, not from scratch

When approaching a new feature, the first step is always to look at successful solutions from respected companies and designers on **Mobbin** and **Are.na**. Good design stands on the shoulders of people who came before. Don't reinvent the wheel — study what works, understand *why* it works, then adapt it.

## Build from parts

Take specific patterns — a nav system from one app, a card layout from another — deconstruct why they work, then rebuild them for our context. This is not copying; it's informed composition.

## Dedicate your deepest thinking to unknown unknowns

Templates, macros, and proven patterns handle the known. The real design work is revealing what you haven't considered yet. When new knowledge surfaces during the design process, don't be afraid to abandon existing work and rebuild on a fresh foundation.

## Iterate quickly

Move fast through the structural decisions. Get to something testable. The goal is not a perfect first draft — it's a sound skeleton that can be validated and refined.

> [!NOTE]
>
> This maps directly onto the V0 principle from the [overview](https://design.slingshotai.com/philosophy/overview.md): structural soundness first, expressive investment second — and only where it's earned.


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