← ClaudeAtlas

protocol-doclisted

Document a network / application protocol in Tsukini's way (from the 2ETP protocol doc of his myteams project) - name + version + acronym, what it provides, the framing of a transmission (control bytes ENQ / ETB / EOT...), the payload types table (byte, hex, link), one section per message type (grammar + field bullets), the code tables (errors, events, commands, with the data sent), a summary of every frame, the handshake / key exchange step by step with the exact frames and a sequence diagram, the commands of the client and of the server (purpose, answer, usage), the storage format (separators, layout, parsed type) - always asking first the output (Markdown, PDF, HTML section inside the existing docs/ site). Use whenever the user wants to document, specify, describe or review a protocol, a wire format, a message format, a handshake, the commands of a client / server, or the files format of a networking project.
TsukiNi22/ai-utils · ★ 1 · Data & Documents · score 74
Install: claude install-skill TsukiNi22/ai-utils
# Protocol documentation `<name>` (a skill) = the folder of that skill: `~/.claude/skills/<name>` (setup.sh) or `${CLAUDE_SKILL_DIR}/../../*/<name>` (plugin of the marketplace). `SKILL_DIR` = the directory of this file. The reference is the **2ETP** doc of the user (the `README.md` of `~/delivery/year_2/nwp/G-NWP-400-BDX-4-1-myteams-1`): its order, its tables and its notation are the model, improved by the checks below. Every byte, code, field and command is **read from the code** (the parser, the enums of the control bytes, the command table, the handshake functions): never invented, planned parts marked as such. ## 1. Ask first, always (one AskUserQuestion call, French) Even when the request seems to say it, confirm (the answers decide the files): 1. **Format** (multiSelect): `Markdown (Recommandé)` (`PROTOCOL.md`, or a section of the README when the project has no other doc) · `PDF` (from the Markdown, style of `report`) · `HTML dans la doc existante` (sections of the technical page of `docs/`, `html-doc` style; no `docs/` yet: the technical page is created with `html-doc`). 2. **Contenu** (multiSelect, the ones found in the code pre-selected in the descriptions): `Trame + types de messages` · `Codes (erreurs, événements, commandes)` · `Handshake / échange de clés` · `Commandes client / serveur` · `Format de stockage`. 3. **Langue**: `Anglais (Recommandé)` · `Français` · `Les deux` (HTML: EN / FR switch of `html-doc`, always both). 4. **Emplacement** (only w