Dashboard Surface Retirement

Removes deprecated dashboard UI while preserving backend maintenance endpoints and storage.

Updated Mar 13, 2026

Search Tags:#testing #routing #maintenance #dashboard #retirement #ui-surface #admin-config

Ready to run

npx skills add https://github.com/JDL440/nfl-eval --skill dashboard-surface-retirement

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Dashboard Surface Retirement
Source: https://github.com/JDL440/nfl-eval/tree/main/.squad/skills/dashboard-surface-retirement
Command: npx skills add https://github.com/JDL440/nfl-eval --skill dashboard-surface-retirement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dashboard Surface Retirement enables teams to safely retire unused UI surfaces while preserving essential backend endpoints, reducing maintenance overhead without breaking workflows.

Core Features & Use Cases

Remove retired UI routes, views, and dead CSS while preserving stable API contracts for maintenance tasks.
Centralize maintenance actions on the canonical admin surface (e.g., /config) and keep existing endpoints intact.
Update tests to assert operator-visible outcomes and ensure redirects/deprecations are reflected in the UI.

Quick Start

Remove the surface code and associated view modules for the retired dashboard area, shift maintenance triggers to the canonical admin surface, and update tests to reflect operator-visible outcomes.

Frequently Asked Questions about Dashboard Surface Retirement

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

FAQPage Schema

How do I retire deprecated dashboard UI routes without breaking backend maintenance endpoints?▼

Retiring dashboard routes involves removing view modules and dead CSS while preserving stable backend API contracts. Maintenance triggers are migrated to the canonical admin surface so existing endpoints remain intact and functional.

What is the best way to remove dead CSS and deprecated views from a retired UI surface?▼

The best way to remove dead CSS and deprecated views is to delete the retired surface code and associated view modules. Maintenance actions are shifted to the canonical admin surface, ensuring no orphaned styles remain.

How do I update tests to reflect operator-visible outcomes after retiring a dashboard surface?▼

Updating tests for retired dashboard surfaces involves asserting operator-visible outcomes rather than internal route behavior. Tests verify maintenance actions are accessible on the canonical admin surface and reflect deprecation redirects.

Can I move maintenance actions to a canonical admin surface while keeping existing endpoints intact?▼

Yes, you can move maintenance actions to the canonical admin surface while keeping existing endpoints intact. The retirement process preserves stable API contracts and storage, ensuring backend functionality remains unaffected.

When should I not remove deprecated UI components and routes from my codebase?▼

You should not remove deprecated UI components if backend maintenance endpoints depend on those routes, or if migration to the canonical admin surface is incomplete. Stable API contracts must be preserved to avoid breaking workflows.

Does retiring a dashboard surface require migrating to a canonical admin surface like /config?▼

Yes, retiring a dashboard surface requires migrating maintenance triggers to a canonical admin surface such as /config. This ensures operators retain access to maintenance actions without needing the deprecated UI views.