Przejdź do treści
Biblioteka skilli
Programowanie · Budowanie i kod

draw-flow

/draw-flow

Rysuje, jak system lub proces naprawdę działa, w diagramach Mermaid, z jednym przepływem na diagram i ścieżkami błędów, sprawdzonymi poprawnie.

Repozytorium
ai-worker ↗
Licencja
MIT
Ostatnia zmiana repozytorium
13.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Rysuje, jak system lub proces naprawdę działa, w diagramach Mermaid, z jednym przepływem na diagram i ścieżkami błędów, sprawdzonymi poprawnie.

Oryginalny opis (EN)

Draw how a system or process really works as Mermaid diagrams, one flow per diagram, including the paths that fail, checked so they display correctly. Use when the user types /draw-flow, asks for a flow, flowchart, sequence diagram or Mermaid diagram, or wants to see how the parts of a system connect. Vẽ cách một hệ thống hay quy trình thực sự chạy bằng sơ đồ Mermaid, mỗi sơ đồ một luồng, gồm cả nhánh thất bại, có kiểm để hiển thị đúng. Dùng khi người dùng gõ /draw-flow, nhờ vẽ flow, lưu đồ, sơ đồ tuần tự, sơ đồ Mermaid, hoặc muốn xem các phần của hệ thống nối với nhau ra sao.

Jak działa

  1. Input
  2. How to do it
  3. Choosing the type
  4. Drawing rules
  5. Syntax rules
  6. Checking that it displays
  7. Example
  8. Limits
Sekcje z nagłówków SKILL.md, w oryginale · 87 linii, 947 słów
Podgląd SKILL.md
---
name: draw-flow
description: Draw how a system or process really works as Mermaid diagrams, one flow per diagram, including the paths that fail, checked so they display correctly. Use when the user types /draw-flow, asks for a flow, flowchart, sequence diagram or Mermaid diagram, or wants to see how the parts of a system connect. Vẽ cách một hệ thống hay quy trình thực sự chạy bằng sơ đồ Mermaid, mỗi sơ đồ một luồng, gồm cả nhánh thất bại, có kiểm để hiển thị đúng. Dùng khi người dùng gõ /draw-flow, nhờ vẽ flow, lưu đồ, sơ đồ tuần tự, sơ đồ Mermaid, hoặc muốn xem các phần của hệ thống nối với nhau ra sao.
---

# Draw a flow

Answer and write the labels in the user's language.

Purpose: a reader sees how something really happens, including where it can refuse or fail, without anyone explaining the diagram.

## Input
`$ARGUMENTS`: the flow to draw. It may be a system in a project, or a process the user describes.

## How to do it
1. **Find what really happens.** In a project, follow the code from the first step to the last. Every step in the diagram must be something you saw. For a process the user describes, the user is the evidence. Mark what you could not confirm as `[to confirm]` in its label.
2. **Fix the scope:** one diagram, one flow, with one trigger and a clear end. "Everything about logging in" is several flows. If the request covers several, draw each one and say so.
3. **Choose the type** from the table below.
4. **Draw it** by the drawing and syntax rules below.
5. **Write one or two sentences above the diagram** on what the picture cannot show: why it works this way, or what the reader should notice. Do not retell the steps.
6. **Check that it displays** (see below).
7. **Save it** as a fenced `mermaid` block in the document it belongs to, or in `docs/` if there is none. If the project keeps documents in two languages, write both, with translated labels.
8. **Report in a few lines:** where it was saved, how it was checked, and every `[to confirm]`.

## Choosing the type
| What the reader needs to see | Type |
|---|---|
| The parts of a system and what connects them | `flowchart LR`, with `subgraph` for each machine or owner |
| Steps with decisions and branches | `flowchart TD` |
| A few steps in a straight line | `flowchart LR` |
| Messages between parties, in order | `sequenceDiagram` |
| The states one thing moves through | `stateDiagram-v2` |

If time order between two or more parties matters, use a sequence diagram. If the choices matter more, use a flowchart.

