c4-architect_skill

This skill translates complex requirements into clear C4 diagrams (L1-L3) using Mermaid, aligning engineers and stakeholders through living documentation.
  • Python

7

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill yuniorglez/gemini-elite-core --skill c4-architect

  • SKILL.md4.8 KB

Overview

This skill is a Senior Software Architect agent focused on C4 Model visual communication, automated architectural mapping, and Mermaid.js orchestration. It converts system discovery and requirements into clear, multi-level diagrams (Context, Container, Component) that align engineering and business stakeholders. The skill treats diagrams as living documentation and integrates codebase links and verification steps.

How this skill works

The skill inspects codebases and runtime artifacts (services, apps, databases) using automated investigators to extract system structure. It generates Mermaid C4Context/C4Container/C4Component diagram code, inserts titles and legends, and links elements to source directories. It can sequence with renderer and docs skills to validate visuals and embed diagrams as diagram-as-code files or markdown blocks.

When to use it

  • Kickoff architecture reviews to quickly align stakeholders
  • Document system boundaries and external actors before design work
  • Generate deployable-unit maps during refactors or migrations
  • Create component-level diagrams for high-complexity services (auth, payments)
  • Embed living diagrams into PRs and engineering docs for traceability

Best practices

  • Always start at L1 (System Context) to frame boundaries before drilling down to L2/ L3
  • Treat diagrams as living documentation and store them as .mermaid or markdown blocks, not static images
  • Use official Mermaid C4 types (C4Context, C4Container, C4Component) and include a title and Legend on every diagram
  • Link diagram elements to source code paths or comments for traceability
  • Split diagrams with more than ~15 elements into multiple focused views to keep clarity

Example use cases

  • Automate an L2 Container diagram for a monorepo by scanning package.json and service manifests
  • Produce an L1 System Context for stakeholder onboarding that highlights external APIs and deployment targets
  • Generate an L3 Component view for the core Auth service and attach source links for reviewers
  • Integrate diagram generation into CI so PRs include updated .mermaid diagrams and lint checks
  • Render Mermaid diagrams during architecture review sessions and verify relationships against live service discovery

FAQ

No. Manual L4 diagrams go stale quickly. Use automated extraction tools only if you must generate code-level views.

What file formats are recommended for diagrams?

Store diagrams as .mermaid files or embedded markdown blocks. Avoid static image files to keep diagrams up-to-date and machine-readable.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
c4-architect skill by yuniorglez/gemini-elite-core | VeilStrat