What problem does it solve? Customizing a pharmacy storefront without understanding the existing source architecture leads to broken checkout flows, unauthorized data access, and duplicated business logic. This Skill guides a structured process of source orientation, user interviews, and contract inspection before any code is written. ## Core Features & Use Cases - Source-Grounded Planning: Traces actual app routes, screen components, data loaders, and GraphQL operations in features/storefront and features/keystone instead of guessing from conventions. - Built-in vs. Separate Client Guidance: Helps decide whether to adapt the existing storefront or build an independently deployed client with pinned schemas, strict types, and server-side credential handling. - Capability Matrix & Safe Handoff: Produces a verified/presentation-only/blocked capability matrix covering actor scope, idempotency, provider behavior, and audit evidence for pharmacy workflows like OTC checkout and prescription intake. - Use Case: A team wants to rebrand and restructure their pharmacy's online ordering experience. The Skill interviews stakeholders, inspects the real schema and access rules, then implements only presentation-safe changes while flagging anything requiring backend contract work. ## Quick Start Ask the assistant to plan a custom pharmacy storefront by first inspecting the current Openfront source checkout and GraphQL schema.
