deneb-reviewer — Claude Code subagent: Deneb spec validation
deneb-reviewer validates Vega and Vega-Lite specs for Power BI before presenting them to the user. Catches syntax errors, Deneb convention violations, and offers design feedback.
GPL-3.0 ★ 1,104 updated 2026-10-28
.github/agents/deneb-reviewer.agent.mdWhat deneb-reviewer does
The subagent runs automatically when the main agent creates or modifies a Deneb visualization. It checks ten items: schema correctness, data binding structure (array for Vega, object for Vega-Lite), field names (spaces preserved, special characters replaced with underscores), expressions with double quotes, responsive sizing via pbiContainerWidth and pbiContainerHeight signals, config settings (autosize: fit, Segoe UI font), pbiColor() usage instead of hardcoded hex, encoding block correctness, and tooltip setup. URL-based data sources are blocked by AppSource certification.
After validation, it provides design recommendations: chart type fit for the data relationship, intentional color usage, readable axes and legends, sufficient text size (12pt minimum), sensible sort order. The output lists failed checklist items, up to three design suggestions, and an overall verdict of READY or NEEDS CHANGES. Requires Read, Grep, and Glob tools to access spec files.
What it helps with
- validate Vega and Vega-Lite syntax before publishing
- catch data binding and field name errors in Deneb specs
- ensure visualizations are responsive and theme-compliant
- get design feedback on charts before showing them to clients
Example prompts for the agent
- Run
deneb-reviewerto validate the new chart spec - Check the changes in
bullet-chart.jsonwith the Deneb review subagent - Validate all Vega specs in the project
How to install deneb-reviewer
Manually: put the files in place
.github/agents/deneb-reviewer.agent.md1Plugin marketplace
/plugin marketplace add data-goblin/power-bi-agentic-development/plugin install reports@power-bi-agentic-development2Manually: put the files in place
.claude/agents/deneb-reviewer.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention. Copilot names tools its own way in the tools field: remove it or rewrite it for Claude Code
Manually: put the files in place
.codex/agents/deneb-reviewer.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/deneb-reviewer.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about deneb-reviewer
How to install deneb-reviewer in Claude Code?
Run /plugin marketplace add data-goblin/power-bi-agentic-development, then /plugin install reports@power-bi-agentic-development. The subagent will be in .claude/agents/deneb-reviewer.md.
What does deneb-reviewer do?
It validates Deneb specs against ten criteria — from schema and data binding to responsiveness and Power BI theme colors. It gives design suggestions and a READY or NEEDS CHANGES verdict.
What tools does deneb-reviewer need?
Read, Grep, and Glob to access and search spec files in the project.