Skip to content

FISCFED9/CLI / .agents/skills/plugins/antigravity-awesome-skills-claude/skills/c4-context

c4-context

Verified

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

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

[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
  • Stakeholder-friendly documentation understandable by non-technical audiences
  • Consistent documentation format
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 466kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 196kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 196kUpdated Claude CodeCodexVerifiedInstall