Plantuml class diagram
Skill brunojaime/plantuml-diagram-toolkit/skills/plantuml-class-diagram
Skills y herramientas para generar, validar y renderizar diagramas PlantUML
npx -y skills add brunojaime/plantuml-diagram-toolkit --skill plantuml-class-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 class diagrams in PlantUML from domain models, source code, APIs, or requirements. Use for clases, interfaces de código, attributes, methods, inheritance, realization, composition, aggregation, and navigability. Do not model runtime deployment, component interfaces, temporal messages, or database tables/cardinalities unless explicitly mapping persistence classes.
SKILL.md
1.8 KB, as published. Nobody here has run it
PlantUML Class Diagram
Model the static structure and behavior contracts of types.
Workflow
- Determine whether the source describes domain concepts or implementation classes; state the selected level.
- Extract classes, code interfaces, attributes, operations, visibility, and types only when supported.
- Distinguish inheritance, realization, composition, aggregation, and plain association.
- Add multiplicities only when explicit or logically required.
- Apply conventions.md. Apply LANG-001 and LANG-002 to every user-visible label and response field.
- Render and inspect crossings, member density, and hierarchy.
- Return one
@startuml ... @endumlblock plus assumptions.
Hard rules
- Do not represent services, nodes, APIs, or databases as classes merely because they appear in architecture notes.
- Generate all user-visible content in Spanish. Preserve exact class/code identifiers when translation would break traceability.
- Do not turn database foreign keys into class relationships automatically.
- Do not invent methods, visibility, types, inheritance, or multiplicities.
- Hide implementation members when the requested view is conceptual.
- Use unique aliases and no remote includes.
When user feedback is reusable, update references/conventions.md.