Anatomy
Turn a process into a readable mechanical diagram: identify inputs, transformations, and outputs before choosing geometry.
Explain a system through clear diagram semantics, labels, and an intentional reading path.
---
name: knoveya-diagram-design
description: "Explain a system through clear diagram semantics, labels, and an intentional reading path. Use for matching visual design work."
---
# Diagram Design
## Scope
Apply this guidance when the requested task matches the description. Honor the user's chosen outcome, repository rules, and existing authorization.
## Workflow
Explain a system through clear diagram semantics, labels, and an intentional reading path.
Before acting, inspect the relevant artifact and ask only for information that materially changes the result. Use existing tools and conventions; do not install dependencies, publish, send messages, deploy, or mutate external data unless the user has authorized that operation.
## Acceptance check
Arrows and groupings represent real relationships and remain legible at export size.
## Example task
Draw an approval boundary distinctly from a data-flow arrow.
## Report
State what changed, the evidence checked, and what remains unverified. Do not claim a successful operation or completed test without observing it.Copy the full block, including its frontmatter, into a new folder named knoveya-diagram-design as SKILL.md. Review the instructions before enabling them. For Codex, a user skill normally lives in ~/.codex/skills/knoveya-diagram-design/SKILL.md; check the current documentation for another agent's supported location. Do not overwrite an existing skill.
This is an independent Knoveya skill. No files are installed by this website.
Draw an approval boundary distinctly from a data-flow arrow.
Arrows and groupings represent real relationships and remain legible at export size.
Test the skill on a small, authorized example. File validation alone does not prove that an agent will make good decisions.
The skill supplies instructions, not tool access or expertise guarantees. Inspect generated work and preserve the user's approval boundaries.