What problem does it solve? Customizing the Openfront Salon operator dashboard is risky without knowing the real server contract: guessing GraphQL operations, borrowing Ecommerce conventions, or duplicating authorization logic in components leads to broken or unsafe 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-Grounded Planning: Explains the actual architecture (features/dashboard, features/platform, app/dashboard, Keystone models and schema.graphql) before proposing changes. - Structured Interview & Capability Matrix: Interviews the user about goals, roles, and constraints, then classifies each requested feature as verified, presentation-only, needs backend contract, blocked, or absent. - Built-in vs Separate Client Guidance: Provides distinct implementation rules for adapting the built-in dashboard or deploying an independent client with pinned schemas, named operations, and fail-closed validation. - Use Case: A salon platform team wants a redesigned appointments and waitlist screen. The Skill inspects the real routes, server actions, and GraphQL operations, identifies which changes are presentation-only versus requiring new backend mutations, and produces a safe implementation plan. ## Quick Start Ask the assistant to plan a custom Openfront Salon operator dashboard and provide the path to your Salon source checkout and target revision.
