Diagram Design
A diagramming skill that produces self-contained HTML and SVG diagrams in a defined editorial style, with stated rules for connectors, labels and accessibility, and import support for draw.io and Mermaid files. Aimed at people who need explanatory diagrams that hold a consistent look.
- Visual assets
- Design review
Source: cathrynlavery/diagram-design · pinned commit dcd9317
View source on GitHubLuluSkill lists this project so you can find it. A listing is not a security review or an endorsement, and nothing on this page is installed or run for you.
EDITORIAL GUIDE
Decide whether a diagram adds information
Use a diagram to expose relationships, not to decorate a list. Separate the semantic structure from the visual style and export format.
LuluSkill’s own reading of this project, not a summary of its README. About 3 minutes to read
This guide is LuluSkill’s own judgement about when this project fits, written from the pinned version named above. It is not the author’s documentation, not a security review and not a recommendation. LuluSkill did not install, run or test the project to write it, and the guide is shown only while this listing still points at the commit it was written against.
When this project fits
This entry suits a process, dependency or architecture explanation whose relationships are difficult to follow in prose. Its opening workflow distinguishes the meaning of the diagram from its visual form and asks for a style profile before generating a browser-based artifact.
When to choose something else
A short ordered list does not automatically need a diagram. Avoid committing to a visual style before deciding what an arrow means. Also avoid a static image when the reader needs searchable text or precise values that would be easier to scan in a table.
What to provide and what to expect
Supply the entities, relationships, reading order, audience and brand constraints. Expect an HTML and inline-vector composition, with image export as a separate step. The useful output is an explanation of the relationship, not merely an attractive canvas.
Tools, permissions and boundaries
Saving the artifact needs scoped file access; rendering or exporting needs compatible browser tooling. A remote brand reference needs network permission. None of these follows automatically from the entry text, and export fidelity must be checked in the target format.
The tradeoff and an alternative
Write one sentence for each relationship first. If those sentences already solve the problem, keep them. A diagram introduces layout and export maintenance; it earns that cost only when spatial grouping or branching makes the explanation easier to understand.
A small acceptance exercise
Proposed exercise: show three steps and one rejection branch. Check that each arrow has one meaning, the rejected path cannot be mistaken for success, labels survive a narrow viewport, and the exported image preserves the same order and content as the browser version.
Source, version and what was actually read
The opening entry sections covering activation, style-profile selection, semantic patterns and output formats were read. The separate export implementation and linked reference material were not inspected. LuluSkill did not install or run this project; the exercise above is a proposed reader check, not a reported result.
How to use this listing
LuluSkill publishes the description and the source link only. The skill itself stays in its author’s repository, and nothing here is installed, copied or run for you.
- Read what the skill helps with The summary above says which job the project is for. If that is not the job you have, this is probably not the listing you want.
- Open the original source and follow the author’s own instructions The link to the original project opens its author’s page. That page, not this one, is where the setup steps and any copying instructions live.
- Use it in a compatible AI assistant Skills of this kind are normally used inside an AI assistant that can read a folder of files on your computer. Which assistants support them is the author’s decision, so check their page before you start.
Who it is for
Somebody who already wants this one job done and is willing to follow the author’s setup steps. No programming knowledge is assumed, and this listing cannot tell you whether the project suits you.
Before you start
You need an AI assistant that supports skills, and you will be following somebody else’s instructions on your own computer. Read them before you run anything.
What you end up with
Whatever the author’s project produces. LuluSkill never runs it, so this page cannot promise a result, a file, or a level of quality.
Where it is normally used
Projects like this are usually used in an AI assistant that supports skills, such as an AI coding assistant. The author’s repository says which assistants it is written for; LuluSkill has not tested it with any of them.
Version checked
The source was checked at this commit: dcd9317
Changes made to the repository after this commit have not been checked.
License
MIT, from the licence file in the source repository at the listed commit. Check the repository’s licence before you use or copy the project.
Listing only
LuluSkill lists this project only. It does not host, download or run its code.
What this page does not include
The project’s files and setup steps stay in its own repository. LuluSkill has not security-tested the project or confirmed which AI assistants it works with.
Report a problem or request removal
Rights holders and users can report licence, attribution, security or accuracy problems with this page. We respond within 48 hours and record every request in our review log.
Opens your email app. You can also write to contact@luluskill.com and include this page’s address.