What problem does it solve? Customizing a pharmacy operator dashboard without understanding the existing Keystone-based architecture leads to broken workflows, duplicated business logic, and unsafe access patterns. This Skill guides the planning and implementation of a custom Openfront Pharmacy dashboard by first inspecting the actual product source, schema, and server contract before writing any code. ## Core Features & Use Cases - Source-Grounded Planning: Explains the existing architecture (features/dashboard, features/platform, app/dashboard, features/keystone) and interviews the user to define scope before implementation. - Contract Inspection: Traces routes, screens, GraphQL operations, schema access rules, and provider integrations to produce a capability matrix distinguishing presentation-only changes from backend-contract work. - Two Implementation Modes: Adapts the built-in dashboard client or builds a separately deployed client with pinned schemas, strict types, and fail-closed behavior. - Use Case: A pharmacy operator wants a redesigned dispensing and refill review screen. The Skill inspects the current source, identifies which operations are safe to reuse, flags missing backend contracts, and implements the UI without duplicating lifecycle or authorization logic. ## Quick Start Ask the assistant to plan a custom pharmacy operator dashboard and provide the path to your current Openfront Pharmacy source checkout.
