dashboard-visualizer

Guide adding and debugging visualizer tabs in the RACA UI.

5|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/Zayne-sprague/Dr-Claude-Code --skill dashboard-visualizer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dashboard-visualizer
Source: https://github.com/Zayne-sprague/Dr-Claude-Code/tree/main/.claude/skills/dashboard-visualizer
Command: npx skills add https://github.com/Zayne-sprague/Dr-Claude-Code --skill dashboard-visualizer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Maintains knowledge about the RACA dashboard visualizer and enables quick answers about capabilities, setup, and common issues.

Core Features & Use Cases

  • Answers what visualizations are supported and how to check artifact compatibility.
  • Guides how to add or modify visualizer tabs and how to edit frontend/backend code when a new visualization type is needed.
  • Supports debugging data displays within the dashboard.

Quick Start

Add a new visualizer tab by editing the frontend and backend and registering it with VisualizerApp.

Frequently Asked Questions about dashboard-visualizer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new dashboard visualization tab to an existing project?

To debug data displays in a dashboard visualization, you can use guided troubleshooting steps to trace data flow from the backend to the frontend, verifying artifact compatibility and component rendering.

What is the best way to verify artifact compatibility for dashboard visualizations?

Verifying artifact compatibility for dashboard visualizations involves checking the supported visualization types within the RACA UI and ensuring your data artifacts match the expected model-trace formats before rendering.

Why is my dashboard visualizer not displaying data correctly?

A dashboard visualizer may fail to display data correctly due to mismatched frontend or backend component registrations, requiring you to debug the data displays and verify that the VisualizerApp integration is properly configured.

Do I need to edit both frontend and backend code to create a new visualization type?

Yes, creating a new visualization type requires editing both the frontend and backend code to handle the new data structure and ensure the visualizer component is properly registered and rendered in the dashboard.

Can I modify existing visualizer tabs without breaking the dashboard layout?

Modifying existing visualizer tabs is supported by adjusting the frontend and backend code while maintaining the VisualizerApp registration, ensuring the dashboard layout remains stable during data display updates.