DEV Community

Pavan Kumar Sadashiv
Pavan Kumar Sadashiv

Posted on

Cloud9 x JetBrains Hackathon 2026 — Step-by-Step Winning Playbook

  • Hackathon: Cloud9 x JetBrains: Sky's The Limit Hackathon 2026
  • Deadline: January 12, 2027 @ 11:00am PT (January 13, 2027 @ 12:30am IST)
  • Prize Pool: $24,000 USD cash across 6 winners ($6,000 1st / $2,000 Runner-Up in each of 3 categories) + GDC Ticket & paid trip (1st place) + JetBrains All Products Pack + $100 Cloud9 Store Gift Card
  • Payout: Direct electronic bank transfer (Global / India eligible; return winner forms within 10 business days of notification)

Step 0: 10-Minute Setup & Rule Verification

Before writing a single line of code, complete these quick checks on your logged-in cloud9.devpost.com page:

  • [ ] Open the Rules tab and verify:
    • Exact judging criteria & point weights (design your project & demo directly around them).
    • Whether one person/team can submit separate entries across multiple categories.
    • Exact list of qualifying JetBrains tools (IntelliJ, PyCharm, WebStorm, Rider, DataGrip, JetBrains Air, Junie).
  • [ ] Open the Resources tab and claim:
    • Any free JetBrains IDE / Junie / JetBrains Air hackathon license or credits.
    • GRID Esports Data API key or sample datasets (if building Category 1 or 2).
    • Official Discord link (lurk for mentor hints, judge Q&As, and common pitfalls).

Step 1: Pick the Highest-Odds Winning Category

There are 3 categories, each paying $6,000 (1st) and $2,000 (Runner-Up). Pick one primary track to dominate:

Category Best For Why It Wins
Category 3: Event Mini Game (Recommended for Fastest Win) Fast, high-polish visual wow-factor with zero data-wrangling friction Judges can play it in 30 seconds. A slick, esports-arena-ready web game with instant QR/mobile play + live spectator leaderboard stands out immediately.
Category 1: VALORANT Tactical Scouting (Best AI/Data Track) Developers strong in data visualization + AI coaching Combine GRID match data (or pro match replays) with an interactive minimap + AI counter-strat generator coaches can actually use.
Category 2: LoL Macro Scouting & Draft Management League of Legends fans / strategy analytics builders Interactive pick/ban draft simulator with live win-probability shifts and Cloud9-specific macro scouting reports.

Winning Concept Blueprints (Pick One)

  1. Option A — Category 3 (Event Mini Game): *Cloud9 Arena Rush*

    • Hook: A 60-second, zero-install browser mini-game built for live Cloud9 fan booths & watch parties.
    • Core Loop: Fast arcade reflex/tactical challenge (e.g., clutch defuse/skillshot timing or rapid esports draft-reaction rounds) with crisp sound effects, combo multipliers, Cloud9 branding palette, and instant replayability.
    • Judge Wow-Factor: One-click "Live Event Mode" (big-screen leaderboard + QR code so fans/judges can scan on their phone and compete in real time).
    • Tech Stack: Vite + React + TypeScript + HTML5 Canvas (or Phaser) + Web Audio API + Supabase/Firebase (or lightweight WebSocket/Edge backend) for live leaderboard.
  2. Option B — Category 1 (VALORANT Tactical Scouting): *Strata9 — AI Match & Round Coach*

    • Hook: Turns raw VALORANT match telemetry into an interactive 2D round replay + 1-click opponent scouting report.
    • Core Loop: Load a match -> see heatmaps (site hit rates, eco-round tendencies, first-blood zones) -> ask an AI assistant "How do we counter their defense on Ascent?" -> get evidence-backed callouts with timestamped round clips/replays.
    • Judge Wow-Factor: Pre-loaded sample matches so judges click "Launch Instant Demo" with zero API keys or login required.
    • Tech Stack: Next.js / React + TypeScript + Python FastAPI (built in WebStorm / PyCharm) + GRID data adapter + interactive SVG/Canvas minimap.

Step 2: Mandatory Submission Requirements (Zero Disqualification Risk)

Never lose a prize to a missing technical requirement. Lock these in on Day 1:

  • [ ] JetBrains Tool Usage (Mandatory): Build/update the project inside a JetBrains IDE (WebStorm, PyCharm, IntelliJ IDEA, Rider, or DataGrip) and/or use JetBrains Air / Junie. Take screenshots/short clips of your JetBrains workflow to feature in the README and demo video.
  • [ ] Public Open-Source Repo: Host on GitHub, GitLab, or Bitbucket with a visible open-source license (add an MIT LICENSE file immediately).
  • [ ] Live Working Demo URL: Deployed publicly (Vercel, Netlify, or Cloudflare Pages) with zero login wall (provide an instant demo mode).
  • [ ] Demo Video (< 3 minutes): Keep it at 2:30–2:45 sharp. Never exceed 3:00.
  • [ ] Devpost Write-up: Clear problem, solution, architecture diagram, JetBrains usage section, and how to run locally.

Step 3: What to Automate to Build & Win ASAP

Use automation to eliminate 80% of repetitive hackathon grunt work so you spend your time on visual polish and judge impact:

