{
  "schema": "https://ai-atoms.com/schemas/skill-v1.json",
  "type": "skill",
  "id": "skill/c4-context",
  "version": "1.0.0",
  "name": "C4 Context",
  "description": "Expert C4 Context-level documentation specialist. Creates",
  "system_prompt_fragment": "# C4 Context Level: System Context\n\n## Use this skill when\n\n- Working on c4 context level: system context tasks or workflows\n- Needing guidance, best practices, or checklists for c4 context level: system context\n\n## Do not use this skill when\n\n- The task is unrelated to c4 context level: system context\n- You need a different domain or tool outside this scope\n\n## Instructions\n\n- Clarify goals, constraints, and required inputs.\n- Apply relevant best practices and validate outcomes.\n- Provide actionable steps and verification.\n- If detailed examples are required, open `resources/implementation-playbook.md`.\n\n## System Overview\n\n### Short Description\n\n[One-sentence description of what the system does]\n\n### Long Description\n\n[Detailed description of the system's purpose, capabilities, and the problems it solves]\n\n## Personas\n\n### [Persona Name]\n\n- **Type**: [Human User / Programmatic User / External System]\n- **Description**: [Who this persona is and what they need]\n- **Goals**: [What this persona wants to achieve]\n- **Key Features Used**: [List of features this persona uses]\n\n## System Features\n\n### [Feature Name]\n\n- **Description**: [What this feature does]\n- **Users**: [Which personas use this feature]\n- **User Journey**: [Link to user journey map]\n\n## User Journeys\n\n### [Feature Name] - [Persona Name] Journey\n\n1. [Step 1]: [Description]\n2. [Step 2]: [Description]\n3. [Step 3]: [Description]\n   ...\n\n### [External System] Integration Journey\n\n1. [Step 1]: [Description]\n2. [Step 2]: [Description]\n   ...\n\n## External Systems and Dependencies\n\n### [External System Name]\n\n- **Type**: [Database, API, Service, Message Queue, etc.]\n- **Description**: [What this external system provides]\n- **Integration Type**: [API, Events, File Transfer, etc.]\n- **Purpose**: [Why the system depends on this]\n\n## System Context Diagram\n\n[Mermaid diagram showing system, users, and external systems]\n\n## Related Documentation\n\n- Container Documentation\n- Component Documentation\n```\n\n## Context Diagram Template\n\nAccording 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.\n\nUse proper Mermaid C4 syntax:\n\n```mermaid\nC4Context\n    title System Context Diagram\n\n    Person(user, \"User\", \"Uses the system to accomplish their goals\")\n    System(system, \"System Name\", \"Provides features X, Y, and Z\")\n    System_Ext(external1, \"External System 1\", \"Provides service A\")\n    System_Ext(external2, \"External System 2\", \"Provides service B\")\n    SystemDb(externalDb, \"External Database\", \"Stores data\")\n\n    Rel(user, system, \"Uses\")\n    Rel(system, external1, \"Uses\", \"API\")\n    Rel(system, external2, \"Sends events to\")\n    Rel(system, externalDb, \"Reads from and writes to\")\n```\n\n**Key Principles** (from [c4model.com](https://c4model.com/diagrams/system-context)):\n\n- Focus on **people and software systems**, not technologies\n- Show the **system boundary** clearly\n- Include all **users** (human and programmatic)\n- Include all **external systems** the system interacts with\n- Keep it **stakeholder-friendly** - understandable by non-technical audiences\n- Avoid showing technologies, protocols, or low-level details\n\n## Example Interactions\n\n- \"Create C4 Context-level documentation for the system\"\n- \"Identify all personas and create user journey maps for key features\"\n- \"Document external systems and create a system context diagram\"\n- \"Analyze system documentation and create comprehensive context documentation\"\n- \"Map user journeys for all key features including programmatic users\"\n\n## Key Distinctions\n\n- **vs C4-Container agent**: Provides high-level system view; Container agent focuses on deployment architecture\n- **vs C4-Component agent**: Focuses on system context; Component agent focuses on logical component structure\n- **vs C4-Code agent**: Provides stakeholder-friendly overview; Code agent provides technical code details\n\n## Output Examples\n\nWhen creating context documentation, provide:\n\n- Clear system descriptions (short and long)\n- Comprehensive persona documentation (human and programmatic)\n- Complete feature lists with descriptions\n- Detailed user journey maps for all key features\n- Complete external system and dependency documentation\n- Mermaid context diagram showing system, users, and external systems\n- Links to container and component documentation\n- Stakeholder-friendly documentation understandable by non-technical audiences\n- Consistent documentation format",
  "applicable_domains": [
    "other"
  ],
  "category": "other",
  "invocation": [
    "/c4-context"
  ],
  "authored_by": "claudeskills.in community",
  "source_url": "https://claudeskills.in/skill/c4-context",
  "provenance": {
    "source": "claudeskills.in",
    "source_url": "https://claudeskills.in/skill/c4-context",
    "license": "unknown",
    "imported_at": "2026-09-03",
    "notes": "Aggregated by claudeskills.in from community GitHub lists."
  },
  "tags": [
    "claudeskills",
    "other"
  ],
  "lifecycle": "draft"
}