What problem does it solve? Building a customer-facing storefront for Openfront Convenience is risky because the source has no canonical storefront layer, and guessing at routes or GraphQL operations leads to broken or unauthorized flows. This Skill guides a disciplined process: orient in the actual source, interview stakeholders, inspect real routes and schema contracts, then adapt the built-in client or build a safe separate one. ## Core Features & Use Cases - Source Orientation & Inspection: Enumerates actual app routes, traces screen components and their data loaders, and reads schema.graphql, access rules, and resolvers before proposing any code. - Structured User Interview: Asks a concise question set covering target revision, built-in versus separate client, required journeys, brand, accessibility, and available test environments. - Capability Matrix & Safe Client Boundaries: Classifies each operation as verified, presentation-only, needs backend contract, blocked, or absent, and enforces rules like pinned schemas, named operations, and no arbitrary GraphQL proxying. - Use Case: A team wants a new convenience retail customer portal. The Skill inspects the repository, discovers which public routes and GraphQL operations actually exist, flags missing backend contracts for checkout, and produces a handoff report with implemented files, tests, and blockers. ## Quick Start Ask the assistant to plan a custom storefront for your Openfront Convenience checkout by inspecting the current source and interviewing you about the required customer journeys.
