Skip to content

mzizi-dev/mzizi

v1.10.0Apache-2.0

Build with Mzizi: seven Mzizi agent skills (@nyuchi/mzizi-skills 0.20.0: mzizi-language, mzizi-roots, mzizi-design, mukoko-design, mzizi-backend, mzizi-architecture, discoverability), the /mzizi:component and /mzizi:scaffold commands, the fundi architecture agent, and the Mzizi MCP at mcp.mzizi.dev (free, no account; sign-in only for the Fundi tools). The 21-family palette, the shell first, Mzizi Roots components in Rust first, the Mzizi language, and the Ubuntu doctrine. Markdown and an MCP connection only: no scripts and no hooks. Owned and operated by Mzizi; live at mzizi.dev.

mzizi-architecture

Use this skill before you start a new Mzizi app, site, console or page, before you add a page to one, and whenever you decide where code, data or a component belongs. Design architecture is the DNA helix (8 nodes, 4 rungs, 6 strands), read live from api.mzizi.dev/v1/architecture or mzizi_get_architecture, with what each placement obliges. App architecture puts the shell first: every app or page mounts exactly one shell before anything else (AppShell for a signed-in app, the Dashboard Standard; DiscoverShell for a public browse site, the Discover Standard), then the page patterns, the five application layers, and the rule that a missing component goes upstream. System architecture covers Rust first, Astro as the default UI, Cloudflare Workers, the four API gateways, files as the registry's data layer at a pinned commit, one service per domain database, and what is decided versus built. Use it when an app lacks a shell, a page invents its own chrome, or someone asks how the pieces fit.

Read SKILL.md at the source

Pinned to revision 7c6449a1e5a1, so it is the text this page describes rather than whatever the author pushed since.

Files

Every link opens the file at its source, pinned to the revision this page describes.