External dashboards

Give an LLM the Sports Agents dashboard skill to adapt the built-in dashboard or create a separate client.

To create a custom Sports Agents dashboard, copy the skill and give it to your LLM. The skill explains how features/dashboard supplies the Keystone administration shell while features/platform contains the agency-specific operator screens.

After that source orientation, it asks what you dislike, what should stay, which workflows and users matter, and what the replacement should look like. It then traces the exact routes, GraphQL calls, access rules, and payment boundaries in your copy of the source before proposing work.

The skill is public/skills/openfront-sports-agents-custom-dashboard/SKILL.md in the docs repository.

Current platform routes

Route files live in app/dashboard/(admin)/platform/**. Each one imports a screen from features/platform and exports it. There are no per-route permission wrappers. Access comes from list access and the athlete scope, so a page shows what the user's role can read.

RouteSliceWhat it does
/dashboarddashboardMoney view
/dashboard/platform/clientsclientsRoster with status and league filters
/dashboard/platform/clients/[id]clientsAthlete record with nine tabs
/dashboard/platform/recruitingrecruitingProspect board by stage
/dashboard/platform/contractscontractsContracts by status
/dashboard/platform/contracts/[id]contractsTerms, years, incentives, signing, schedule
/dashboard/platform/endorsementsendorsementsDeal pipeline and deliverables
/dashboard/platform/brandsbrandsBrands and contacts
/dashboard/platform/commissionscommissionsPayments, invoices, ledger, payouts
/dashboard/platform/trusttrustTrust accounts and entries (read-only)
/dashboard/platform/approvalsapprovalsRequest, approve, reject, use
/dashboard/platform/payment-providerspayment-providersProvider list
/dashboard/platform/taskstasksOpen tasks and reminder generation
/dashboard/platform/certificationscertificationsAgent certifications by expiry
/dashboard/platform/settingssettingsAgency record (read-only)

Sidebar entries come from features/platform/lib/navigation.ts. The shared shell routes are /dashboard/init, /dashboard/signin, /dashboard/signup (only when PUBLIC_SIGNUPS_ALLOWED=true), /dashboard/reset, /dashboard/no-access, and the generic list screens /dashboard/[listKey], /dashboard/[listKey]/create, and /dashboard/[listKey]/[id]. The generic screens are the starter's list pages and work for any list the user can access.

How screens get data

Screens are server components. They call GraphQL through platformQuery in features/platform/lib/query.ts. Actions go through runAgencyCommand in features/platform/actions/agency.ts, which holds a fixed set of mutation documents. Approval actions are in actions/approvals.ts. A button creates one idempotency key per click and reuses it on retry.

Named operations by slice

SliceReadsCommands
dashboardMoneyView (invoices, scheduled payments, deliverables, certifications, agreements)None
clientsClients, ClientDetailsignRepresentationAgreement, markPaymentReceived
recruitingAthletes by statusmoveRecruitingStage
contractsplayingContracts, playingContractrecordContractSigned, generatePaymentSchedule
endorsementsendorsementDeals, deliverablesactivateEndorsementDeal, completeDeliverable
commissionsPayments, invoices, ledger, payoutsmarkPaymentReceived, draftCommissionInvoice, sendCommissionInvoice, recordInvoicePayment, reverseLedgerEntry
approvalsmanagerApprovalsrequestManagerApproval, decideManagerApproval, activateEndorsementDeal, writeOffCommissionInvoice
taskstasksgenerateAutoTasks
trust, brands, certifications, payment-providers, settingsLists onlyNone
onboardingensureOnboardingRecordupdateActiveUser

Notes for a separate dashboard

  • Use the custom commands for every money or status change. Generated writes for those lists are blocked.
  • Re-check permission and athlete scope on the server. The navigation does not enforce them.
  • Send an idempotency key with every command.
  • Do not copy the placeholder proof link that the built-in Mark completed button sends.
  • There is one agency per deployment. There is no tenant id to pass.

On this page