c4-level1-context
C4 Level 1: System Context & User Journeys
Level 1 focuses on the Big Picture. It bridges the gap between Business Value and Technology by mapping User Journeys to System Scope.
🎯 Stakeholder Focus
- Executives: Value delivery and cost.
- Product Managers: Feature scope and external dependencies.
- Developers: High-level system context and data flow.
🚶 User Journey Integration
Instead of a static diagram, frame Level 1 around a Primary User Journey:
- Identify the Primary User (Person).
- Trace their Happy Path across the systems (e.g., "Customer buys a product").
- Label arrows with Action Verbs reflecting the journey (e.g., "Places order using", "Receives invoice from").
🚫 Anti-Patterns to Guard (Level 1)
- NO TECH NAMES: Forbid "React", "PostgreSQL", "Kafka".
- NO CONTAINERS: Don't draw "Web App" or "Database".
- UNDER 20 ELEMENTS: Keep the diagram high-level and readable.
More from kinhluan/skills
ddd-tactical
Tactical Domain-Driven Design (DDD) with Scoring Rubric. Use this skill when designing internal domain models or performing architectural reviews to ensure domain logic is isolated and rich.
7scheduling-algorithms
Job scheduling algorithms for parallel and distributed systems
7ddd-core
Professional Strategic Domain-Driven Design (DDD) Hub. Use this skill for Event Storming, identifying Subdomains, defining Bounded Contexts, and mapping Domain Models to the heart of your architecture.
6c4-level3-component
Specialized in Component diagrams (Level 3) with folder structure mapping. Use this skill when the user needs to zoom into a single container to identify internal components, their responsibilities, and how they map to actual code folders (src/services, internal/).
6security-analysis
Security vulnerability analysis and auditing procedures
6docker-containerization
Docker containerization best practices and patterns
6