nyuchimziziMzizi — an open-architecture project of the Bundu Foundation, operated and developed by Nyuchi. Built on the Seven African Minerals palette.
Playground
Doctrine
Releases
Documentation
v1.0.0
nyuchimzizinyuchimziziMzizi — an open-architecture project of the Bundu Foundation, operated and developed by Nyuchi. Built on the Seven African Minerals palette.
323 components, blocks, and charts rooted in the Seven African Minerals palette. One design system powering mukoko, nyuchi, and every app in the bundu family. Install with the shadcn CLI — no packages, no lock-in.
Real components, rendered live — theme-adaptive, accessible, and installed straight into your repo with the shadcn CLI. This is the same registry your AI assistant reads.
Make changes to your account here.
4.0 / 5.0
Total Revenue
$45,231
↑ +20.1% from last month
Active Users
2,350
↑ +12.5% from last month
Use the shadcn CLI to add any component. Dependencies and tokens resolve automatically.
npx shadcn@latest add https://mzizi.dev/api/v1/ui/buttonComponents land in your project as source files. Full ownership, zero hidden dependencies.
components/ui/button.tsxSeven African Minerals built in. Swap tokens to match your product, or ship as-is.
<Button variant="outline">Ship it</Button>The portal is a registry, a token system, an MCP server, and a set of installable Claude Code skills. You don't pull a package — you pull exactly the pieces you need and own the source. Here's the full authoring loop.
Every registry item is installable through the shadcn CLI. The CLI copies the source into your repo — you own and modify it freely.
Browse the live registryCopy the :root and .dark blocks from app/globals.css — Seven African Minerals, semantic colors, typography, radius scale. Every component reads from these CSS variables.
Add https://mzizi.dev/mcp to your Claude Code settings. tools and resources let your AI assistant install components, scaffold new ones, look up tokens, and read live docs without round-tripping to the browser.
Three design skills ship in the @nyuchi/mzizi-skills bundle: nyuchi-design, bundu-design, mukoko-design. Run npx skills add @nyuchi/mzizi-skills and the router activates them automatically.
The L8 assurance layer surfaces runtime failures across the ecosystem. Run pnpm check before every push to mirror the full CI gate locally.
Going from create-next-app to a portal-consuming production build? The ecosystem-app-setup skill walks Claude Code through the eight setup steps end-to-end.
Mzizi ships with a Model Context Protocol server and a Claude Code skill. Your AI assistant can browse components, generate scaffolds, and fetch source code — without leaving the conversation.
Streamable HTTP · tools and resources
Connect Claude Code, Cursor, or any MCP-compatible assistant to the full component registry. Browse, search, scaffold, and fetch source — live from the database.
.claude/settings.json
{
"mcpServers": {
"mzizi": {
"type": "url",
"url": "https://mzizi.dev/mcp"
}
}
}Slash command · Design system aware
Three design skills — nyuchi-design, bundu-design, mukoko-design — teach Claude Code the Seven African Minerals palette, component patterns, Ubuntu design principles, and APCA accessibility standards.
Usage
# In any Claude Code session:
/nyuchi-design
/bundu-design
/mukoko-design
# Or ask Claude directly:
@mzizi get_component button
@mzizi scaffold_component data-tablePublic metrics · CC BY 4.0
Usage metrics are public — aligned with the bundu open data philosophy. See which components are most installed, API latency, error rates, and MCP tool usage in real time.
Other libraries hand you components. Mzizi ships the spine that connects them to infrastructure — observability, accessibility, motion, resilience and health — with zero config. Wrap a section or call the hook; everything else is wired.
// Declarative — wrap any section
<NyuchiHarness name="events-feed" skeleton={<FeedSkeleton />}>
<EventsFeed />
</NyuchiHarness>
// Imperative — inside a component
const { log, motion, announce } = useNyuchiHarness("listing-card")Tokens (L1) and primitives (L2) stay pure. Brand (L3), safety (L4) and resilience (L5) components plug into the same harness — so behaviour is consistent across the whole system, not re-implemented per component.
A scoped logger per component and render timing, reported to the health monitor.
Auto-mounted aria-live region, announce(), and focus-ring tokens — for free.
Entry animation from the motion tokens, automatically honouring reduced-motion.
A branded fallback with retry and structured error tracking around every section.
Reports healthy / degraded / error / loading to the global health monitor.
Text direction (RTL/LTR) and a string-token accessor via useLocale.
The Mzizi DNA helix has two backbones that build the product; two cross-cutting rungs — fundi and documentation — exist so the system never goes stale or insecure.
Fundi (Shona for "artisan") is a rung— a cross-cutting base pair that bridges both backbones of the helix rather than sitting on a single strand. It consumes the N8 assurance node's runtime signals and remediates the root cause, so a failure becomes a learning event rather than a user-facing incident.
Every component, brand spec, and changelog entry lives in Supabase; long-form guides live in standalone Mintlify docs sites. The Next.js app and the MCP server read live; nothing is copy-pasted between them. When a component changes in the database, the portal, the API, and the AI tools all pick it up on the next request. Drift becomes structurally impossible.
/api/v1/* endpoints serve component + brand + changelog data live from the databaseregistry.json is a CI-verified snapshot, never hand-editedNet effect. Five CVEs cleared in this PR alone — caught by pnpm audit, fixed inside the same PR per the no-deferral rule. CodeQL workflow-permissions findings, Dependabot advisories, and security-review notes never wait for a follow-up PR. See the architecture page for the full helix model and SECURITY.md for the disclosure process.
Design system, component library, architecture reference, and developer docs — all in one place.
203 production-ready UI components. Browse, preview, and install.
The open Mzizi DNA double helix — nodes on strands, plus cross-cutting rungs.
Live usage metrics for the registry, the API, and the MCP server.
Installation, theming, CLI, and contributing guides.
REST API, MCP server, and the OpenAPI contract.