openfront-rental-custom-storefront

Plan and build custom Openfront Rental storefronts by inspecting source code and GraphQL contracts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Customizing a rental storefront without understanding the existing architecture leads to broken booking flows, duplicated business logic, and unsafe GraphQL access. This Skill guides the planning and implementation of a custom Openfront Rental storefront by grounding every decision in the actual source code and server contract. ## Core Features & Use Cases - Source-Grounded Planning: Explains where storefront behavior lives (features/storefront, app/**, features/keystone/**, schema.graphql) before any implementation begins. - Structured Discovery: Interviews the user about goals, constraints, and target journeys, then inspects routes, data loaders, GraphQL operations, access rules, and provider integrations. - Capability Matrix: Classifies each requested feature as verified, presentation-only, needing backend contract work, blocked, or absent. - Use Case: A team wants to rebrand and restructure the guest booking experience for their Openfront Rental deployment. The Skill inspects the actual checkout and reservation flows, identifies which changes are presentation-only versus requiring new server mutations, and produces a safe implementation plan. ## Quick Start Use this skill to plan a custom storefront for my Openfront Rental deployment and tell me which changes are presentation-only versus backend contract work.

Frequently Asked Questions about openfront-rental-custom-storefront

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

FAQPage Schema
How do I customize the Openfront Rental storefront?

Start by inspecting the actual source: routes live in `app/**`, behavior in `features/storefront`, and the server contract in `features/keystone/**` and `schema.graphql`. Then decide whether to adapt the built-in client or build a separately deployed one, and classify each change as presentation-only or backend contract work.

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

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 never expose an arbitrary GraphQL proxy.

Can I reuse Ecommerce GraphQL queries in a Rental storefront?

No, not without validation. The Rental vertical has its own workflow nouns and authority boundaries, so Ecommerce roots must be verified to exist and be authorized in `schema.graphql` and the access rules before use.

What is a capability matrix in storefront planning?

A capability matrix classifies each requested feature as verified, presentation-only, needing a backend contract, blocked, or absent. It prevents claiming a flow works based only on a schema-valid document or an HTTP 200 response.

Why is a generated GraphQL schema not proof of safe access?

A schema-valid document can still violate model and field access rules, actor scope, or lifecycle authority. Safe access requires tracing actual server operations, access control, idempotency, and error states in the source code.