maintaining-dev-playgroundlisted

# Maintaining the Dev Playground The Dev Playground (`apps/client/src/dev/`, accessible at `/dev` in development) is a living gallery of every visual component in DorkOS. It exists so that designers and developers can review components in isolation, catch regressions visually, and verify that the design system is coherent. The playground is only useful if it stays in sync with the actual application. Stale or missing showcases erode trust and let regressions slip through. This skill exists to prevent that drift. ## When This Skill Applies Assess playground impact whenever you edit files in: - `apps/client/src/layers/widgets/**/ui/**` — widget UI components - `apps/client/src/layers/features/**/ui/**` — feature UI components - `apps/client/src/layers/entities/**/ui/**` — entity UI components - `apps/client/src/layers/shared/ui/**` — shared UI primitives - `apps/client/src/dev/**` — direct playground edits After editing a UI component, ask yourself three questions: 1. **Is this component a good playground candidate?** (See candidacy criteria below) 2. **Is it already in the playground?** Check the section registries in `dev/sections/`. 3. **If it's already there, is the showcase still accurate?** Does it reflect the current props, states, and visual appearance? ## Candidacy Criteria A component belongs in the playground if it meets **any** of these: - **Visual and reusable** — renders UI that appears in more than one place, or could - **Has multiple meaningful states*