manus-skills/.kortix/opencode/skills/design/markdown-mermaid-writing/references/diagrams/packet.md
zhukang 1c7abd81d1 All 310 Manus skill-hub community skills as a Kortix marketplace registry
- 310 registry:skill items, 1528 files, 7 categories (hub tags)
- registry.json generated by @kortix/registry buildRegistry
- nested SKILL.md in sn-da-* renamed SUBSKILL.md (no phantom skills)
- provenance + licenses: SOURCES.md
2026-09-15 13:37:20 +08:00

1.7 KiB

Packet Diagram

Back to Style Guide — Read the style guide first for emoji, color, and accessibility rules.

Syntax keyword: packet-beta Best for: Network protocol headers, data structure layouts, binary format documentation, bit-level specifications When NOT to use: General data models (use ER), system architecture (use C4 or Architecture)

⚠️ Accessibility: Packet diagrams do not support accTitle/accDescr. Always place a descriptive italic Markdown paragraph directly above the code block.


Exemplar Diagram

Packet diagram showing the structure of a simplified TCP header with field sizes in bits:

packet-beta
    0-15: "Source Port"
    16-31: "Destination Port"
    32-63: "Sequence Number"
    64-95: "Acknowledgment Number"
    96-99: "Data Offset"
    100-105: "Reserved"
    106-111: "Flags (URG,ACK,PSH,RST,SYN,FIN)"
    112-127: "Window Size"
    128-143: "Checksum"
    144-159: "Urgent Pointer"

Tips

  • Ranges are start-end: in bits (0-indexed)
  • Keep field labels concise — abbreviate if needed
  • Use for any fixed-width binary format, not just network packets
  • Row width defaults to 32 bits — fields wrap naturally
  • Always pair with a Markdown text description above for screen readers

Template

Description of the protocol or data format and its field structure:

packet-beta
    0-7: "Field A"
    8-15: "Field B"
    16-31: "Field C"
    32-63: "Field D"