implementation
Implement in your agent
# Implement Skeleton in your agent ## Objective Implement Skeleton for this verified behavior: Decorative placeholder shapes that reserve the approximate layout of content while that content is loading. ## Prerequisites - Inspect the repository, design system, and existing tests first. - Preserve unrelated changes and keep the file scope bounded. - Confirm that Skeleton matches the need before writing code. ## Required behavior - Placeholder shapes reserve stable space and are replaced by real content without a layout jump. - The content region exposes its busy state while a separate visual indicator remains redundant. ## States to cover - Placeholders visible — Placeholders visible - Content visible — Content visible - Failed card error visible — Failed card error visible ## Accessibility - The primary control or named region for Skeleton has a stable accessible name from visible text or an explicit programmatic label; placeholder text and tooltips are not names. - Focus remains on the existing page; replacing placeholders does not reorder or steal focus. - Skeletons disappear only when replaced by content, an empty state, or an actionable error state. - Placeholders never enter the tab order - Retry controls appear only in real error states ## Non-goals - The wait concerns one compact button action - The final layout is unknown or highly variable ## Acceptance criteria - Placeholder geometry approximates final content - Skeleton shapes are hidden from assistive technology - The parent region exposes busy state - Empty and error states replace an indefinite wait
sha256:acc42f9d1877d8a8eb6e72f40c090cce7e9bcf900457827ce4dc74fb5e7a8bf2