What problem does it solve? Customizing a hotel storefront without understanding the existing codebase leads to broken booking flows, unauthorized data access, and duplicated business logic. This Skill guides a disciplined process of source inspection, user interviews, and contract verification before any code changes. ## Core Features & Use Cases - Source Orientation: Maps the Openfront Hotel repository structure, including features/storefront, app/** routes, Keystone models, and schema.graphql, so changes start from the real architecture. - Structured Discovery: Interviews the user about target revision, built-in versus separate client mode, required journeys, and deployment constraints before proposing implementation. - Contract Verification: Traces every data loader, GraphQL operation, access rule, and provider integration to produce a capability matrix distinguishing presentation-only changes from backend-contract work. - Use Case: A team wants a rebranded booking experience deployed separately from the built-in storefront. The Skill walks them through pinning the schema, generating strict types, keeping privileged credentials server-side, and testing anonymous, wrong-tenant, and provider-failure scenarios. ## Quick Start Use the openfront-hotel-custom-storefront skill to plan a custom booking storefront against my Openfront Hotel source checkout.
