visual-skills

Why this skill exists

When a user provides data, the naive response is to guess a chart type and write ad-hoc code. This produces inconsistent, low-quality visuals. Every chart looks different. Libraries change. Code breaks.

This skill solves that by:

1. Semantically understanding the data first (not just column names or file extensions)
2. Routing to a pre-defined visual template for that data type
3. Mapping the user's data into the stable template
4. Rendering a consistent, production-quality artifact

The LLM's job is understanding + mapping. The template's job is rendering.

Protocol: How to use this skill