1. Automate Scaffolding & Feature Sprints (JetBrains Junie / AI Agents)

  • Use JetBrains Junie / AI Assistant directly inside WebStorm or PyCharm to:
    • Generate your initial Vite/React/TypeScript or FastAPI project structure.
    • Generate game physics/state machines, UI components, and responsive CSS.
    • Auto-generate TypeScript interfaces from sample JSON schemas (e.g., GRID match payloads).
  • Bonus: Using Junie / JetBrains Air directly satisfies and strengthens the JetBrains sponsor requirement.

2. Automate Data & Demo Seeding (No Live-API Failures During Judging)

  • Write a single seed script (scripts/seed-demo.ts or scripts/fetch-grid.py) that:
    • Pulls/normalizes real GRID esports data into cached JSON snapshots inside /public/demo-data/.
    • Populates realistic leaderboard scores or scouting matches automatically.
  • Why: If an external API rate-limits or changes during judging week, your live demo still works 100% smoothly offline/from cached snapshots.

3. Automate Deployments (Zero-Touch CI/CD)

  • Connect your GitHub repo to Vercel or Cloudflare Pages on Day 1.
  • Every git push to main automatically deploys your live demo link and generates preview URLs for every PR.

4. Automate Bug Catching Before Submission (Playwright Smoke Test)

  • Add a 30-line Playwright check (npm run test:e2e) in GitHub Actions that automatically:
    • Opens your live deployed URL in desktop + mobile viewports.
    • Verifies zero console errors, zero 404 assets, and completes one full user journey (e.g., start game -> play -> submit score, OR open scouting report -> run AI query).
    • Captures clean high-res screenshots automatically for your README & Devpost gallery!

5. Automate Asset & Polish Generation

  • Audio (for Mini Game): Generate crisp procedural sound effects (clicks, hits, countdowns, victory fanfare) directly with the browser Web Audio API — zero external audio licensing headaches.
  • README & Architecture Diagram: Maintain a single Mermaid diagram in README.md + auto-generated Playwright screenshots so documentation stays synced with code.

6. Automate Demo Video Production

  • Write a 150-second timed script before recording:
    • 0:00–0:20: Hook + live app in action immediately (NO long title slides).
    • 0:20–1:30: Core gameplay / scouting workflow walkthrough (show the "wow" feature live).
    • 1:30–2:10: Architecture + JetBrains workflow showcase (show your IDE / Junie / Air in action).
    • 2:10–2:40: Live Event / real-world impact for Cloud9 fans or coaches + closing call-to-action.
  • Record crisp 1080p footage with OBS/QuickTime using a clean browser window (hide bookmarks bar), add clean subtitles/captions, and upload to YouTube (Unlisted or Public).

Step 4: 7-Day "Win ASAP" Execution Sprint

You have until January 12, 2027, which means finishing a strong v1 in 7 days leaves plenty of buffer to iterate, test with users, and polish to perfection:

  • [ ] Day 1 — Lock & Deploy Skeleton: Claim JetBrains/GRID resources, create GitHub repo with MIT LICENSE, open in JetBrains IDE, scaffold app, deploy "Hello World" live URL on Vercel.
  • [ ] Day 2 — Core Engine / Data Pipeline: Build the playable game loop (Cat 3) OR GRID data loader + minimap visualization (Cat 1/2).
  • [ ] Day 3 — The "Signature Wow Feature": Add Live Event QR Leaderboard + spectator mode (Cat 3) OR AI Counter-Strat Assistant with visual callouts (Cat 1/2).
  • [ ] Day 4 — Visual & UX Polish: Dark esports aesthetic (Cloud9 cyan #00AEEF + crisp dark UI), micro-animations, sound effects, mobile responsiveness, and 1-click Instant Demo mode.
  • [ ] Day 5 — Automation & Hardening: Run Playwright E2E smoke test in Incognito mode, fix all console warnings, verify clean local setup (npm install && npm run dev).
  • [ ] Day 6 — Video & Devpost Story: Record <2:45 demo video, capture 4–5 crisp gallery screenshots, write clear README + Devpost submission draft.
  • [ ] Day 7 — Early Submit & Polish Buffer: Submit at least 48+ hours before deadline (Devpost allows editing your submission right up until the deadline!). Test every link in an Incognito browser.

Step 5: Judge-Winning Checklist (What Separates #1 from Everyone Else)

Judges review dozens of projects in ~3–5 minutes each. Make yours impossible to ignore:

  • [ ] Zero friction: Opens directly into an interactive experience (no mandatory sign-up or API-key prompt).
  • [ ] Looks like a real Cloud9 product: Clean esports typography, responsive layout, smooth animations, zero broken images.
  • [ ] Explicit JetBrains showcase: Clearly explain which JetBrains tools you used and how they sped up engineering/debugging.
  • [ ] Real-world usability: Clearly show how Cloud9 fans (at an event booth) or Cloud9 coaches (in match prep) would use this tomorrow.
  • [ ] Clean open-source repo: MIT license, concise README with screenshots, .env.example, and reproducible run instructions.

Step 6: Post-Submission & Payout Readiness

  • [ ] Monitor your Devpost email + spam folder after January 12, 2027.
  • [ ] If selected as a winner, return all Required Forms within 10 business days (strict deadline in rules).
  • [ ] Select direct electronic bank transfer for fast online payout.

Top comments (0)