okhp3-mermaid-architecture
System and solution architecture diagrams in Mermaid for technical audiences - C4 model (Context/Container/Component/Code), architecture-beta cloud/infrastructure diagrams, block diagrams, packet/protocol diagrams, service topology, and integration flows. Use when the user wants to diagram software architecture, infrastructure, deployments, service relationships, or "how systems connect." Always load okhp3-mermaid-core first for audience/type/theming.
Target: Software development & testing. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- okhp3-mermaid-architecture
- C4 Layering
- Architecture-beta Diagrams
- Solution Patterns
- Execution contract
- Block & Packet Diagrams
- Cross-diagram zoom coherence
- Scope
OverKill Hill P³ · overkillhill.com · github.com/OKHP3 System/solution architecture vocabulary, loaded after okhp3-mermaid-core. Context → Container → Component → Code. Each layer is typically a separate diagram (per core's splitting guidance), cross-referenced in DIAGRAMS.md. The same system at multiple zoom levels is a feature, not duplication - see references/c4-patterns.md for layer-by-layer guidance and what belongs at each zoom level. The newer Mermaid architecture syntax (architecture-beta) for cloud/infrastructure: groups, services, edges with directional sides (L/R/T/B), junctions for layout control. See references/architecture-beta.md for syntax and the known layout limitations (siblings sharing logical position, fcose layout tuning via idealEdgeLengthMultiplier). Declare the audience and zoom level before selecting Context, Container, Component, Code, block, or packet notation. Separate confirmed systems from proposed systems and label assumptions. Keep names stable across views, validate every cross-view relationship, and do not invent services, boundaries, protocols, or deployment details. Integration flows, service topology, data flow diagrams. See references/solution
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- OKHP3/skillz
- Source file
- mermaid/okhp3-mermaid-architecture/SKILL.md
- Fixed revision
- 7b187777d42ab7bc7bab1e5f2c940cd3139ecebf
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: OKHP3/skillz · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-10T10:00:55.051Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.