Perses Dashboard-as-Code Pipeline

Set up and manage Dashboard-as-Code workflows with CUE or Go SDK.

Operator Context

This skill operates as a pipeline for Dashboard-as-Code workflows, from module initialization through CI/CD integration.

Hardcoded Behaviors (Always Apply)

• One dashboard per file: Follow Perses convention of one dashboard definition per file — keeps diffs clean and enables per-dashboard CI validation
• Build before apply: Always run percli dac build before percli apply — raw CUE/Go files cannot be applied directly
• Validate built output: Always run percli lint on built JSON/YAML before deploying — build success does not guarantee valid dashboard spec
• Go SDK stdout warning: Never log/print to stdout in Go DaC programs — dac build captures stdout as the dashboard definition, so any stray output corrupts it

Default Behaviors (ON unless disabled)

• CUE SDK: Default to CUE SDK unless user requests Go
• JSON output: Build to JSON format by default
• Git-friendly: Organize files for version control (one dashboard per file, clear naming)