Files
pi-skill/skills/references/type-architecture.md
2026-05-25 16:41:08 +07:00

998 B
Raw Permalink Blame History

Architecture

Best for: system overviews, data-flow diagrams, integration maps, infra topology.

Layout conventions

  • Group components by tier or trust boundary (frontend → backend → data; public → private).
  • Primary flow runs left→right or top→down. Pick one and hold it.
  • Draw arrows before boxes so z-order puts connections behind components.
  • 12 coral focal nodes: the primary integration point, the primary data store, or the key decision node.
  • Dashed boundary rectangles mark regions (VPC, security group, trust zone); labels sit on a paper-colored mask over the boundary line.

Anti-patterns

  • Every box in coral ("this is important too") — hierarchy collapses.
  • Bidirectional arrow when one direction is obvious from context.
  • Legend floating inside the diagram area.

Examples

  • assets/example-architecture.html — minimal light
  • assets/example-architecture-dark.html — minimal dark
  • assets/example-architecture-full.html — full editorial