원클릭으로 Manus에서 모든 스킬 실행

okhp3-mermaid-architecture

스타3

포크0

업데이트2026년 6월 23일 04:17

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.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

OKHP3

OKHP3/mermaid-diagram-bpmn

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

OKHP3 Mermaid Architecture

System/solution architecture vocabulary, loaded after okhp3-mermaid-core.

C4 Layering

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.

Architecture-beta Diagrams

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).

Solution Patterns

Integration flows, service topology, data flow diagrams. See references/solution-patterns.md.

Block & Packet Diagrams

For high-level system overviews (block-beta) and protocol/network-level detail (packet-beta), routed here from core's type matrix. Patterns TBD — Phase 2.

Cross-diagram zoom coherence

When the same system appears at multiple C4 layers, each diagram should be independently valid (passes all 3 gates on its own) AND collectively coherent (container names match between Context and Container layers, etc.). This is a Gate 2 (semantic) check that spans multiple files — flag inconsistencies even though each individual diagram might pass its own Gate 2.

이 저장소의 다른 Skills

같은 저장소

okhp3-foundry-repo-creator

OKHP3/mermaid-diagram-bpmn

Create governed FoundRy child repositories from Custom GPTs, Gemini Gems, Copilot agents, prompt bundles, Notion concepts, research notes, or prototype ideas. Use whenever the user wants to migrate an AI capability into GitHub, standardize a repo, create a child repo scaffold, or convert platform-specific AI work into a reusable capability package.

2026-06-263

okhp3-skill-foundry

OKHP3/mermaid-diagram-bpmn

OverKill Hill P³ Skill Foundry -- complete eight-phase methodology for creating, honing, and polishing production-quality Agent Skills. Activate when asked to create a new skill from scratch, hone or polish an existing skill, apply OKHP3 brand attribution, design live evals, run executor subagents for benchmarking, grade responses with evidence-anchored expectations, compute benchmark deltas, or iterate based on eval failures. Also activate when someone wants to turn a workflow into a distributable skill, needs to benchmark a skill's with-skill vs without-skill gap, wants a professional quality bar for a SKILL.md, or asks about the OKHP3 skill authoring process. This is the authoritative Foundry methodology for any skill creation or honing work in this repo -- use it even when the user just says "make a new skill" or "improve this skill" without mentioning the Foundry by name.

2026-06-263

okhp3-as-is-process-capture

OKHP3/mermaid-diagram-bpmn

Capture and normalise a current-state process description into a structured as-is process YAML with stable step identifiers. Use this skill when the user has a process that is already running and needs to document its current state before gap analysis or redesign; when they provide step lists, SOPs, or process notes that need to be structured; when they say "document what we do today", "capture the current process", or "baseline the process before we change it". Produces a structured as-is process artifact with normalised step IDs.

2026-06-243

okhp3-decision-model-authoring

OKHP3/mermaid-diagram-bpmn

Author and validate decision models from PNS decision points using DMN-aligned rule tables. Use this skill when the PNS contains three or more gateway decision points that warrant a structured decision table; when the user asks to document business rules as decision logic, build a DMN table, or make decision criteria explicit. This is a recommended extension skill triggered automatically when visual-process-modeling identifies three or more gateways. Produces a decision-model YAML and a human-readable DMN rule table.

2026-06-243

okhp3-elicitation-and-interview-facilitation

OKHP3/mermaid-diagram-bpmn

Plan and facilitate structured elicitation sessions using BABOK v3 interview and workshop techniques. Use this skill when you need to gather process knowledge from subject matter experts; when the user wants a question plan before an interview or workshop; when elicitation is incomplete and gaps need targeted follow-up; when they say "help me interview the process owner", "prepare questions for the workshop", or "what should I ask to fill in the missing steps". Produces a question plan and elicitation notes template.

2026-06-243

okhp3-future-state-and-change-strategy

OKHP3/mermaid-diagram-bpmn

Design a target-state process and a structured change strategy from a gap analysis. Use this skill when the user wants to redesign a process after gaps have been identified; when they ask "what should the process look like", "how do we fix this", "design the to-be process", or "build a change plan". Produces a future-state process artifact and a change strategy document. This is a recommended extension skill — use after process-gap-and-exception-analysis has produced a gap analysis. Scope firewall applies: never include employer-proprietary constraints without explicit user authorisation.

2026-06-243

name

okhp3-mermaid-architecture

description

OKHP3 Mermaid Architecture

System/solution architecture vocabulary, loaded after okhp3-mermaid-core.

C4 Layering

Architecture-beta Diagrams

Solution Patterns

Integration flows, service topology, data flow diagrams. See references/solution-patterns.md.

Block & Packet Diagrams

For high-level system overviews (block-beta) and protocol/network-level detail (packet-beta), routed here from core's type matrix. Patterns TBD — Phase 2.