What problem does it solve? Customizing the Openfront Barbershop operator dashboard is risky without knowing the real architecture: teams often guess at GraphQL contracts, borrow Ecommerce conventions, or ship UI changes that break booking, POS, or queue workflows. This Skill guides a disciplined process of source orientation, user interviews, and contract inspection before any code is written. ## Core Features & Use Cases - Source Architecture Orientation: Explains where behavior lives in the repository, including features/dashboard (generic Keystone admin shell), features/platform (Barbershop-specific screens and workflows), app/dashboard routes, and the Keystone schema and access rules. - Structured Requirements Interview: Asks a concise set of questions about the target checkout, built-in versus separate client mode, operator jobs, roles, visual direction, and available test environments. - Contract Verification and Capability Matrix: Traces routes, data loaders, GraphQL operations, access rules, and provider integrations, then classifies each requested feature as verified, presentation-only, needs backend contract, blocked, or absent. - Use Case: An agency is asked to redesign the barbershop's walk-in queue and POS screens. The Skill walks them through inspecting the actual schema and server actions, distinguishing safe UI-only changes from work requiring new backend mutations, and producing a handoff report with blockers and test evidence. ## Quick Start Ask the assistant to plan a custom operator dashboard for your Openfront Barbershop checkout and answer its interview questions about your source revision and desired changes.
