openfront-uikit-custom-dashboard

Plan and build a custom Openfront UIKit operator dashboard from inspected source code.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Customizing an operator dashboard without understanding the existing source architecture leads to broken contracts, duplicated business logic, and unsafe assumptions about backend capabilities. This Skill guides a disciplined process of source orientation, user interviews, and contract inspection before any dashboard code is written. ## Core Features & Use Cases - Source Architecture Orientation: Explains where behavior lives across features/dashboard, features/platform, app/dashboard, and the Keystone schema before implementation begins. - Structured Requirements Interview: Asks targeted questions about checkout path, deployment mode, operator jobs, roles, and test environments. - Contract Verification: Traces routes, data loaders, GraphQL operations, access rules, and provider adapters to produce a capability matrix distinguishing verified, presentation-only, and blocked work. - Use Case: A team wants to redesign the UIKit operator dashboard for catalog and order management. The Skill inspects the actual checkout, maps every screen to its server operations, and recommends whether to adapt the built-in client or build a separate one. ## Quick Start Ask the assistant to plan a custom Openfront UIKit operator dashboard by first inspecting the current source checkout and interviewing you about requirements.

Frequently Asked Questions about openfront-uikit-custom-dashboard

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

FAQPage Schema
How do I customize the Openfront UIKit operator dashboard?

Start by inspecting the current source checkout: `features/dashboard` holds the reusable Keystone admin shell and `features/platform` holds the product-specific screens. Then decide whether to adapt the built-in client or build a separate one, and verify every server operation against `schema.graphql` before implementing.

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 safely. Build a separate client when you need independent deployment, but pin the schema, use checked named operations, and never expose an arbitrary GraphQL proxy.

What source files define the dashboard behavior in this product?

The generic dashboard shell lives in `features/dashboard`, product-specific operator screens in `features/platform`, thin route entries in `app/dashboard`, and the server contract in `features/keystone/models`, `features/keystone/access.ts`, and `schema.graphql`.

Can I reuse Ecommerce GraphQL operations in a UIKit dashboard?

No, not without validation. The Skill explicitly forbids borrowing Ecommerce roots or renaming entities across verticals; every operation must be verified against this product's schema, access rules, and authorization boundaries first.

Why is a capability matrix required before dashboard implementation?

A capability matrix records which operations are verified, presentation-only, need backend contract work, blocked, or absent. A schema-valid document or HTTP 200 response is not proof that an operator workflow is safe or authorized.