External storefronts

Give an LLM the Sports Agents storefront skill to adapt the public site or create a separate client.

To create a custom public site or client portal, copy the skill and give it to your LLM. The skill explains how features/storefront and the public routes implement the current placeholder, and where the invoice payment boundary sits.

After that source orientation, it asks what you dislike, what should stay, who the visitors are, and what the replacement should look like. It then traces the routes, GraphQL operations, proof handling, and Stripe boundary before proposing work.

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

Current state

The public site is a plain placeholder with no design. Keep the data contract and replace the presentation.

Current routes

RouteScreenWhat it does
/HomePagePublished athletes
/athletes/[id]AthletePageOne athlete and the inquiry form
/invoiceLookupPageInvoice lookup by email and number
/invoice/[id]InvoicePageInvoice and Stripe card form
/invoice/[id]/confirmationConfirmationPageConfirmation code

Named operations

All calls are in features/storefront/lib/data.ts and use only custom operations.

FunctionOperation
getRosteragencyRoster, agencyName
getAthleteagencyAthlete, agencyName
sendInquirysubmitInquiry
lookupInvoiceActionlookupInvoice, then a redirect with the proof
getInvoiceguestInvoice, agencyName
startPaymentpayCommissionInvoice
confirmPaymentconfirmCommissionPayment

Rules

  • Do not expose raw list CRUD. The invoice, payment, and ledger lists are staff-only.
  • The proof is the only guest credential. It is bound to one invoice and expires after two hours. Keep it out of logs and analytics.
  • The card form runs in the browser with Stripe.js and the publishable key. The server never receives card data.
  • Confirm payment only through confirmCommissionPayment. The server verifies the amount with Stripe before it posts a receipt.
  • A signed-in athlete linked through Athlete.portalUser can use myAthleteSummary, myDeliverables, and myInvoices. No built-in screen uses them.
  • The invoice page needs an installed Stripe provider and test keys. The live site has both.

On this page