- tools/ui_map.mjs find <words on screen | key | /anomalous/route | file.js>, read from the code each time (tools/ui_map_scan.mjs: the words, what each web file shows and calls, its CSS classes, imports, the backend's routes); build writes the whole map to the untracked docs/ui-map.md, with the routes no page calls and the words no file uses. - docs/architecture/ui-flows.md: the hand-written part for the AI workbench (what each part is for, what a click does, why) and a glossary of one name per thing. The structure check fails when a word in it is no longer on screen, a file or route it names is gone, or a retired name is back on screen. - One name each on the AI page: 素材 (not 材料), 留言 (not 消息), 节点结构 (the / command too), 连接 for the last AI, 副本 for the task's tab, 撤销; English "Node map". - AGENTS.md: look a button up with the map before changing it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.8 KiB
1.8 KiB
Architecture Topic Guide
Start with the repository-root ARCHITECTURE.md, then
open only the topic needed for the current task.
ui-flows.md: the UI map's hand-written part, in Chinese: what each part of a page is for, what a click does and why, and one name per thing (a glossary the structure check enforces). Where a word on screen is drawn and what it calls comes from the code:node tools/ui_map.mjs find <words>(tools/ui_map.mjs, its indextools/ui_map_scan.mjs;buildwrites the whole map to the untrackeddocs/ui-map.md).backend.md: Python routes, filesystem safety, persistence, scan state, model sidecars, and backend performance.frontend.md: extension bootstrap, UI ownership, localization, media lifecycle, panel state, and graph mutations.recipes.md: Workflow Recipes, packages, galleries, Parameter Notebooks, prompt roles, and recipe-to-model transitions.material-library.md: saved prompts and node values (material files), keeping an output image, and dragging prompts onto the canvas.recipe-model-lifecycle.md: authoritative model fields, Hash synchronization, local matching, partial append, and note privacy.model-resolution.md: model provenance, Model Check, hash injection, model scanning, and recovery policy.../decisions/README.md: concise records of product and architectural decisions that still explain current behavior.
These documents describe current contracts rather than implementation history.
For exact changes, use Git history. For user-visible releases, use
CHANGELOG.md. For recurring implementation traps, use
lessons.md.