slide-arch-diagram
Slide Arch Diagram
npx skills add https://github.com/peter-tu-zynkr/zynkr-skill-builder --skill slide-arch-diagram
Turns one ideated business workflow into a slide-ready architecture diagram: three horizontal lanes (前端 Front End · 後端 Back End · 資料庫 Database) with the workflow's IPO stitched left→right across them, closed by a single orange law-line verdict. Trigger it whenever a workflow needs to be drawn as an architecture view on an artifact deck — 「畫成架構圖」「畫 FE/BE/DB」"draw this workflow as an architecture diagram" — or when slide-visual-selector routes an architecture-flavoured process page here.
What this is
A business workflow drawn as architecture, not as a flowchart. The three lanes answer "who owns this?" — the human surface (FE), the execution and its rules (BE), the stored state and knowledge (DB) — and the workflow's IPO pushes left→right across them. One diagram = one workflow = one page.
The point of the drawing is the placement discipline behind it: if you can place every element of a workflow into the right lane, you have already answered what can be automated, what knowledge must be written down first, and where the human stays in the loop. The diagram is that argument made visible.
Core mental model (canonical, load the full version from ./references/canonical-model.md):
- FE — Interaction & Intent: where humans interact; captures inputs and commands, presents outcomes. FE shows intent, it never owns rules.
- BE — Execution & Meaning: where work is orchestrated and rules are enforced; the canonical source of meaning. Every process node lives here.
- DB — State & Knowledge: durable state and codified knowledge that feed execution. An index or a context window is never the system of record.