openfront-coffee-shop-custom-storefront

Plan and build a custom Openfront Coffee Shop storefront from verified source contracts.

27|5|Updated Aug 10, 2022
One-click install
npx skills add https://github.com/openshiporg/docs --skill openfront-coffee-shop-custom-storefront-openshiporg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openfront-coffee-shop-custom-storefront
Source: https://github.com/openshiporg/docs/tree/main/public/skills/openfront-coffee-shop-custom-storefront
Command: npx skills add https://github.com/openshiporg/docs --skill openfront-coffee-shop-custom-storefront-openshiporg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Customizing a Coffee Shop storefront without understanding the actual backend contract leads to broken flows, unauthorized GraphQL calls, and features that look complete but fail in production. This Skill grounds every change in the real source code, schema, and access rules before any implementation begins. ## Core Features & Use Cases - Source-Grounded Planning: Explains where behavior lives in features/storefront, app/** routes, Keystone models, and schema.graphql before proposing changes. - Structured Discovery: Interviews the user about goals, constraints, and environments, then produces a capability matrix classifying each feature as verified, presentation-only, backend-blocked, or absent. - Two Implementation Modes: Guides adapting the built-in storefront client or building a separately deployed client with pinned schemas, strict types, and server-side credential handling. - Use Case: A team wants to redesign the Coffee Shop pickup ordering flow with new branding. The Skill inspects the actual routes, GraphQL operations, and access rules, identifies which changes are presentation-only versus requiring backend work, and delivers a verified implementation plan. ## Quick Start Use this skill to plan a custom storefront for my Openfront Coffee Shop deployment and inspect the current source before proposing changes.

Frequently Asked Questions about openfront-coffee-shop-custom-storefront

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I customize the Openfront Coffee Shop storefront?

Start by inspecting the built-in storefront in features/storefront, which contains the screens, data loaders, and GraphQL calls. Then decide whether to adapt that client in place or build a separately deployed client against the verified schema.

Should I adapt the built-in storefront or build a separate client?

Adapt the built-in client when you can reuse its sessions, transport, and design tokens while keeping route files thin. Build a separate client when you need independent deployment, but pin the schema, use named operations, and keep credentials server-side.

Can I reuse Ecommerce GraphQL operations in the Coffee Shop storefront?

No, not without validation. The Coffee Shop vertical has its own workflow nouns and authority boundaries, so you must verify that each operation exists in schema.graphql and is authorized for the actor and tenant scope before using it.

What should I check before changing checkout or ordering flows?

Trace every data loader and server action the built-in screens call, then record actor, scope, inputs, idempotency, and error states for each operation. Consequential actions require a bounded server command validating ownership, state transitions, and provider behavior.

Why is a working GraphQL query not proof a storefront flow is safe?

A schema-valid document or HTTP 200 response does not prove access rules, lifecycle authority, or provider behavior are correct. The Skill requires inspecting model access, field access, and custom resolvers before treating any flow as operational.