What problem does it solve? Design reviews and frontend builds stall when screens contain placeholder text instead of realistic data, and hardcoded fake values scattered through the UI become painful to replace when real APIs arrive. ## Core Features & Use Cases - Mock Data Layer Generation: Creates a single data/mock/ directory with realistic, domain-accurate JSON files per entity, including edge cases like bye weeks, zero scores, and missing fields. - Data Mapping Document: Produces docs/data-mapping.md, a proto-API contract mapping every mock field to its eventual real source, field name, and connection status. - Backlog Integration: Updates slice records in docs/backlog.md so slices blocked on pending data anchors get unblocked with concrete file paths and field names. - Use Case: A solo builder finishes design screens for a fantasy football app but has no API yet. Run this Skill to generate realistic player and performance data, wire it into the screens behind a swappable data layer, and produce the first draft of the API contract. ## Quick Start Generate realistic mock data for all screens in docs/design and create the data mapping document before design review.
