Run any Skill in Manus with one click

architecture-map

Stars0

Forks0

UpdatedJuly 19, 2026 at 06:41

Ideal target-state file map for KyzoDB — where each seat lives and what it owns. Use before placing a construct, naming a file, choosing a zone, or judging whether code sits in the wrong place. Not current-tree inventory (read the tree) and not per-construct coding law (rust-* skills).

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

kyzodb

kyzodb/kyzo

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	architecture-map
description	Ideal target-state file map for KyzoDB — where each seat lives and what it owns. Use before placing a construct, naming a file, choosing a zone, or judging whether code sits in the wrong place. Not current-tree inventory (read the tree) and not per-construct coding law (rust-* skills).

The Architecture Map

Authority: target-arch.md — flat list of ideal target paths with a one-line role for each seat.

Read that file when seating or renaming work. Do not invent a parallel map. Update target-arch.md when the ideal layout changes.

More from this repository

same repository

wise-architect-review

kyzodb/kyzo

The review lens for judging any code, seal, or story against the storage architecture's caliber — not "did it pass the meter" but "is this the best it can be." Use when QA'ing a sealed task, assessing a story, or judging whether built code rises to decisions.md and the storage architecture. Not a checklist pass; a wisdom pass.

2026-07-190

qae-context-creator

kyzodb/kyzo

Create precise, high-context direction for LLMs as Q/A/E triplets — the hardest question, the ruled answer, the enforcement that makes it stick. Use when writing specs, rulings, migration destinies, agent priming, review standards, or any context where an LLM must make a choice exactly the way you would.

2026-07-190

closure-check

kyzodb/kyzo

Gate whether a working set of atoms/clusters is closed under dependency edges (OPEN lists crossings). Use after organize-work when the border must be a real min-cut. Not organize-work. Not architecture-design.

2026-07-180

io-inversion

kyzodb/kyzo

Hoist all reads to session entry and sink all writes to session exit around a pure Decision middle. Use when a host/session path mixes IO with meaning. Not name-and-seat-construct. Not organize-work.

2026-07-180

name-and-seat-construct

kyzodb/kyzo

Name a construct's kind of truth and seat it in exactly one zone (KEEP or SPLIT). Use when placing or splitting a type/module/bag under zone law and future pressure. Not io-inversion. Not architecture-design. Not organize-work.

2026-07-180

organize-work

kyzodb/kyzo

Partition stories/requirements into MECE clusters ordered by dependency. Use when re-slicing many items on wrong seams or turning planning smear into a build partition. Not closure-check (border gate). Not architecture-design. Not write-story.

2026-07-180

Run any Skill with one click