Configure visualization location, style presets, and output preferences
37
33%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./devflow-plugin/skills/visualizations-config/SKILL.mdYou are configuring the visualization system for a project. This sets up where visualizations live, what style to use, and which categories to create by default.
Check for existing configuration:
.devflow/visualizations.json in the current project~/.config/devflow/visualizations.json as global defaultIf $ARGUMENTS contains specific flags, parse them:
--path <dir> — set visualization directory--style <preset> — set style preset (devflow, minimal, custom)--categories <list> — comma-separated category folders to create--global — write to global config instead of project config--show — just display current config, don't modifyIf no arguments provided, guide the user through setup:
Ask: "Where should visualizations be stored?"
Options:
docs/visualizations/ (recommended for most projects)visualizations/ (if docs/ doesn't exist)Ask: "Which style preset?"
Options:
Ask: "Which diagram categories?"
Default categories:
architecture/ — System architecture diagramsworkflows/ — Process flow diagramsintegrations/ — Tool/service integration diagramsdecisions/ — Visual ADRsThe user can add or remove categories.
.devflow/visualizations.json):{
"path": "docs/visualizations",
"style": "devflow",
"categories": ["architecture", "workflows", "integrations", "decisions"],
"init": {
"flowchart": {
"rankSpacing": 50,
"nodeSpacing": 30,
"diagramPadding": 15
}
},
"colors": {
"primary": "#3b82f6",
"secondary": "#059669",
"accent": "#be185d",
"warning": "#d97706",
"info": "#0891b2",
"neutral": "#374151"
},
"frontmatter": true,
"symlinks": []
}~/.config/devflow/visualizations.json):Same schema but applies as default when no project config exists.
Create the configured directory structure:
mkdir -p <path>/{<categories>}Generate <path>/README.md with:
/devflow:update-visualizationsAdd .gitkeep to empty category folders so git tracks them:
touch <path>/<category>/.gitkeepSummarize what was configured:
/devflow:update-visualizations to create initial diagrams$ARGUMENTS
b0b1bb6
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.