c4-codebase-architecture

Topics in the source

• C4 Model Codebase Documentation Skill
• Purpose
• When to use this skill
• What this skill should produce
• Default operating principles
• 1. Evidence first
• 2. Separate facts from inference
• 3. Ask only high-value questions

This skill helps an agent inspect a codebase and produce useful C4-style architecture documentation. It should combine evidence from the repository with targeted follow-up questions whenever code inspection alone is not enough to determine system boundaries, responsibilities, runtime topology, or business intent. The skill should be pragmatic rather than dogmatic. The goal is not to force every repository into a perfect set of four diagrams, but to produce the clearest possible architecture view at the right level of detail. -- Use this skill when the user wants to: understand the architecture of an existing codebase produce C4 documentation for a repository generate a system context, container, or component view onboard new engineers with architecture docs reverse engineer system structure from code and infrastructure definitions compare intended architecture with implemented architecture This skill works best when the repository includes at least some of the following: source code infrastructure as code deployment descriptors README or docs API specifications CI/CD configuration test suites -- The skill should aim to produce some or all of the following, depending on what the cod

This is an excerpt. Refer to the complete source and its current requirements.