## Drawing rules
- Fifteen nodes or fewer, or about fifteen messages. Past that, split it.
- Every decision is a question, with every answer labelled. Include the "no" and the failure paths: they are usually why the diagram is worth drawing.
- In a sequence diagram, one party checking something itself is an arrow to itself, with the refusal in the text: `W->>W: Check the key, else 401`.
- Every path reaches an end. A branch that stops in the middle means a step is missing.
- A label names one action, verb first, in a few words. Use the words the code or the spec uses.
- A solid arrow is what the system does. Use a dotted arrow (`-.->`) for what a person does by hand.
- Name real things where the reader may look for them: file names, paths, status codes.
- No colors or styles unless the color carries meaning.

## Syntax rules
Start every flowchart with this line, because labels drawn as HTML can be cut off in some browsers even when the diagram looks right in yours:
`%%{init: {"htmlLabels": false, "flowchart": {"htmlLabels": false}}}%%`

Breaking any of these stops the whole diagram from displaying:
- Put every node label in double quotes: `Check["Verify (again)"]`, `Own{"Own key?"}`. Brackets in an unquoted label are an error.
- Do not use lowercase `end` as a node ID. Use `Done` or `Stop`.
- In a sequence diagram, do not use a semicolon in message text: it cuts the message off.
- Close each `alt`, `loop`, `opt` and `subgraph` with its own `end`.

Two habits keep the source easy to read and change:
- Node IDs are short and ASCII (`Check`, `Sig`). Other languages go in the labels.
- Write a double quote inside a label as `#quot;`, and a line break as `<br/>`.

## Checking that it displays
Use the first of these that works, and say which one you used:
1. `mmdc -i <file>.mmd -o <file>.svg`, if the Mermaid command line tool is installed.
2. A preview that can display Mermaid on this computer. A local page that loads the Mermaid library and draws in the browser counts, because the diagram stays on this computer.
3. If neither works, write "not displayed yet" in your report. Do not say it works.

Do not paste diagrams with internal names into an online editor, which keeps them on someone else's server.

Then read the result as a stranger: does each arrow follow from the one before it, and does each label fit?

## Example
A person resets a password. The same message is shown whether or not the email is known, so nobody can use this page to find out who has an account.

```mermaid
%%{init: {"htmlLabels": false, "flowchart": {"htmlLabels": false}}}%%
flowchart TD
  Ask["Person asks to reset a password"] --> Msg["Show the same message either way"]
  Msg --> Known{"Email on file?"}
  Known -- No --> Nothing["Send nothing"]
  Known -- Yes --> Mail["Email a link, valid 30 minutes"]
  Mail --> Open{"Link opened in time?"}
  Open -- No --> Again["Ask them to start again"]
  Open -- Yes --> Set["Set the new password"]
  Set --> Close["End the sessions already open"]
```

## Limits
- Do not draw what you wish the system did as if it were true. A planned step is labelled as planned.
- Do not put passwords, keys, tokens, real names or internal addresses in a diagram.
- Do not send a diagram with internal names to Gemini or ChatGPT.
- Do not change code while drawing. If the trace turns up a bug, report it separately.

Wersje

W bazie nie ma innych skilli o nazwie draw-flow.

Migawka bazy z 13.11.2026 · wersja paczki 6950ff3f24b8 (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

  • 100qa-site
    Testuje cały serwis webowy: odkrywa strony i przepływy, układa plan, uruchamia testy i scala raport dla zespołu.
  • 90flow
    Rysuje na żywo diagramy Mermaid, takie jak przepływy, sekwencje czy maszyny stanów, i poprawia je według uwag z podglądu.
  • 100mermaid-diagramming
    Tworzy diagramy Mermaid w niebiesko-szarym motywie projektu, na przykład przepływy, sekwencje i diagramy architektury w plikach markdown.
  • 100diagrams
    Pomaga tworzyć diagramy techniczne jako kod w Mermaid: architektura, sekwencje i przepływy, dobór typu diagramu i utrzymanie dokładności wraz ze zmianą systemu.
  • 100visual-communication
    Tworzy diagramy systemów i przepływów w Mermaid (flowchart, sequence, state, ER, class) oraz modele C4 jako diagram-as-code.
  • 100write-spec
    Pisze lub aktualizuje specyfikację systemu albo funkcji: cel, zakres, wymagania i ograniczenia.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.