What problem does it solve? Teams customizing the Openfront Marketplace operator experience often assume it is a Keystone-based vertical with dashboard, storefront, and GraphQL layers, leading to invented contracts and unsafe implementations. This Skill grounds the work in the actual Marketplace source, interviews the user, and separates presentation-only changes from backend-contract work. ## Core Features & Use Cases - Source Orientation: Explains that Marketplace lives in app/page.tsx and features/marketplace/**, with no Keystone dashboard, storefront, or schema.graphql layer. - Structured Interview & Inspection: Asks targeted scoping questions, then enumerates routes, traces completion transport, MCP tools, adapters, egress policy, carts, and sessions, producing a capability matrix. - Built-in vs Separate Client Guidance: Provides rules for adapting the built-in client or building a separate client with pinned endpoints, checked named operations, and fail-closed validation. - Use Case: An operator team wants a custom dashboard for managing curated store configurations and adapter diagnostics; the Skill inspects the real source, identifies which screens are presentation-only versus blocked on backend contracts, and delivers a verified implementation plan. ## Quick Start Use this skill to plan a custom operator dashboard for my Openfront Marketplace checkout at the provided source path.
