openfront-hospital-custom-dashboard

Plan and build a custom Openfront Hospital operator dashboard from source inspection.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Customizing a hospital operator dashboard without understanding the existing codebase leads to broken workflows, unsafe data access, and mismatched assumptions. This Skill guides you through inspecting the actual Openfront Hospital source, interviewing stakeholders, and safely adapting the built-in dashboard or building a separate client. ## Core Features & Use Cases - Source Orientation: Explains the repository architecture, including the reusable Keystone dashboard shell in features/dashboard and the hospital-specific operator experience in features/platform. - Structured Interview Process: Asks targeted questions about deployment targets, required operator jobs, roles, and visual direction before writing code. - Contract Verification: Traces GraphQL operations, schema access rules, and server actions to produce a capability matrix distinguishing presentation-only changes from backend contract work. - Use Case: A hospital IT team wants a custom intake and appointments dashboard. The Skill inspects the current routes, verifies which GraphQL operations are authorized, and either adapts the built-in client or scaffolds a separate client with pinned schema and strict types. ## Quick Start Ask the assistant to plan a custom operator dashboard for your Openfront Hospital deployment and point it at your source checkout.

Frequently Asked Questions about openfront-hospital-custom-dashboard

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

FAQPage Schema
How do I customize the Openfront Hospital dashboard?

Start by inspecting the source: features/dashboard contains the reusable Keystone admin shell, while features/platform holds the hospital-specific screens and workflows. Then decide whether to adapt the built-in client or build a separate one, verifying each GraphQL operation against schema.graphql before coding.

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

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

What is the difference between features/dashboard and features/platform in Openfront?

features/dashboard is the generic Keystone administration layer with list/item screens and authentication helpers. features/platform contains the hospital-specific operator navigation, screens, server actions, and workflows mounted into that shell.

Can I reuse Ecommerce GraphQL operations in the Hospital dashboard?

No. The Skill explicitly forbids borrowing Ecommerce roots or renaming products and orders into the hospital vertical. Every operation must be validated against the Hospital schema.graphql, access rules, and custom resolvers before use.

Why does a schema-valid GraphQL query still fail in the dashboard?

A schema-valid document is not proof of safe access. Field-level and model-level access rules, actor scope, tenant boundaries, and lifecycle authority can all block execution, so each operation must be traced and tested against real authorization logic.