Skip to content
Skillpedia
Documentation48k · #2487

c4-context

Helps your agent create high-level C4 context diagrams. It documents users, journeys, features, and external system dependencies.

What it does

Helps create high-level documentation for a software system, focusing on how it interacts with people and other systems. It's like a map showing who uses the system and what it connects to.

When to use it

  • ✓When starting a new project to understand the overall scope.
  • ✓When needing to explain the system to non-technical people.
  • ✓When documenting interactions between the system and its users or other software.

Example of what to ask your AI

“Create the system context documentation for an e-commerce application.”

Want more? Open the sections below.

How to use

The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.

Skill link

https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/c4-context/SKILL.md

Ready-to-paste message

Use this skill to help me: https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/c4-context/SKILL.md Read the SKILL.md file at that link and follow its instructions for my task.
How it works

The AI asks for information about the system, its users, and other systems it communicates with. It then organizes this information and can even generate a simple visual diagram.

Installation

Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.

In the terminal (Claude Code, Codex, Cursor), in your project folder:

npx skills add sickn33/agentic-awesome-skills --skill c4-context

Or download just the file:

curl -L https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/main/plugins/agentic-awesome-skills-claude/skills/c4-context/SKILL.md -o SKILL.md
Technical content (original SKILL.md)

Original text by the author, straight from GitHub.

C4 Context Level: System Context

Use this skill when

  • Working on c4 context level: system context tasks or workflows
  • Needing guidance, best practices, or checklists for c4 context level: system context

Do not use this skill when

  • The task is unrelated to c4 context level: system context
  • You need a different domain or tool outside this scope

Instructions

  • Clarify goals, constraints, and required inputs.
  • Apply relevant best practices and validate outcomes.
  • Provide actionable steps and verification.

System Overview

Short Description

[One-sentence description of what the system does]

Long Description

[Detailed description of the system's purpose, capabilities, and the problems it solves]

Personas

[Persona Name]

  • Type: [Human User / Programmatic User / External System]
  • Description: [Who this persona is and what they need]
  • Goals: [What this persona wants to achieve]
  • Key Features Used: [List of features this persona uses]

System Features

[Feature Name]

  • Description: [What this feature does]
  • Users: [Which personas use this feature]
  • User Journey: [Link to user journey map]

User Journeys

[Feature Name] - [Persona Name] Journey

  1. ...

[External System] Integration Journey

  1. ...

External Systems and Dependencies

[External System Name]

  • Type: [Database, API, Service, Message Queue, etc.]
  • Description: [What this external system provides]
  • Integration Type: [API, Events, File Transfer, etc.]
  • Purpose: [Why the system depends on this]

System Context Diagram

[Mermaid diagram showing system, users, and external systems]

Related Documentation

  • Container Documentation
  • Component Documentation

## Context Diagram Template

According to the [C4 model](https://c4model.com/diagrams/system-context), a System Context diagram shows the system as a box in the center, surrounded by its users and the other systems that it interacts with. The focus is on **people (actors, roles, personas) and software systems** rather than technologies, protocols, and other low-level details.

Use proper Mermaid C4 syntax:

```mermaid
C4Context
    title System Context Diagram

    Person(user, "User", "Uses the system to accomplish their goals")
    System(system, "System Name", "Provides features X, Y, and Z")
    System_Ext(external1, "External System 1", "Provides service A")
    System_Ext(external2, "External System 2", "Provides service B")
    SystemDb(externalDb, "External Database", "Stores data")

    Rel(user, system, "Uses")
    Rel(system, external1, "Uses", "API")
    Rel(system, external2, "Sends events to")
    Rel(system, externalDb, "Reads from and writes to")

Key Principles (from c4model.com):

  • Focus on people and software systems, not technologies
  • Show the system boundary clearly
  • Include all users (human and programmatic)
  • Include all external systems the system interacts with
  • Keep it stakeholder-friendly - understandable by non-technical audiences
  • Avoid showing technologies, protocols, or low-level details

Example Interactions

  • "Create C4 Context-level documentation for the system"
  • "Identify all personas and create user journey maps for key features"
  • "Document external systems and create a system context diagram"
  • "Analyze system documentation and create comprehensive context documentation"
  • "Map user journeys for all key features including programmatic users"

Key Distinctions

  • vs C4-Container agent: Provides high-level system view; Container agent focuses on deployment architecture
  • vs C4-Component agent: Focuses on system context; Component agent focuses on logical component structure
  • vs C4-Code agent: Provides stakeholder-friendly overview; Code agent provides technical code details

Output Examples

When creating context documentation, provide:

  • Clear system descriptions (short and long)
  • Comprehensive persona documentation (human and programmatic)
  • Complete feature lists with descriptions
  • Detailed user journey maps for all key features
  • Complete external system and dependency documentation
  • Mermaid context diagram showing system, users, and external systems
  • Links to container and component documentation

…

FAQ

What is a context diagram?

It's a simple drawing showing the system in the center, with boxes around it representing the people and other systems that interact with it.

What is context documentation used for?

It provides an overview of the system, who uses it, and what it connects to, in a way that anyone can understand, even without a technical background.

What information is needed?

Information about what the system does, who the users are (people or other programs), what features it offers, and what other systems it uses or connects to.

Details

Original description by the author

Expert C4 Context-level documentation specialist. Creates high-level system context diagrams, documents personas, user journeys, system features, and external dependencies.

repo: sickn33/agentic-awesome-skills

Popularity

GitHub stars
48k
Ranking position
#2487
License
MIT
Updated
10/15/2026

Is this skill useful?

0

Sign in to vote.

Comments

  • …

More skills from this repository

Similar skills