matchday-demo-workflow

Sterne0

Forks0

Aktualisiert16. Mai 2026 um 12:26

Use when changing the demo narrative, GitHub workflow, PR review story, or Codex automation story.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

chrisreddington

chrisreddington/matchday-commerce-autopilot

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	matchday-demo-workflow
description	Use when changing the demo narrative, GitHub workflow, PR review story, or Codex automation story.

Matchday Demo Workflow

Keep the demo optimized for a 4-hour hackathon recording.
Show GitHub issues, a Codex branch, TDD verification, a PR, @codex review, local github:gh-address-comments, and automation as part of the delivery story.
Keep the demo storefront-first: show / as the shopper experience, favorite a real World Cup team, check in to a real fixture, then use /admin as the backend that powers the offer.
Use real static FIFA team and fixture data for schedule claims. Never invent team lists, fixture dates, kickoff times, or venues.
Show the Codex Matchday Assistant as deterministic local automation: it reads local fixture and simulated score state, then suggests campaigns.
Prefer clear storefront/admin separation and fan-relevant marketplace polish over checkout or inventory depth.
Do not add checkout, inventory, live sports feeds, or production auth ceremony.

Mehr aus diesem Repository

gleiches Repository

codex-app-server

chrisreddington/matchday-commerce-autopilot

Use when designing or implementing product integrations that embed Codex App Server, custom Codex clients, rich Codex threads, streamed agent events, approvals, auth, skills, or app connector flows.

2026-05-160

matchday-ui-ux

chrisreddington/matchday-commerce-autopilot

Use when editing Matchday Commerce Autopilot UI, UX, styling, storefront/admin screens, product cards, campaign forms, favorite-team flows, demo polish, or fan marketplace presentation.

2026-05-160

next16-local-guidance

chrisreddington/matchday-commerce-autopilot

Use before changing Next.js App Router, route handlers, server rendering, auth, or testing patterns in this repository.

2026-05-160

matchday-promotion-rules

chrisreddington/matchday-commerce-autopilot

Use when changing campaign or promotion eligibility behavior for Matchday Commerce Autopilot.

2026-05-160

name	matchday-demo-workflow
description	Use when changing the demo narrative, GitHub workflow, PR review story, or Codex automation story.

Matchday Demo Workflow

Keep the demo optimized for a 4-hour hackathon recording.
Show GitHub issues, a Codex branch, TDD verification, a PR, @codex review, local github:gh-address-comments, and automation as part of the delivery story.
Keep the demo storefront-first: show / as the shopper experience, favorite a real World Cup team, check in to a real fixture, then use /admin as the backend that powers the offer.
Use real static FIFA team and fixture data for schedule claims. Never invent team lists, fixture dates, kickoff times, or venues.
Show the Codex Matchday Assistant as deterministic local automation: it reads local fixture and simulated score state, then suggests campaigns.
Prefer clear storefront/admin separation and fan-relevant marketplace polish over checkout or inventory depth.
Do not add checkout, inventory, live sports feeds, or production auth ceremony.