MR
Mayur Rathi
@mayurrathi
⭐ 40.7k GitHub stars

C4 Context

C4 Context is an code AI skill with a core value of |. It helps developers solve real-world problems in the code domain, boosting efficiency, automating repetitive tasks, and optimizing workflows.

|

Last verified on: 2026-07-08

Quick Facts

Category code
Works With Claude
Source sickn33/antigravity-awesome-skills
Stars ⭐ 40.7k
Last Verified 2026-07-08
Risk Level Low
mkdir -p ./skills/c4-context && curl -sfL https://raw.githubusercontent.com/sickn33/antigravity-awesome-skills/main/skills/c4-context/SKILL.md -o ./skills/c4-context/SKILL.md

Run in terminal / PowerShell. Requires curl (Unix) or PowerShell 5+ (Windows).

Skill Content

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

- If detailed examples are required, open `resources/implementation-playbook.md`.


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. [Step 1]: [Description]

2. [Step 2]: [Description]

3. [Step 3]: [Description]

...


[External System] Integration Journey


1. [Step 1]: [Description]

2. [Step 2]: [Description]

...


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

text

## 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:

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

text

**Key Principles** (from [c4model.com](https://c4model.com/diagrams/system-context)):

- 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 log

🎯 Best For

  • Claude users
  • Software engineers
  • Development teams
  • Tech leads

💡 Use Cases

  • Code quality improvement
  • Best practice enforcement

📖 How to Use This Skill

  1. 1

    Install the Skill

    Copy the install command from the Terminal tab and run it. The SKILL.md file downloads to your local skills directory.

  2. 2

    Load into Your AI Assistant

    Open Claude and reference the skill. Paste the SKILL.md content or use the system prompt tab.

  3. 3

    Apply C4 Context to Your Work

    Open your project in the AI assistant and ask it to apply the skill. Start with a small module to verify the output quality.

  4. 4

    Review and Refine

    Review AI suggestions before committing. Run tests, check for regressions, and iterate on the skill output.

❓ Frequently Asked Questions

Is C4 Context compatible with Cursor and VS Code?

Yes — this skill works with any AI coding assistant including Cursor, VS Code with Copilot, and JetBrains IDEs.

Do I need specific dependencies for C4 Context?

Check the install command and Works With section. Most code skills only require the AI assistant and your codebase.

How do I install C4 Context?

Copy the install command from the Terminal tab and run it. The skill downloads to ./skills/c4-context/SKILL.md, ready to use.

Can I customize this skill for my team?

Absolutely. Edit the SKILL.md file to add team-specific instructions, examples, or workflows.

⚠️ Common Mistakes to Avoid

Skipping validation

Always test AI-generated code changes, even for simple refactors.

Missing dependency updates

Check if the skill requires updated dependencies or new packages.

🔗 Related Skills