Architecture diagram
Draw how a system fits together -- components, data flow, a request's path, a data model -- as a Mermaid diagram with a short note on what it shows.
In Lobstack: Skills › Library › Add
What your agent will do.
Someone asks how a system works, wants a diagram for docs or a design review, or is about to change how parts connect.
- 01
Read the code and config before drawing: entry points, services, queues, stores, external APIs, and how they call each other. Draw what is there.
- 02
Pick one question per diagram: what the parts are (flowchart LR with subgraphs per boundary), how one request flows (sequenceDiagram), or how data is shaped (erDiagram).
- 03
Keep it to five to fifteen nodes with two or three word labels. Put protocols or payloads on the arrows, not in the boxes.
- 04
Post it with post_diagram, then a short post_document: what each part owns, where the risks and single points of failure are, and the file each claim came from.
- 05
For a proposed change, draw the before and the after as two diagrams.
Never commit a diagram to a repository or wiki without asking.
The whole SKILL.md: 29 lines of Markdown.
Add it in the app from Skills › Library, or copy it and paste it into Skills › Add a skill.
---name: architecture-diagramdescription: "Draw how a system fits together -- components, data flow, a request's path, a data model -- as a Mermaid diagram with a short note on what it shows."metadata: title: "Architecture diagram" category: engineering tags: [architecture, diagrams, docs]--- ## When to use this Someone asks how a system works, wants a diagram for docs or a design review, oris about to change how parts connect. ## How 1. Read the code and config before drawing: entry points, services, queues, stores, external APIs, and how they call each other. Draw what is there.2. Pick one question per diagram: what the parts are (flowchart LR with subgraphs per boundary), how one request flows (sequenceDiagram), or how data is shaped (erDiagram).3. Keep it to five to fifteen nodes with two or three word labels. Put protocols or payloads on the arrows, not in the boxes.4. Post it with post_diagram, then a short post_document: what each part owns, where the risks and single points of failure are, and the file each claim came from.5. For a proposed change, draw the before and the after as two diagrams. Never commit a diagram to a repository or wiki without asking.
- Engineering
Commit message from a diff
Write a commit message from a diff: a subject line that states what was found, then prose explaining why the change was made.
SKILL.md · App - Engineering
Triage a failing build
Triage a red CI run: find the first real failure, attribute it to a change, and say whether the code is wrong or the runner was.
SKILL.md · App - Engineering
Review what a linter cannot
Review a change for what a linter cannot see: whether it is correct, what it breaks elsewhere, and which parallel list it forgot to update.
SKILL.md · App - Engineering
Pull request description
Write a pull request description from the diff: why it exists, what changed, how it was tested, and where a reviewer should look first.
SKILL.md · App - Engineering
Incident postmortem
Write a blameless postmortem from an incident's alerts, logs and chat: timeline, impact, root cause, and actions with owners.
SKILL.md · App - Engineering
Reproduce a bug before fixing it
Fix a bug by reproducing it first: turn the report into a failing test or script, shrink it, make the smallest fix, and show the test pass.
SKILL.md · App