Operations dashboard

Show live or seeded system status, incidents, and freshness.

Customize the recipe

0/1500 characters
Workflow boosters

Prompt preview

# Operations dashboard

Show live or seeded system status, incidents, and freshness.

## Deliverable
An operator dashboard with predictable loading, stale, error and recovered states.

## Stack and visual direction
- Recommended starting stack: Next.js, TypeScript and shadcn/ui. Use local fixtures for development and a database for records that must persist across users.
- Bento grid: Arrange content in purposeful modules whose sizes communicate priority. Preserve logical reading and keyboard order when modules reflow. Apply this direction to the interface while keeping data and controls easy to read.

- Inspect the workspace first. Adapt to its stack when it contains a project, or use the recommended starting stack in a new workspace.

## Tools and setup · Universal
Use the receiving agent’s documented skill and tool mechanisms. Match setup to the agent and workspace you actually have.

Check available tools first. Propose documented project-level setup only when it materially helps and follow the host's permission prompts. If a tool or integration is unavailable, continue with the workflow below using existing tools, local fixtures or a manual check. Keep secrets in the intended configuration environment.

- [shadcn/ui Skill](https://ui.shadcn.com/docs/skills) (Skill) — Inspect the project's component registry and assemble accessible UI primitives.
  Project with compatible React and styling configuration. Follow the skill's agent-specific setup. Fallback: Reuse established controls in the project, or start with semantic native controls and test keyboard and error states.
- [Recharts](https://github.com/recharts/recharts) (Repository) — Visualize comparisons or time series with a readable textual or tabular alternative.
- [Mock Service Worker](https://github.com/mswjs/msw) (Repository) — Build repeatable network fixtures for loading, error, empty and success scenarios.

## Workflow
1. Design status summaries, a timeline, and a detail view around documented metrics. Mark data freshness, make status understandable without color, and simulate unavailable feeds.
2. Use the simplest implementation that delivers the stated outcome. Follow the user's project constraints and treat the starting stack as a default. Reuse existing work and ask for essential input only when it would change the result. Use realistic labeled sample data when real inputs are unavailable.
3. Run the applicable checks and report what actually passed along with any checks you could not run.

## Acceptance checks
- [ ] A stale feed shows its last successful refresh and keeps context visible.
- [ ] Simulated incident transitions appear consistently in summary and history views.
- [ ] Walk the primary journey with keyboard only. Check visible focus, logical order, accessible names, readable contrast, zoom and reduced motion. Use axe where available and manually check behavior that automation cannot assess.
- [ ] Verify real actions and persisted data where required. Exercise relevant loading, empty, invalid, pending, failure and success states. Provide a clear recovery path.
- [ ] Use fixtures to verify core flows, including a narrow-screen layout and any applicable permission boundaries.

Recipe resources

Source, setup, and compatibility details.