Plantuml sequence diagram
Skill brunojaime/plantuml-diagram-toolkit/skills/plantuml-sequence-diagram
Skills y herramientas para generar, validar y renderizar diagramas PlantUML
npx -y skills add brunojaime/plantuml-diagram-toolkit --skill plantuml-sequence-diagramAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 10 days oldThe repository was created 10 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Generate and refine UML sequence diagrams in PlantUML from use cases, API flows, webhooks, queues, retries, callbacks, or architecture notes. Use when the user asks for secuencia, flujo temporal, order of calls, request/response, asynchronous events, alternatives, loops, errors, timeouts, or participant lifelines. Do not show deployment containment, static component topology, class structure, or database entity relationships.
SKILL.md
1.9 KB, as published. Nobody here has run it
PlantUML Sequence Diagram
Model who communicates, in what order, with which message, and under which conditions.
Workflow
- Define the scenario start, success outcome, and relevant failure boundary.
- Select participants by runtime role, not every internal class.
- Order messages from top to bottom and name messages by intent.
- Use solid arrows for calls/messages and dashed arrows for returns.
- Use
alt,opt,loop,par, andbreakonly when supported. - Distinguish synchronous calls, asynchronous events, callbacks, retries, and timeouts.
- Apply conventions.md. Apply LANG-001 and LANG-002 to every user-visible label and response field.
- Render and inspect chronology and activation readability.
- Return one
@startuml ... @endumlblock plus assumptions.
Hard rules
- A sequence arrow represents a message, not a component dependency or provided/required interface.
- Generate all user-visible content in Spanish. Preserve official products, protocols, event names, and exact API/code identifiers.
- Do not show nodes, regions, containers, class members, or DER cardinalities.
- Do not invent retries, timeouts, response payloads, or error paths.
- Keep one primary scenario per diagram; use a separate diagram for unrelated workflows.
- Use unique aliases and no remote includes.
When user feedback is reusable, update references/conventions.md.