openfront-restaurant-custom-storefront

Start by inspecting the current source: enumerate app routes, trace screens in features/storefront, and read schema.graphql plus access rules. Then decide whether to adapt the built-in client or build a separate one, and classify each change as presentation-only or backend contract work.

Adapt the built-in client when you can reuse existing sessions, transport, design tokens, and named server operations. Build a separate client when you need independent deployment, but pin the schema, use checked named operations, and keep privileged credentials server-side behind a BFF.

No, not without validation. The Skill explicitly warns against borrowing Ecommerce roots or renaming products and orders into the restaurant vertical. Every operation must be verified against this product's schema.graphql and access rules first.

Never expose an arbitrary GraphQL proxy or accept browser-selected fields, operations, provider IDs, or endpoint URLs. Pin the exact schema, generate strict types, runtime-validate responses, and test anonymous, wrong-user, wrong-tenant, and provider-failure cases against disposable data.

The Skill requires one bounded server projection or command validating actor, scope, ownership, state transitions, idempotency, and audit evidence for consequential actions. If that contract does not exist, the feature is shown as unavailable and a backend contract is requested.