What problem does it solve?
Dashboard changes in PostHog span many surfaces—authenticated scenes, public shares, embeds, exports, and templates—and a change that works in one place can silently break permissions, caching, or layouts in another. This Skill gives engineers a structured routing, design, and testing process so dashboard platform changes stay consistent and safe across every surface.
Core Features & Use Cases
- Change routing and surface analysis: Classifies requests between dashboard platform work and widget work, then forces an explicit affected/unaffected decision for each rendering surface before coding.
- Design gates and contracts: Provides checklists for RBAC, filters and variables, caching and scale, responsive layouts, templates, and backend operations, backed by seven in-depth reference documents.
- Boundary-focused testing and code map: Lists edge cases (empty dashboards, shared tokens, concurrent edits, streaming failures) plus a file-level map of the dashboards backend, frontend scene, and MCP tools.
- Use Case: When adding a new dashboard filter type, an engineer uses the Skill to define filter precedence, verify shared-token behavior, update serializers and OpenAPI output, and run the focused test commands for each edited layer.
Quick Start
Ask the agent to plan and implement a change to PostHog dashboard filters, layout, sharing, or templates using the managing-dashboards skill.