What problem does it solve? Customizing the Openfront Dealership operator dashboard is risky without knowing the actual source architecture, GraphQL contract, and access rules. This Skill guides a structured process—source orientation, user interview, and rigorous code inspection—so dashboard changes are grounded in the real product rather than assumptions borrowed from other verticals like Ecommerce. ## Core Features & Use Cases - Source-Grounded Planning: Explains the features/dashboard shell versus features/platform product layer, then interviews the user about goals, roles, and constraints before any code is written. - Contract Verification: Traces routes, screens, server actions, GraphQL operations, and schema.graphql access rules to produce a capability matrix marking each feature as verified, presentation-only, backend-blocked, or absent. - Two Delivery Modes: Supports adapting the built-in dashboard client or building a separately deployed client with pinned schemas, strict types, and server-side credential handling. - Use Case: A dealership operator wants a redesigned deals and finance intake screen. The Skill inspects the actual Keystone models and mutations, confirms which lifecycle transitions are authorized, and only then proposes UI changes or requests a backend contract. ## Quick Start Ask the assistant to plan a custom Openfront Dealership operator dashboard and point it at your source checkout so it can inspect the routes, screens, and GraphQL contract before proposing changes.
