hackathon

<!-- Adapted from sendaifun/solana-new (submit-to-hackathon, apply-grant), MIT © 2026 SendAI and Superteam. Telemetry removed. --> # Hackathon Submission Track choice → scannable description → <3-min demo script → checklist. Optimize for a judge who has 90 seconds, not a reader who has 10 minutes. ## Context handoff At start, read `.claude/context/idea.md` and `.claude/context/build.md` if present — pull the pitch, wedge, and what actually works from them instead of asking again. ## Workflow ### 1. Pick the least-crowded track Winning a thin track beats placing in a fat one. Per candidate track: estimate entry volume, fit with what's actually built, and judge appetite (sponsor tracks often have the fewest serious entries). - Winner patterns + track history: [hackathon-winners.md](../ext/solana-new/skills/data/colosseum/hackathon-winners.md) — every Colosseum grand champion and track winner, with what they built - Live crowdedness check: [ext/colosseum](../ext/colosseum/skills/colosseum-copilot/SKILL.md) — query 5,400+ past submissions for cluster density and gaps (requires `COLOSSEUM_COPILOT_PAT`) ### 2. Write a scannable description **Judges read 100+ submissions.** Yours gets one skim deciding whether it gets a real read: - Tagline: what it does, one sentence, no jargon - First paragraph: problem + who has it - Bold the one thing that's novel - "What works today" list — demo-able claims only, never roadmap dressed as product - Why Solana (one concrete reason: spe...