Guide Hackathon Navigator

An autonomous agent that helps teams navigate hackathons end-to-end — from ideation and team formation through rapid prototyping, pitch preparation, and submission, optimizing for judging criteria and time constraints.

When to Use This Agent

Choose Guide Hackathon Navigator when:

• You are participating in a hackathon and need structured guidance on ideation and execution
• Your team needs help scoping a project that is achievable within the time limit
• You want to optimize your submission for specific judging criteria
• You need rapid prototyping assistance with demo-ready deliverables

Consider alternatives when:

• You are building a production application (use standard development workflows)
• You need deep technical architecture planning (use a system architect agent)
• Your project is already well-defined and you just need coding help

Quick Start

Copy
# .claude/agents/hackathon-navigator.yml
name: guide-hackathon-navigator
description: Navigate hackathons from ideation to pitch
agent_prompt: |
  You are a Hackathon Navigator helping teams win hackathons.

  When engaged:
  1. Understand the hackathon theme, rules, timeline, and judging criteria
  2. Brainstorm ideas that align with criteria and are achievable in time
  3. Create a project plan with hour-by-hour milestones
  4. Guide rapid prototyping with focus on demo-able features
  5. Prepare pitch deck and demo script
  6. Review submission materials before deadline

  Always optimize for: judge-ability > completeness > polish.
  A working demo of one feature beats a broken prototype of five.

Example invocation:

Copy
claude "We have 24 hours for a climate-tech hackathon. Team of 3 (2 devs, 1 designer). Judged on innovation, impact, and technical execution."

Sample agent output:

Hackathon Battle Plan — Climate Tech (24h)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Recommended Idea: Carbon Footprint Tracker for Daily Commutes
  Innovation: GPS + transit API mashup with gamification
  Impact: Addresses personal carbon reduction with behavior change
  Feasibility: API-driven, demo-able in 24h

Timeline:
  Hours 0-2:   Finalize idea, set up repo, design wireframes
  Hours 2-6:   Core backend (transit API, carbon calc engine)
  Hours 6-10:  Frontend MVP (map view, daily dashboard)
  Hours 10-14: Integration + gamification (streaks, badges)
  Hours 14-18: Polish UI, fix bugs, prepare sample data
  Hours 18-20: Build pitch deck (5 slides max)
  Hours 20-22: Practice demo, record backup video
  Hours 22-24: Final submission + buffer time

Tech Stack (speed-optimized):
  Frontend: Next.js + Tailwind (fast UI)
  Backend: Next.js API routes (no separate server)
  Database: Supabase (instant setup + auth)
  APIs: Google Maps, Transit, carbon intensity
  Deploy: Vercel (one-click deploy for demo)

Core Concepts

Hackathon Success Framework

Factor	Weight	Strategy
Working Demo	35%	Focus on one killer feature that works perfectly
Innovation	25%	Combine existing tech in a novel way
Impact	20%	Show measurable user benefit with data
Technical Execution	15%	Clean code, proper error handling, deployed
Presentation	5%	Clear story, engaging demo, confident delivery

Time Management Protocol

24-Hour Hackathon Breakdown:
┌──────────────┬─────────────────────────────────────┐
│ Phase        │ Allocation                          │
├──────────────┼─────────────────────────────────────┤
│ Ideation     │ 10% (2.4h) — idea + validation      │
│ Setup        │ 5%  (1.2h) — repo, tooling, deploy   │
│ Core Build   │ 40% (9.6h) — main features           │
│ Integration  │ 15% (3.6h) — connect + test           │
│ Polish       │ 15% (3.6h) — UI, UX, sample data     │
│ Pitch Prep   │ 10% (2.4h) — deck, demo script       │
│ Buffer       │ 5%  (1.2h) — surprises + submission   │
└──────────────┴─────────────────────────────────────┘

Rapid Tech Stack Selection

Copy
// Speed-optimized stack selector
const stackRecommendations = {
  "web-app": {
    frontend: "Next.js + Tailwind CSS",
    backend: "Next.js API Routes or Express",
    database: "Supabase (instant Postgres + Auth)",
    deploy: "Vercel (auto-deploy from GitHub)",
    reason: "Zero config, instant deploy, built-in auth"
  },
  "mobile-app": {
    framework: "React Native + Expo",
    backend: "Firebase (auth + Firestore + functions)",
    deploy: "Expo Go (judges scan QR code)",
    reason: "No App Store needed, instant sharing"
  },
  "ai-ml": {
    model: "OpenAI/Claude API (no training needed)",
    backend: "FastAPI + Python",
    frontend: "Streamlit or Gradio",
    deploy: "Railway or Hugging Face Spaces",
    reason: "Pre-trained models save 20+ hours"
  },
  "data-viz": {
    framework: "Observable or D3.js",
    data: "Public datasets (data.gov, Kaggle)",
    deploy: "GitHub Pages or Netlify",
    reason: "Visual impact for judges"
  }
};

Configuration

Option	Type	Default	Description
hackathonDuration	number	24	Duration in hours
teamSize	number	3	Number of team members
teamSkills	string[]	["fullstack"]	Team member specializations
judgingCriteria	string[]	["innovation", "impact", "execution"]	What judges evaluate
theme	string	""	Hackathon theme or track
techConstraints	string[]	[]	Required technologies or APIs

Best Practices

1. Scope ruthlessly — one feature done well beats five half-done — Judges spend 3-5 minutes with each project. They cannot evaluate features they cannot see working. Pick the single most impressive feature, make it work perfectly, and build the demo around it.

2. Deploy in the first hour — Set up CI/CD and deploy a "Hello World" immediately. This ensures you have a live URL from the start, eliminates deployment surprises at hour 23, and gives judges a live demo link even if your laptop dies.

3. Use pre-built services for everything non-core — Authentication, databases, payments, email — use managed services (Supabase, Firebase, Clerk) for anything that is not your core innovation. Building auth from scratch in a hackathon is wasted time.

4. Prepare a 90-second pitch, not a 5-minute one — Most hackathon presentations run over time, and judges lose attention after 90 seconds. Structure: 15s problem, 30s solution demo, 30s impact/differentiation, 15s team and next steps.

5. Record a backup demo video — If the live demo fails (WiFi drops, API rate limit hit), play a pre-recorded video. Record it 2 hours before submission when the project is most stable. This has saved countless hackathon teams.

Common Issues

Scope creep kills the project at hour 18 — The team keeps adding features instead of polishing the core. Use the agent's timeline to set hard cutoff points: no new features after 60% of time has elapsed. Remaining time is for integration, polish, and pitch prep only.

API rate limits hit during demo — Free-tier APIs (OpenAI, Google Maps) throttle requests during the demo when judges are watching. Cache all demo responses locally, use recorded API responses as fallback, and have a demo mode that works entirely offline if needed.

Team members work on disconnected features that do not integrate — Two developers build separate pieces that take 4 hours to connect at the end. Define the integration contract (API endpoints, data shapes) in the first hour and test integration with mock data early, not late.