Mona’s Octoverse Arcade

GitHub Day of Learning · 2-hour workshop game challenge

Mona’sOctoverse Arcade

Canvas Extension Edition

Build a browser game starring Mona the Octocat as the hero and Copilot as the sidekick, then ship it as a Copilot App canvas extension. Every team starts from one prompt. What you build from it is up to you.

  • 2hours
  • 4–6people per team
  • 25rubric points
  • 3award categories
Get the starter promptForm your team
Mona perched on green blocks beneath a white sprout, surrounded by pastel clouds and a blue sky.

01 · Start here

One prompt. Your game.

Every team starts with this prompt in the Copilot App. It sets the baseline, not the limit. Build what it asks, then take the game somewhere only your team would.

starter-prompt.txt

Build a Copilot App canvas extension called Mona’s Octoverse Arcade. Start from the provided canvas starter template. Inside the canvas, create a game where Mona the Octocat collects green commit-squares while dodging red bugs. Track the score, increase speed over time, and show a game-over screen with a restart button. Copilot appears as a sidekick that gives an encouraging tip every 10 points. The extension must install cleanly and open as a playable canvas. Keep it to HTML/CSS/vanilla JS inside the canvas — no external build step.

The baseline

  • Mona collects green commit squares and dodges red bugs.
  • The score is tracked, and the speed increases over time.
  • A game-over screen has a restart button.
  • Copilot cheers you on with a tip every 10 points.

Make it yours

  • Rethink the world

    Levels, settings, and a story that make Mona’s arcade feel like yours.

  • Invent power-ups

    Shields, magnets, merge combos, or boss bugs. Surprise the judges.

  • Give Copilot personality

    Make the sidekick funny, helpful, or full of surprises.

  • Find your style

    Art direction, animation, and sound that make people want to keep playing.

02 · Teams

Build as a team

Up to 150 people may take part, so everyone builds in a team. Form your team and choose a team name during kickoff.

  • People per team

    Minimum 4, maximum 6. Aim for 5.

  • Choose a team name

    Pick it during kickoff. You’ll use it on your submission.

  • Shared repository

    Keep your team’s extension in one repository that judges can open.

Planning numbers: with 150 participants, teams of 5 make about 30 teams (25–38, depending on team size). If your group has fewer than 4 people, join another group. If it has more than 6, split into two teams.

03 · Core requirement

Ship it as a canvas extension

Your game can’t be a loose HTML file. It must be a Copilot App canvas extension that:

  1. Lives in its own folder

    With an extension.mjs that registers a canvas (the game UI).

  2. Can be installed

    Into the Copilot App — via install_extension from a GitHub gist or repo folder, or dropped into the extensions directory.

  3. Runs as a canvas

    When the agent opens it with open_canvas, the game renders in the side panel and is playable.

Start from the provided canvas starter template. Build the game UI with HTML, CSS, and vanilla JavaScript inside the canvas — no external build step. You’ll learn the real extension model: manifest, canvas registration, install, and launch. That’s the “GitHub twist” that makes the challenge platform-native.

04 · Timed agenda

Two hours, five phases

  1. 0:00–0:1515 min

    Kickoff & teams

    See the target canvas extension, get the starter prompt and rubric, form teams of 4–6, and choose a team name.

  2. 0:15–0:2510 min

    Install the starter

    Every team installs and opens the starter canvas template — confirm it runs.

  3. 0:25–1:1550 min

    Build your game

    Start from the prompt, then build your team’s version inside the canvas with the Copilot App.

  4. 1:15–1:3520 min

    Power-up

    Pick a “power-up” stretch goal: leaderboard, sound, animation, theming, or your own idea.

  5. 1:35–2:0025 min

    Record & submit

    Record a demo video of up to 90 seconds and post your submission in the challenge Discussion before the workshop ends. 🏆

05 · Submit

Submit in the challenge Discussion

Before the workshop ends at 2:00, one teammate posts your team’s submission as a single comment in the challenge Discussion. Your facilitator will share the link. Include:

  1. Team name

    The name your team chose at kickoff.

  2. Description

    A few sentences about your game, your creative spin, and your power-up.

  3. Demo video

    Up to 90 seconds. Install the extension, open it as a canvas, and play. Attach the video to your comment or add a link.

  4. Repository link

    The repository that contains your extension folder. Make sure the judges can access it.

06 · Judging

Scoring rubric (25 points total)

How judging works: after the workshop, judges review every submission’s demo video and repository against the 25-point rubric. They choose all three award winners and announce them in the challenge Discussion. There is no audience vote.

CriteriaPointsWhat judges look for
It works — installs & runs as a canvas8Extension installs, canvas opens, game is actually playable.
Fun factor6Is it enjoyable? Would you play again?
GitHub theme5Creative use of Mona & Copilot as characters.
Polish3Visuals, animations, sound, game-over/restart flow.
Wow / stretch3A power-up feature that surprised the judges.
Total25

07 · Awards

Three ways to win

The judges decide all three categories. Each category winner takes home swag 🎁.

  • Overall Winner

    Best total rubric score across all criteria.

  • Best Design

    The best-looking, most visually striking game (Polish).

  • Most Fun

    The game the judges most wanted to keep playing (Fun factor).

Award rollover rule: a team can win more than one category, but if the Overall Winner also tops another category, that second award rolls to the runner-up to spread the recognition.

08 · Design principles

How this challenge is designed

  • Rubric up front

    Ship the rubric up front so teams build toward what’s judged.

  • Known-good starter

    Provide a known-good canvas starter so “install & run” is achievable for everyone.

  • Reward working software

    The rubric weights “it runs” highest — 8 of 25 points for installing and running as a canvas.

  • Shared theme, personal spin

    Every team starts from the same prompt and builds Mona’s Arcade, then makes it its own.

09 · Beyond the workshop

Ideas for your next canvas extension

Inspiration for after the workshop — not submissions for this competition. Every team builds Mona’s Arcade for this challenge, with the shared gameplay requirements and 25-point rubric.

  • “Ask Mona” Chatbot

    Concept
    A rule-based/scripted Q&A assistant UI.
    GitHub twist
    Mona answers Git/GitHub beginner questions; Copilot suggests follow-ups.

  • Commit Streak Tracker

    Concept
    A habit/streak tracker.
    GitHub twist
    Themed as a “contribution graph” — earn Mona badges for streaks.

  • Octo-Quiz

    Concept
    Timed trivia game.
    GitHub twist
    Git/GitHub trivia; Copilot gives hints, Mona celebrates wins.

  • PR Review Simulator

    Concept
    Card-swipe game (approve/request changes).
    GitHub twist
    Learn code-review etiquette; Mona is the author, Copilot the reviewer.

  • Mona’s Sticker Maker

    Concept
    Canvas drawing + Octocat generator.
    GitHub twist
    Compose your own Octocat; export as PNG.

Built with imagination

One Mona. Endless possibilities.

Bring your own creative spin to the arcade. Keep Mona at the heart of the game, and make something worth playing again.

GitHub Universe ’26 artwork with Mona and colorful silhouettes. The original event lockup reads October 2026, San Francisco, CA.
Universe ’26 · Supplied event artwork, not workshop event details.
Mona looking toward a glowing white butterfly, surrounded by pastel clouds against a blue sky.
A little curiosity. A whole new world to build.