openfront-gym-custom-dashboard

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Customizing a gym 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 Gym source code, interviewing stakeholders, and safely adapting the built-in dashboard or building a separate client. ## Core Features & Use Cases - Source Architecture Orientation: Explains where dashboard behavior lives across features/dashboard, features/platform, and features/keystone before any code changes. - Structured Requirements Interview: Asks targeted questions about target revision, deployment mode, operator jobs, roles, and design constraints. - Contract Verification: Traces GraphQL operations, schema access rules, and server actions to produce a capability matrix distinguishing presentation-only changes from backend work. - Use Case: A gym operator wants a custom front-desk check-in screen. The Skill inspects the current dashboard routes, verifies the GraphQL mutations exist and are authorized, then either adapts the built-in client or scaffolds a safe separate client with pinned schema types. ## Quick Start Use this skill to plan a custom operator dashboard for my Openfront Gym deployment by inspecting the source and interviewing me about requirements.

Frequently Asked Questions about openfront-gym-custom-dashboard

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

FAQPage Schema
How do I customize the Openfront Gym dashboard?

Start by inspecting the source code in `features/dashboard` for the generic Keystone shell and `features/platform` for gym-specific screens. Then decide whether to adapt the built-in client or create a separate deployment, and verify all GraphQL operations against the actual schema before coding.

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

The `features/dashboard` directory contains the reusable Keystone administration layer with generic list screens and authentication. The `features/platform` directory holds gym-specific operator navigation, workflows, and server actions mounted into that shell.

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

Adapt the built-in client when you want to reuse existing session handling, design tokens, and server operations. Build a separate client when you need independent deployment, but you must pin the schema, validate operations server-side, and never expose arbitrary GraphQL proxies.

How do I verify GraphQL operations are safe to use?

Trace every data loader and server action to its GraphQL document, then check `schema.graphql` and access control rules. Confirm actor scope, tenant boundaries, and idempotency before assuming an operation is authorized for your use case.

What gym workflows does this dashboard support?

The dashboard handles memberships, classes, instructors, rosters, scheduling, front-desk check-in, billing, locations, and reports. Always verify the current implementation state rather than assuming every flow is complete or safe.