flow-map
/flow-map
Rysuje, jak coś płynie od A do B, w trzech małych diagramach Mermaid sprawdzonych wobec źródeł, zapisuje je w Markdown i utrzymuje w aktualności.
- Autor
- Gamebreack ↗
- Repozytorium
- flow-map ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 04.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 3
- Skrypty
- 0
- Komentarze HTML
- 1
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 04.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.
Co robi i kiedy
Rysuje, jak coś płynie od A do B, w trzech małych diagramach Mermaid sprawdzonych wobec źródeł, zapisuje je w Markdown i utrzymuje w aktualności.
Wyzwalacze z opisu
Oryginalny opis (EN)
Draws how something flows from A to B as three small Mermaid diagrams, checked against its sources, saved as Markdown beside them and kept current. Targets - a repo, several repos or a monorepo, a plain folder, or documents (Markdown, Word, PDF). Use to see, map or "understand visually" a service, system, repo(s), process or flow end to end; for a mermaid of the project, an onboarding picture, or to update a flow map. Not for single-class, database schema/ER or one-function diagrams.
Jak działa
- What are we mapping?
- Find A and B
- Status from evidence
- Draw three diagrams
- Checklist
- Write the map
- Fresh review
- Update (a map already exists)
Podgląd SKILL.md
---
name: flow-map
description: Draws how something flows from A to B as three small Mermaid diagrams, checked against its sources, saved as Markdown beside them and kept current. Targets - a repo, several repos or a monorepo, a plain folder, or documents (Markdown, Word, PDF). Use to see, map or "understand visually" a service, system, repo(s), process or flow end to end; for a mermaid of the project, an onboarding picture, or to update a flow map. Not for single-class, database schema/ER or one-function diagrams.
---
# flow-map
Write the map in English, keeping the target's own terms as written. Use another language only if the user asks.
If a map already exists in the target (see Update), update it instead of making a new one.
## What are we mapping?
Decide what the target is and say which in the report: one repo, several repos or a monorepo, a plain folder, or documents.
Several flows: map the one asked for; else ask; if you can't ask, map the largest (most stages backed by sources on both ends), name the others, and say in the map's intro which you picked and why.
Several repos: first read each README or overview, then link repos by the events and APIs they share, not by name.
Where the map goes: `flow-map.md` at the root of the target. Several repos: the folder holding them. Documents: next to them. If unclear, ask.
## Find A and B
A: what starts it (event, request, manual action, schedule, files landing in a folder). A start outside the target (another system, a person, a timer, power-on) is a grey box. B: the target's last step; anything after it outside the target is one grey box after B.
Ask only if A or B is ambiguous.
Read documents (Markdown, Word, PDF) as sources. A file you can't open: report it, never guess its content.
## Status from evidence
**exists**: in the sources. **missing**: the flow needs it (a doc, ticket or promise names it) but no source has it. Never invent missing items.
- Code targets: a step needs code to exist, except a step done by a developer script or by hand (below); a ticket, spec or proposal with no code is missing.
- A step done only by a developer script or by hand exists: draw it as a side path. The product part a source names but nobody built is missing.
- Committed but off by default: exists; the key says it is off by default.
- Claims in docs ("verified", "done") only add detail to a step with code. Documents: the documents are the sources.
- A source too thin to map (only a README, no flow described): report it to the user; do not invent stages.
Map the committed state of the current branch. A step only in uncommitted work is drawn as missing; mention the work in the status line.
Read-only: the map file (plus temporary render files outside the target) is the only thing you write; never change anything else in the target, never commit, never write to any system (production included). Git: read-only commands only (`status`, `log`, `diff`, `show`).
## Draw three diagrams
Blocks and colors: `references/style.md` here.
1. **What happens**: stages A to B, one subgraph per phase, up to 20 boxes and about 20 arrows. Over 20 arrows: keep the main path and every missing item; turn retry and recovery loops into a box line or key note.
2. **Who talks to whom**: systems or parties, the target as one box per repo or system, up to 7 boxes.
3. **The life of one item**: a numbered sequence, up to 5 participants. Self-steps allowed; a participant may stand for "X or Y".
Limits count every box, grey and missing ones too; phase frames do not count. Over a limit: merge, never drop. Box = bold title plus one short line (about 40 characters at most); edge labels 1-3 words. Diagram 1: timers, queues and storage are edge labels or box lines, not boxes, unless they are the point. A two-way link may be one `<-->` edge. An optional alternate path: side-path box, dotted line.
Missing step: red dashed line (diagrams 1–2), red band (diagram 3). Missing stage: box in its phase color labelled "no code yet" ("not described" for documents), red dashed lines in (from whatever would start it, else the phase's first box) and out. A required outside part (auth server, token, provider): grey box, solid line. Dotted = only optional or read-only.
Legend line: `Lines: solid = exists · red dashed or red band = missing · dotted = optional or read-only · "no code yet" (or "not described") box = missing stage · grey = outside the target · light grey dashed box = side path`
## Checklist
Before asking for review, check your draft against this list; the reviewer checks it again. Ask for every step and connection:
- What starts each step, also at startup? (timer, boot, button, event)
- What are the defaults, and what can a user override? (default city, a "simulate" box)
- Is there a dry-run or test mode? (dry-run flag, sandbox)
- What are the recovery and retry paths? (retries, dead-letter, re-login)
- Who is on the other end of every connection? (who publishes, who consumes)
## Write the map
Write the draft from `assets/map-template.md` here: replace the SLOT parts, delete the `<!-- -->` template notes, keep the `%% N:` edge comments. It holds: status line and legend; three diagrams; key, one line per phase; "Where it lives" table, phase to path (`repo · path` for several repos; check every path exists); stamp.
Before saving, check each Mermaid block. If a Mermaid renderer is available (an installed CLI, or `npx -y @mermaid-js/mermaid-cli@11.4.1` only with the user's OK), render each block into a temp folder, never the target. Otherwise re-read each block against the pitfalls in `references/style.md` and tell the user it was not rendered. Fix errors before saving. Then save it to its final path.
Stamp: `Updated <YYYY-MM-DD> · <repo> <branch> <short-sha>`, one line per repo (date only if no git), e.g. `Updated 2026-11-04 · shop-api dev 1a2b3c4`.
## Fresh review
Then, before calling it done, start a fresh agent (a reviewer role if your harness has one). Give it the draft, the source paths and this skill's folder path (rules and checklist), not your conclusions. Tell it to report findings only, not edit the map. It checks every box, arrow and sentence against the sources (file:line evidence, replacement text) and runs the checklist. Terse findings, worst first. Apply its fixes.
No fresh agent possible: the status line starts with "draft — not reviewed"; tell the user.
## Update (a map already exists)
1. Find `flow-map.md`, or a Markdown file with a Mermaid block and a stamp line (date, then per repo its name, branch, short SHA). Keep the map's language.
2. Per stamped repo, diff the stamped commit to the current branch (commit gone: commits since the stamp date); date-only: files changed since. Say which.
3. Edit only what moved, recheck those statuses, check the Mermaid as in Write the map, get a fresh review of the changes, write a new stamp.
4. No flow impact: only the stamp changes; say the map did not move.
Report, short: target type, where the map is, what it shows, what is missing, other flows not drawn, and any caveat (review skipped; diff base approximated).
Pliki w paczce (3)
- SKILL.md 7 KB
- assets/map-template.md 7 KB
- references/style.md 2 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · Gamebreack/flow-map | 90 | MIT |
| omexit/claude-skills-pack | 100 | MIT |
| naticorrea-03/claude-code-skills | 100 | MIT |
| benjoox/code-viz | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki d382d2a50a13 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 90codemap
Śledzi jeden przepływ w kodzie i zapisuje go jako mapę markdown z diagramem Mermaid oraz odnośnikami do plików. - 100mermaid-diagrams
Tworzy diagramy oprogramowania w Mermaid: przepływy, sekwencje, klasy, ERD, C4, stany, git, kołowe i Gantta, do dokumentowania architektury, bazy danych i ścieżek użytkownika. - 100mermaid-diagrams
Tworzy i dopracowuje diagramy Mermaid z podglądem na żywo, używając narzędzi mermaid_preview i mermaid_save oraz dobrych praktyk składni i stylu. - 100mermaid-diagrams
Tworzy lub naprawia diagramy Mermaid w markdownie: przepływy, sekwencje, ER, maszyny stanów i diagramy systemowe, gdy Mermaid jest formatem wyjściowym. - 100diagramming
Rysuje diagramy architektury i przepływów jako kod (Mermaid, C4, sekwencje, ER, stany), które zostają w kontroli wersji i nie starzeją się. - 100wavelength-map-code-to-flow
Rysuje w repozytorium przepływ procesu dla pliku, funkcji lub usługi, żeby opisać, jak działa kod.