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.
SkillScore100Maintained
Automatic
◆Doc Ops pack
Last verified 8/16/2026
What it changes
Passed 22 of 22 test cases with the skill, and 20 of 22 without it.
Without skill91%
With skill100%
Checks it passed that the model alone missed
Includes accessibility and performance checks.
Specifies defining an owner or update trigger for visual updates.
Includes a maintenance plan with source file and ownership details.
and 1 more in the full report
2 fixed20 passed either way0 still failing0 broke
Pass-rate lift
+9 pp
Tokens
+7%
Agent turns
0%
Response time
-21%
Model gemini-3.6-flashMeasured 8/16/2026v122 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 2
Prompt
Our documentation team embeds PNG diagrams created in Draw.io into our docs repository. How should we manage these visual assets to ensure long-term maintainability?
Specifies defining an owner or update trigger for visual updates.
Missed
Passed
case-06 · gemini-3.6-flash · 8/16/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md40 linessingle file
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
Load guidelines.md to choose the smallest useful reference set.
Define what the visual must help the reader understand or do.
Choose screenshot, diagram, flowchart, swimlane, or text-only based on the task.
Use workflows/design-technical-visual.md for full visual design or review.
Check accessibility, performance, placement, source files, and maintenance before finalizing.
Default Output
When designing or reviewing visual docs, return:
Visual purpose - what the reader must understand faster or better.
Recommended visual type - screenshot, boxes-and-arrows, flowchart, swimlane, video, or no visual.
Design notes - scope, labels, annotations, contrast, placement, and format.
Accessibility and performance checks - alt text, captions, transcripts, SVG/image size, responsiveness.
Maintenance plan - source file, owner, update trigger, and review cadence.
Contents
Need
Start Here
Understand visual types
references/core/knowledge.md
Apply visual rules
references/core/knowledge.md
See visual decision examples
references/core/knowledge.md
Design or review a visual
workflows/design-technical-visual.md
Route by task
guidelines.md
Core Posture
Use visuals to supplement text, not replace critical instructions.
Prefer one idea or level of detail per visual.
Treat accessibility and maintenance as part of visual design, not post-production polish.
Avoid video unless the motion itself is necessary and maintenance is realistic.