| name | dynacat-dashboard-architect |
| description | Route and orchestrate Glance or Dynacat dashboard work through discovery, planning, approval, implementation, and final review. Use when a user asks to create a dashboard from scratch, redesign or migrate an existing dashboard, choose between Glance and Dynacat, generate a dashboard architecture plan, or implement an approved Glance/Dynacat dashboard. |
Dynacat Dashboard Architect
Purpose
Act as the primary installable skill for npx skills. Choose the right workflow for the user's request and enforce the human-in-the-loop approval gate.
Router
Use these bundled skills when available:
$dynacat-dashboard-discovery for from-scratch dashboards, existing dashboard review, platform selection, and requirements gathering.
$dynacat-dashboard-planning for approval-ready architecture documents, diagrams, matrices, folder structure, and implementation gates.
$dynacat-dashboard-implementation only after the user approves the architecture, or for narrow patches to existing implementations.
If the subskills are not installed, follow the same phases directly from this skill.
Workflow
Progress:
- Discovery
- Planning document
- User review and approval
- Implementation
- Final optimization review
Defaults
Default to discovery for new dashboards, migrations, platform-selection questions, and vague implementation requests.
Default to planning when the user asks for architecture, page hierarchy, service matrix, diagrams, or implementation approach.
Default to implementation only when the user explicitly approves a plan or asks for a small, isolated change.
Source References
Use official and project references as source-of-truth. If the shared package reference is available, load references/source-of-truth.md; otherwise use these URLs directly:
Gotchas
- Do not generate broad implementation code before planning approval.
- Do not invent Glance YAML, Dynacat config, custom API, include, or theme patterns.
- Do not duplicate dashboards, widgets, APIs, or references when a reusable structure exists.
- Do not assume Docker, Kubernetes, Grafana, Prometheus, auth proxies, or media services are acceptable dependencies without user confirmation or repo evidence.