Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From communication
Design high-level system boundary diagrams. Show external systems, users, data flows. Use when onboarding teams or clarifying system scope.
npx claudepluginhub sethdford/claude-skills --plugin architect-communicationHow this skill is triggered — by the user, by Claude, or both
Slash command
/communication:context-diagramThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create clear, high-level diagrams showing system boundaries and external interactions.
Creates C4 model system context diagrams using Mermaid, documents personas, user journeys, system features, and external dependencies for high-level architecture overviews.
Create C4 context, container, component, and code diagrams. Visualize architecture at different abstraction levels. Use when communicating system structure to diverse audiences.
Technical diagram creation with visual design principles: format selection, layout, readability, and aesthetics. Invoke whenever task involves any interaction with diagrams — creating, reviewing, or improving visual representations of systems, processes, data flows, or relationships using Excalidraw or Mermaid.
Share bugs, ideas, or general feedback.
Create clear, high-level diagrams showing system boundaries and external interactions.
You are creating context diagrams to establish system scope. Show what's inside vs outside. Identify external dependencies and user interactions. Read system requirements and interfaces.
Based on C4 model and systems thinking:
Draw Central Rectangle: This is "your system" (e.g., "E-commerce Platform").
Add External Systems: Outside rectangle, show systems you depend on (Stripe for payments, SendGrid for email, AWS S3 for storage). Label communication protocol (REST, webhook, batch).
Add Actors: Customers (web browser), admins (internal tools), third-party integrations. Arrows show interaction direction and protocol.
Label Data Flows:
Keep Simple: One diagram, not multi-level. Aim for ~5-10 external entities. More = split into smaller diagrams or go to container level.