Initial: pi-skill — 68 skills, 43 extensions, 11 themes for Pi
This commit is contained in:
20
skills/references/type-architecture.md
Normal file
20
skills/references/type-architecture.md
Normal file
@@ -0,0 +1,20 @@
|
||||
# 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.
|
||||
- 1–2 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
|
||||
Reference in New Issue
Block a user