/synclair. Every section is a
rendering of a file in your repo — browse the page, or read the source; they’re the
same facts. This is the map; each card links to that section’s full page.
Every section is one source, two renderings: a human page under
/synclair/* and a
machine-readable form for agents. Editing the underlying file updates both.Foundation
Foundations
The design tokens — color, type, spacing as one semantic vocabulary. What the lint
guardrails point back to.
Component library
The catalog: Components, Blocks, Templates — one gallery per tier, each with live
previews and a per-item doc page.
Library & surfaces
For multi-frontend products — a per-surface drill-in so web and native catalogs
coexist. Invisible for single-frontend projects.
Knowledge
Knowledge
Source-of-truth links, distilled digests, and generated summaries — so agents never
start blank.
References
The project’s findings — prior art and recommendations agents accumulate as they
research.
Visibility into the whole app
System map
What the codebase is made of beyond the UI — areas, API surface, data model, jobs,
integrations.
App sitemap
Every view the app serves, a live preview of each, and the components each one
composes.
Hygiene
Where host code steps outside its own foundation — inline styles, raw colors,
bypassed primitives. An advisory sweep.
Reports
A plain-English read of how the build is doing and a ranked, trackable list of what
to do next.
Operations
AI setup
Every skill and agent available, classified by category and origin.
Environment
The running stack, plus the opt-in “call home” freshness check against the upstream
foundation.
GitHub
Recent commits and diffs, read straight from git — the hub’s database.
Search (⌘K)
One command palette across everything — components, tokens, docs, pages.
In existing-app (watcher) mode
When Synclair runs beside a host app, a few sections take on a host flavor: the Component library shows host components tagged “Host” (documented from source, not imported), and Hygiene + the host catalog freshness are checked against the host repo so nothing quietly goes stale.Start with the capabilities
The skills and agents that power all the “regenerate” actions across these sections.