System mapping
Skill charlieviettq/awesome-agent-skill/.cursor/skills/architecture/system-mapping
Curated skill pack for LLM agents in engineer and science workflow (Cursor & Claude ready).
npx -y skills add charlieviettq/awesome-agent-skill --skill system-mappingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 22 stars22 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Map systems with diagrams—components, data flows, feedback loops, and causal relationships. Use for architecture understanding or stakeholder communication. Triggers: "system map", "architecture diagram", "data flow", "C4", "how does this fit together".
SKILL.md
1.7 KB, as published. Nobody here has run it
System Mapping
Lightweight system mapping before deep implementation or refactor. Produces diagrams and narrative that clarify boundaries and dependencies.
When to use
- Onboarding to unfamiliar codebase or pipeline
- Planning integration between services
- Explaining credit/ML/data flows to stakeholders
When not to use
- Formal ADR decision (use
architecture-decision-records) - Auto-generating code from diagram
Workflow
- Scope — system boundary; actors; in/out of scope
- Components — services, stores, queues, humans, external APIs
- Flows — primary happy path; note sync vs async
- Feedback — loops, retries, batch vs realtime
- Risks — single points of failure, PII paths, manual steps
- Diagram — Mermaid or C4-style; keep readable in markdown
Diagram tips
- Start context/container level; drill to component only where needed
- Label data classifications on flows with sensitive data
- Version diagram with date in doc title or footer
Output template
## System map: [name]
- **Purpose:**
- **Actors:**
- **Components:** (table: name, role, owner)
- **Primary flows:**
- **Diagram:** (mermaid block)
- **Open questions:**
Related skills
architecture-decision-records— record resulting decisionsdoubt-driven-review— challenge critical assumptionsinternal-credit-train-lifecycle— credit platform context (if available)
Clean-room system mapping workflow.