mzizi-dev/mzizi
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.
Use this skill whenever a Mzizi-ecosystem site or app needs to be found and correctly rendered by machines — social/messaging link previews (OpenGraph), search engines, and AI agents. Covers the doctrine ("if the machine can't see it, it doesn't exist"), the brand-agnostic Mzizi "hive" OG-image template (dynamic per page, carrying each page's title + description + site icon), the static-Astro implementation (the standard), the rules for a surface already on Next.js (next 16.3.6 or later, no request input in an ImageResponse), APCA-checked text colours, and a pre-ship checklist. Reach for it when a shared link renders no preview, when adding a new route/site, or when wiring SEO/AIO (llms.txt, structured data, agent-readiness). For tokens and brand use mzizi-design; for components use mzizi-roots.
Use this skill whenever you create, apply or export Mukoko's brand identity, or anything that must carry it. That covers the Seed of Life mark (the Swarm), the app icon, favicons, the lockup, the splash screen, social and launch assets, and honeycomb backgrounds. It ships the canonical files byte for byte as mukoko-dev/mukoko-news serves them: the full-palette mark (light and dark), the app icon on deep tanzanite, the paper icon, the favicon set and the lowercase serif lockup. It also carries the honeycomb backgrounds and the 1080×1920 splash, the seven minerals of the mark with their meanings, and the rules. The full-palette mark is the only icon at every size, with no mono or single-colour reduction. Never recolour, reorder, add a gradient or shadow, or redraw it. The wordmark is always lowercase "mukoko". For the wider palette, tokens and UI use mzizi-design, and for app structure use 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.
Use this skill when building or changing a Mzizi backend service — on Cloudflare Workers today (a Rust Worker with workers-rs, or an MCP server in TypeScript), with containers and bare metal as decided direction, not built. Covers where the backend stands today (every live Mzizi Worker is TypeScript; the Mzizi language has a backend service slice, RFC-0011, that mz contract runs in process and mz build lowers to a local Rust + axum package, with no Workers target and nothing deployed), the live endpoint map (api.mzizi.dev, mcp.mzizi.dev, docs.mzizi.dev/mcp), the sans-IO core plus thin host that Mzizi Roots server components use, wrangler config, cron and queues, storage through Workers bindings (no database client), MCP transport, one-factory/many-entrypoints, a code-defined tool catalogue over data bundled at a pinned commit, federation, tool naming and annotations, the free-except-Fundi access rule, logging, publishing to npm and the MCP Registry, and deploy.
Use this skill for the Mzizi design system and brand: generating well-branded interfaces (production or prototype), design tokens, and ecosystem-level work. Contains the canonical 21-family palette (seven African Minerals, seven Heritage tones, the Experimental Seven) with generated stylesheets (tokens/palette.css, tokens-update.css), the radius scale, Noto Sans/Serif and JetBrains Mono type, pill buttons, the Bundu floor (17px body, 14px captions, 49px hit region, 14px inset, 7px gaps, 1.5 leading) and the density layer, 7:1/4.5:1/3:1 contrast, status and surface tokens, the Dashboard and Discover Standards' brand overlays (colour and mark only), the verified brand constellation (each brand's mineral, voice, meaning, URL), the five Ubuntu pillars and principles, what is and isn't an ecosystem app, and the wordmarks. Also covers Apple's Human Interface Guidelines as the baseline and where Mzizi is the authority: touch targets, spacing, type scale, colour, pill geometry, materials, density and the shell.
Use this skill when writing, checking or fixing Mzizi language source (.mz files): LANGUAGE-TRACKER.md as the one list of what Mzizi can and cannot do, the component syntax (enum tables, props, the view tree, when / for each, records, use motion), the backend service (routes, handlers with when / header / respond, example and ensure contracts; RFC-0011), the mz check --agent loop and its NDJSON diagnostics, mz fix for every exact fix, mz contract, mz build (a service to a local Rust + axum package), the diagnostic codes you will meet (MZ0101, MZ0106, MZ0312, MZ0313, MZ0406-MZ0409, MZ0602-MZ0613, MZ07xx, MZ08xx), programs (RFC-0013: fn main, let / var, functions, when / match, loops, int / float, text, list / map / set, records, enums, result with try) checked by mz check and run by mz run, the language harness, and exactly what is not built yet (modules, a standard library, component lowering, Rust interop, I/O, concurrency, generics, mz test, a release).
Use this skill for anything involving Mzizi's components: using them, starting an app on them, or contributing one. Mzizi Roots is Mzizi's own components in Rust (UI and server components) from mzizi-dev/mzizi-registry. Covers cargo add mzizi-roots / mzizi-roots-server, what mzizi_get_component returns (Rust first), the node-to-crate map, pub const CONTRACT, the contracts in the registry's contracts/ for the Dashboard Standard (app/, 35 components) and the Discover Standard (discover/, 16 components; no script, server-filled shells): read one before building or changing a @bundu/ui component. Also no-JS fallback, density and floors (49px hit region, 17px body, 14px inset, 7px gaps) and brand-overlay rules, the frontend paths (pure .astro via mzizi add --type astro, Astro with Roots, pure Rust; Next.js adopts the .tsx), reuse before build, and adding a component (node, .rs, .tsx, registry.json, the gates). Files are the data layer: no database.