Kumiko Framework — Wi Studio Open Lab

Kumiko is an app-agnostic method for turning a complex product experience into traceable, reusable interface pieces:

Cell → Assembly → Screen → Flow

It is designed for teams that need design, implementation and evidence to stay connected while the product changes.

What is included

• A small JSON registry contract for cells, assemblies and screens.
• A decomposition method with explicit owners, states and trace IDs.
• A validation tool that catches duplicate IDs, missing references and orphan screens.
• Templates that can be adapted to mobile, web or other interface systems.

Quickstart

python3 tools/validate_registry.py examples/minimal-project/kumiko.json

Expected result:

PASS: 3 cells, 2 assemblies, 1 screen; all references resolve.

Core idea

Start with the smallest meaningful visual or behavioral unit. Assemble units only when they share a responsibility. Promote an assembly to a screen only when it has a user-facing purpose, state model and evidence plan. This keeps the system legible and prevents a screen library from becoming a pile of disconnected mockups.

Contract

The public registry is intentionally small. Each item has an id, an owner, a purpose and a list of states. Assemblies reference cells; screens reference assemblies. The validator is deliberately stricter than a free-form design document so a later code generator can trust the graph.

See the method notes and the JSON contract.

What this is not

Kumiko is not a visual UI kit, a replacement for platform guidelines, or a claim that every design decision can be automated. Apple or platform-native behavior remains the authority for the target platform.

License and brand

Code is Apache-2.0. Documentation is CC BY 4.0. The Wi Studio artwork in assets/ is a brand asset and is not covered by either license.

Wi Studio Open Lab · by Wi