open source · GPL-3.0

One view for
humans + agents building in harmony.

Synclair gives your product one browsable surface — design system, components, knowledge, codebase map, and AI setup, live from the repo. Humans get visibility. Agents get context. Both stay aligned because they're reading the same place.

View on GitHub
synclair.dev / overview
The Synclair hub overview — live counts of foundations, components, blocks, skills, agents and MCP servers, plus recent changes across code, docs and design, all read live from the repo
Live from the repo
The hub renders straight from git — always current, never a snapshot.
Two renderings
One fact, projected as a page for people and a payload for agents.
Pull / push sync
No server, no accounts. Sync is just git.
Stays aligned
Humans and agents read the same place, so nothing drifts.
— 01 · the problem

Humans and AI build in the same repo —
but no one can see the shape of it.

You can't see which skills and agents are in play, and AI-written code quietly drifts from your system's rules of composability. There's no shared picture of what humans or agents are actually doing — so the two fall out of alignment. Synclair draws that shape: one surface where the whole repo's structure, work, and rules are visible to both.

Product team PMs · design · eng curate Synclair one shared surface tokens · components knowledge · context build AI teammates any agent & its crew
— 02 · how it works

Four steps from repo
to a living project surface.

1embed

Add Synclair to your repo

One clone drops a synclair/ folder into your repository — versioned in git, right beside your code. Nothing about your app changes.

your-repo/app/src/package.jsonsynclair/foundations/library/knowledge/lives insideyour repo
2map

Diggers discover and map your view, backend, docs and AI setup

Intake agents read your code, tokens, PRDs, and Figma, then map it all — components cataloged, tokens traced, briefs distilled. It starts full, not blank.

your-repo/app/src/package.jsonsynclair/foundations/library/knowledge/mapped
3surface

Your repo gets its own dashboard and registry for humans + agents

The whole project becomes one browsable surface. People explore it, agents load it — the same place, always current.

your-repo/app/src/package.jsonsynclair/foundations/library/knowledge/synclair.dev
4sync

Stewards keep what you build in sync with Synclair’s view

As you build, steward agents keep the library, docs, and tokens healthy, and git keeps the surface aligned with your code — every commit, both ways.

your-repo/app/src/package.jsonsynclair/foundations/library/knowledge/synclair.devgit
— 03 · the crew

A team of nerds
that work for your repo.

Specialist agents seed the hub from what you already have, then keep it healthy as you build. Four crews, each with a job.

Diggers
Read your code, tokens, PRDs, and Figma — and fill the hub with what they find.
codebase-surveyor · token-archaeologist · knowledge-harvester
Mappers
Chart what the codebase is made of and keep the system map current.
system-mapper · component-cataloger
Builders
Design, document, and assemble components into the living library.
ui-designer · design-system-architect · ux-doc-writer
Stewards
Keep the library curated, docs reviewed, and tokens healthy as you build.
library-curator · tier-arbiter · render-auditor
— 04 · what's inside

One surface,
everything the project knows.

library48 comp · 120 tokButtonCardInputBadgeModalTabsAa

UX mapping

Design system and component library, collected into one place — every token, variant, and live preview, traced to where it’s used.

knowledge42 docsPRDSPECBRIEFFIGMAone place

Knowledge base

Every PRD, spec, brief, and Figma manifest, gathered in one place and stored as-is — each linked back to its source, never a lossy copy.

ai setup12 skills · 8 agentsskills12agents8mcp servers+3

AI setup

See every skill, agent, and MCP server the project fields — the whole AI toolkit, listed in one browsable place.

system map3 tiers · 7 svcappsvcdatawebadminapiauthjobsdbcache

System & environment map

Services, environments, and dependencies collected into one diagram — how the whole system fits together, at a glance.

routes: FoundationsLibraryKnowledgeSystem MapAI SetupReports
— 05 · the model

A cheerful freeloader
that mooches off tools you already have.

No platform to log into, no servers to babysit. Synclair lives in your repo, piggybacks on git and GitHub to stay in sync, and lets your AI agent do the heavy lifting. It brings the context; everything else, it borrows. Engineless, on purpose.

It's a repo app

Plain files committed inside your project. Nothing to deploy, no database to run — the repo is the app.

Git & GitHub keep it in sync

No server, no accounts. Every change is a commit; sync is just pull and push. GitHub is the backbone the whole hub rides on.

Your agent is the engine

Synclair brings the context, not the compute. Bring your own AI agent — it reads the hub and does the work. Engineless, in the best way.

git HTML agent
One source, two renderings. Git is the database.

Every fact lives once in git and projects two ways — a page a person browses and a machine-readable form an agent loads. No server, no accounts; sync is pull/push.

Yours to take anywhere.

It's plain files in your repo. No lock-in, no platform to log into — fork it, host it, or read it straight from the folder.

Plain files in git
No accounts
Fork & host anywhere
GPL-3.0
— 06 · get started

Two paths in.

new project

Start from Synclair

Clone it as the foundation for something new. The hub is your project's front door from commit one.

existing app

Drop it beside your code

Add it next to an existing repo. Intake agents dig through what you have and fill the hub — it starts full, not blank.

bash
$ git clone github.com/joshuaiwata/synclair
$ cd synclair && npm install
$ npm run dev -- -p 4100
→ hub live at localhost:4100
Built on Hatchable