canvas-communication

name	canvas-communication
description	Use when an idea, workflow, topology, or boundary is easier to explain visually than in prose. Create simple diagrams, maps, or structured visual explanations that improve alignment and handoff quality.

Canvas Communication

Use visual structure when plain text is too abstract.

Treat this as a baseline communication capability, not a niche diagram tool.

Every agent should be able to switch from prose to visual explanation when that improves alignment, speed, or decision quality.

When To Use

• topology explanation
• architecture boundary explanation
• workflow and SOP mapping
• handoff diagrams
• company and role structure
• skill-package activation maps
• before / after comparisons
• scope and ownership diagrams

Core Rule

Do not draw for decoration.

Draw only when the visual makes the logic easier to understand.

Output Standard

Prefer compact visuals:

• box-and-arrow diagrams
• layered maps
• step flows
• role-to-SOP mappings
• skill-to-workflow maps
• interactive canvases when needed

The visual should clarify the system, not add noise.

Default Expectation

If a human would understand the system faster by seeing it than by reading it, use this skill.

Do not wait for a separate request for a diagram when the structure is the message.