What problem does it solve? Customizing a restaurant operator dashboard without understanding the existing codebase leads to broken workflows, unsafe data access, and mismatched assumptions. This Skill guides you through inspecting the actual Openfront Restaurant source, interviewing stakeholders, and safely adapting the built-in dashboard or building a separate client. ## Core Features & Use Cases - Source-Grounded Planning: Explains the architecture split between the generic Keystone dashboard shell (features/dashboard) and the restaurant-specific operator experience (features/platform) before any code changes. - Structured Discovery: Walks through a six-question interview covering target revision, deployment mode, operator jobs, roles, and test environments. - Contract Verification: Requires enumerating routes, GraphQL operations, schema access rules, and producing a capability matrix before proposing implementation. - Use Case: A restaurant platform team wants a redesigned kitchen display and waitlist screen. The Skill inspects the current screens and server actions, identifies which changes are presentation-only versus requiring new backend mutations, and delivers a safe implementation plan. ## Quick Start Ask the assistant to plan a custom operator dashboard for your Openfront Restaurant checkout, starting with a review of the current dashboard source and GraphQL schema.
