openfront-construction-custom-dashboard

Plans and builds custom operator dashboards for the Openfront Construction Keystone platform.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Customizing the Openfront Construction operator dashboard requires understanding a layered Keystone codebase, and guessing at the GraphQL contract or borrowing patterns from other verticals produces broken or unsafe screens. This Skill guides a disciplined process: orient in the actual source, interview stakeholders, inspect the real schema and access rules, then adapt the built-in dashboard or build a separate client safely. ## Core Features & Use Cases - Source Orientation: Explains where behavior lives across features/dashboard, features/platform, app/dashboard, and the Keystone models, access rules, and schema.graphql. - Structured Discovery: Runs a stakeholder interview and a required source inspection covering routes, data loaders, GraphQL operations, access control, idempotency, and provider integrations, producing a capability matrix. - Two Delivery Modes: Adapts the built-in dashboard client or architects a separately deployed client with pinned schemas, named operations, BFF credential handling, and fail-closed validation. - Use Case: A team wants a custom project-portfolio and progress-billing dashboard for their Construction deployment. The Skill inspects their checkout, maps verified versus blocked operations, and implements only contract-backed screens. ## Quick Start Ask the assistant to plan a custom Openfront Construction operator dashboard and point it at your source checkout and target revision.

Frequently Asked Questions about openfront-construction-custom-dashboard

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

FAQPage Schema
How do I customize the Openfront Construction dashboard?

Start by inspecting the actual source: features/dashboard holds the generic Keystone shell, while features/platform holds Construction-specific screens and server actions. Then decide whether to adapt the built-in client or create a separately deployed client, and verify every 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. Build a separate client when you need independent deployment, but pin the schema, use checked named operations, and keep privileged credentials behind a BFF.

Can I reuse Ecommerce GraphQL operations in the Construction dashboard?

No, not without validation. The Construction vertical uses its own workflow nouns like estimates, budgets, contracts, and progress billing, and Ecommerce roots may not exist or be authorized. Always verify operations against the product's schema.graphql and access rules.

What must be verified before adding a consequential dashboard action?

Each consequential action needs one bounded server projection or command validating actor, tenant scope, related-record ownership, state transition, concurrency, idempotency, provider behavior, and audit evidence. If that contract does not exist, request the backend work and show the feature as unavailable.

Why is a schema-valid GraphQL document not enough to ship a dashboard screen?

A schema-valid document only proves the query parses, not that access rules permit it or the workflow is safe. The Skill requires tracing model access, field access, and custom resolvers, then recording actor, scope, lifecycle authority, and error states per operation.