nyuchimzizi
Mzizi — an open-architecture project of the Bundu Foundation, operated and developed by Nyuchi. Built on the Five African Minerals palette.
Built by Nyuchi Africav4.0.39
561 components, blocks, and charts rooted in the Five 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.
How it works
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.tsxFive African Minerals built in. Swap tokens to match your product, or ship as-is.
<Button variant="outline">Ship it</Button>BUILD WITH THE PORTAL
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 — Five 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 Claude Code skills ship in this repo: nyuchi-design-system, scaffold-component, ecosystem-app-setup. Symlink or copy into your project's .claude/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.
AI-Native
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
The nyuchi-design-system skill teaches Claude Code the Five African Minerals palette, component patterns, Ubuntu design principles, and APCA accessibility standards.
Usage
# In any Claude Code session:
/nyuchi-design-system
# Or ask Claude directly:
@design-portal get_component button
@design-portal 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.
RESILIENT BY DESIGN
The 3D frontend architecture is ten layers across five axes. Eight of those layers build the product. Two sit outside the build path on purpose — they exist so the system never goes stale or insecure.
architecture_frontend_axes and architecture_frontend_layers to be populated. See issue #46.Fundi (Shona for "artisan") is the architecture node that lives outside the build path. It defines where self-healing belongs in the 3D model: actors outside the build consume the L8 assurance layer's runtime signals and remediate 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 ten-layer model and SECURITY.md for the disclosure process.
Explore
Design system, component library, architecture reference, and developer docs — all in one place.
410 production-ready UI components. Browse, preview, and install.
The open ten-node frontend architecture across five axes.
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.