AI Founders Design System
AI Founders agentic design system demo
by Rostislav Peška · github.com/rostislavpeska/aifounders-designsystem · website
Install
No release zip yet. The repository archive installs, but the folder name will carry the branch suffix and updates will not flow:
wp plugin install https://github.com/rostislavpeska/aifounders-designsystem/archive/refs/heads/main.zipA WordPress-plugin design system where code is the source of truth — design tokens compile to CSS, components ship with real-markup specimens, and a Playwright contract gate keeps every promise honest. Figma is a projection of the system, never its canon.
Built for the AI Founders platform (aifounders.cz)
and consumed by projects built on it — including
AI Guild — as two brand themes of one system:
aifounders (blue) and aiguild (yellow), mirror-law twins that share
every mechanism and differ only in palette values.
Status: release candidate (
2.0.0-rc.1). The full component inventory is distilled and gated. AIF theme adoption (Stage 2) is underway — the theme retired its 3752-linecomponents.csswholesale for the DS plugin in an additive rebuild (2026-07-08) and its hand-rolled forms now render on DS markup (2026-07-09); the theme enqueuesaifds-componentswith a graceful fallback when the plugin is absent. AIG adoption (Stage 3) follows. Method + lessons: ADOPTION-PLAYBOOK. See docs/IMPLEMENTATION_STATUS.md for the live ledger and roadmap.
What's inside
- Design tokens (
tokens/, DTCG JSON) — a 3-layer color architecture: per-brand palette (64 names, perfect cross-brand parity) → shared semantic roles (51) → surface scopes (7). Components consume roles, never raw values; surfaces re-skin components with zero variant classes ("surfaces replace variants"). Typography, spacing, strokes, shadows, breakpoints (a closed set), and the icon system live here too. - Components (
assets/css/components.css+inc/styleguide.php) — the full inventory from text styles and forms through cards, modal, accordion, comments, engagement, and the site chrome (header, footer, sticky bar). One row per decision, not per CSS class — see the component ledger and the per-component reference docs in docs/components/. - The styleguide — activate the plugin and open
/?aifds_styleguide=1(admin/WP_DEBUG-gated). Every specimen renders the real markup on both brands and both color surfaces. A sandbox (/?aigds_sandbox=1) hosts full-page experiments without touching canon. - The gate (
tests/tokens.spec.js+build/lint-css.mjs) — 80+ Playwright contract tests per brand (token values × surfaces × scales × behaviors) plus lint-enforced CSS laws. CI runs the headless layer; the WordPress-bound layer runs against a local stack. - Provenance — every divergence, unification, and veto is a dated ruling in docs/DECISIONS.md. Values were harvested from rendered production reality, never invented.
- Figma projection (
assets/figma-map.json) — the token layers are imported into Figma as variable collections (Palette · Semantic · Base · Type Primitives) with the CSS surface scopes as modes; components are built with Auto Layout. The map is the committed import ledger (itsfigma_node_ids backfill into the vector rows). Manual component refinement is in progress. Code stays canon; Figma is the projection — see FIGMA-IMPORT.md.
Install
Standard WordPress plugin: drop this repo into wp-content/plugins/ (or
upload a ZIP of it) and activate. Stage 1 is inert by design — styles
are registered but never enqueued on theme pages, so activation changes
nothing user-visible; the plugin only renders its own styleguide routes.
Theme adoption is the explicit, separate step.
Develop
node build/build.mjs # tokens JSON → assets/css/tokens.css (+ manifest)
node build/lint-css.mjs # the CSS laws (3-layer, breakpoints)
npx playwright test tests/tokens.spec.js # the contract gate (needs the local WP stack)
The ritual for every change: build → lint → gate → conventional commit. Never weaken a gate assertion to make it pass.
The agentic layer
This system is built to be operated and consumed by agents:
- The per-component docs in
docs/components/are written at decision-space granularity — "when do I reach for this, what's the contract, what breaks" — and double as retrieval rows for the vector index described in docs/proposals/VECTOR-DS.md (GitHub canonical → Supabase pgvector as a rebuildable router; the vector finds the component, the repo remains the truth). - Architecture research and the target end-state live in docs/proposals/AGENTIC-DS-RESEARCH.md.
License
MIT.