Krusible
A full identity-and-build suite — tokens, components, an AI build harness, and automated QA — packaged as a product for teams who ship branded surfaces at portfolio scale.
- Stage
- In build
- Domain
- krusible.com
- Brand sites powered internally
- 14+
- Shipped sibling systems
- 3
Why We Built It
I run a portfolio of brands as a single operator. Every marginal cost of shipping a new brand — deciding tokens, assembling components, wiring the content pipeline, running accessibility and SEO audits — gets multiplied by every other brand in the portfolio. The friction is the business model blocker. A new brand that takes a week to scaffold is a brand that never gets launched.
The public tools in the design-system space solve parts of this. Token pipelines exist. Component libraries exist. AI coding assistants exist. But they do not compose into a coherent production stack. Each one leaves gaps, and the gaps are where consistency dies: a hardcoded color slips through, an accessibility check is skipped, a piece of content drifts off-brand.
Krusible is the consolidation. I built it for myself first, running 14+ brand sites on top of it. The product thesis is that other portfolio-scale operators — agencies running many clients, holding companies running many sub-brands, platform teams running many surfaces — have the same compounded friction, and the solution is the same full-suite answer.
How It's Being Built
The suite is deliberately full-stack, not a single library. Tokens, components, build harness, content pipeline, and deploy infrastructure are all first-class. Each piece is already running in production for the sites in my own portfolio; Krusible packages them together and exposes them to external teams.
The design-token layer defines identity as structured manifests — OKLCH color science, typography, spacing, motion — compiled to CSS custom properties with contrast validated at build time. A broken contrast pair fails the build before it can ship.
The AI build harness is the piece that separates Krusible from a conventional design system. Claude is wired into the pipeline with strict guardrails: the model builds inside the token system, selects from a curated component library, and every output passes an automated QA gate before it reaches production. The AI is a participant in the system, not a freestyle generator.
What It Does When Complete
Lets a team define a brand as a manifest — a structured JSON of colors, fonts, spacing, voice, content posture — and generate a production-ready branded surface against it. The token pipeline, component library, and content system all bind to that single source of truth.
Runs an AI-assisted build harness powered by Claude. The harness enforces the system rather than bypassing it: every generated component, every layout, every content block is gated by the token compliance and accessibility checks that the rest of the suite enforces. What AI ships is indistinguishable from what the team would have shipped by hand.
Ships with an automated QA gate covering contrast, accessibility, responsive breakpoints, dark mode, security headers, and SEO infrastructure. Each gate blocks deploys instead of filing warnings. The posture is: if the system cannot guarantee the quality, the site does not go live.
Integrates a content pipeline based on the Content Mint engine — research, drafting, quality scoring, and publish — so branded content is produced inside the same voice and compliance envelope as the UI it ships into.
Where It Is
The underlying systems are already operating the portfolio this site is part of. Krusible is the productization layer — the work of turning internal tooling into something external teams can consume — and it is in active development at krusible.com.
Shipped sibling systems power the suite: the token pipeline, the harness pattern (from Harness Lab), and the content engine (from Content Mint) are all running in production and feeding into Krusible as product primitives. The product is the integration, not a from-zero rebuild.
The stance is deliberate: this is a product, not a template marketplace and not a headless CMS. Krusible is opinionated about identity-first building, about AI-inside-the-system rather than AI-as-a-bolt-on, and about quality gates as the load-bearing primitive. Those opinions are the reason it exists.
Tech Stack
More work like this
The portfolio has more shipped products. About me covers the background and philosophy that connects them.