Individual skill
visual-docs-diagrams
Design and review visual content for developer documentation, including screenshots, architecture diagrams, boxes-and-arrows diagrams, flowcharts, swimlanes, video decisions, accessibility, performance, annotations, and visual maintenance. Use when creating or auditing diagrams, screenshots, visual explanations, or media in technical docs.
plugins/LVTD-LLC/skills/skills/visual-docs-diagrams/SKILL.md
Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,532
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-coding Repository topic
- awesome Repository topic
- awesome-list Repository topic
- codex Repository topic
- codex-plugins Repository topic
- openai Repository topic
- codex-skill Repository topic
- codex-skills Repository topic
- marketplace Repository topic
- codex-marketplace Repository topic
- engineering Derived category
- design Derived category
- docs Derived category
- writing Derived category
Declared tags are partial or unavailable.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,729 bytesSKILL.mdcore · 2,729 bytesSKILL.mdcore · 2,729 bytesguidelines.mddoc · 1,215 bytesreferences/core/knowledge.mddoc · 4,419 bytesworkflows/design-technical-visual.mddoc · 2,263 bytes
Read excerpt
# Visual Docs Diagrams
Use this skill to decide whether developer docs need visuals and to design or review those visuals for comprehension, accessibility, performance, and maintainability.
This skill is derived from *Docs for Developers: An Engineer's Field Guide to Technical Writing*, especially Chapter 6, "Adding visual content." The guidance is transformed and paraphrased; do not copy book prose into user outputs. Source: https://link.springer.com/book/10.1007/978-1-4842-7217-6
## Quick Start
1. Load `guidelines.md` to choose the smallest useful reference set.
2. Define what the visual must help the reader understand or do.
3. Choose screenshot, diagram, flowchart, swimlane, or text-only based on the task.
4. Use `workflows/design-technical-visual.md` for full visual design or review.
5. Check accessibility, performance, placement, source files, and maintenance before finalizing.
