openfront-coffee-shop-custom-dashboard

Plan and build a custom Openfront Coffee Shop operator dashboard from verified source code.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Customizing the Openfront Coffee Shop operator dashboard is risky without knowing the real architecture: assumptions about routes, GraphQL operations, and access rules lead to broken or unsafe changes. This Skill guides a source-grounded process that inspects the actual product code and contract before proposing or implementing dashboard changes. ## Core Features & Use Cases - Source Orientation: Explains where behavior lives, including features/dashboard (generic Keystone admin shell), features/platform (Coffee Shop operator experience), app/dashboard routes, and the Keystone schema and mutations. - Structured Interview and Inspection: Asks targeted scoping questions, then enumerates routes, screens, data loaders, GraphQL operations, access rules, and provider integrations to build a capability matrix. - Built-in vs Separate Client Guidance: Provides rules for safely adapting the built-in dashboard or building an independently deployed client with pinned schemas, checked operations, and server-side credentials. - Use Case: An operator wants a redesigned KDS and orders screen. The Skill inspects the current screens and server actions, classifies each change as presentation-only or backend-contract work, and delivers a handoff report with blockers and tests. ## Quick Start Ask the assistant to plan a custom Coffee Shop operator dashboard by inspecting the current Openfront source and interviewing you about scope and deployment.

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

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

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

Start by inspecting the actual source: `features/dashboard` holds the generic Keystone admin shell and `features/platform` holds the Coffee Shop operator screens. Then decide whether to adapt the built-in client or build a separate one, and verify every GraphQL operation against the schema before changing code.

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

Adapt the built-in client when you can reuse existing session handling, 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.

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

No, not without validation. The Skill explicitly forbids borrowing Ecommerce roots or renaming products and orders into this vertical; every operation must be verified against the Coffee Shop schema, access rules, and authorization boundaries first.

What is a capability matrix in dashboard planning?

A capability matrix classifies each requested feature as verified, presentation-only, needing a backend contract, blocked, or absent. It is produced after tracing routes, screens, data loaders, GraphQL documents, and access rules in the inspected source.

Why is a schema-valid GraphQL document not enough for dashboard changes?

Schema validity does not prove safe access. The Skill requires checking actor, tenant or store scope, lifecycle authority, idempotency, and error states for each operation, since generated CRUD may still violate access rules or workflow authority.