Cursor Boston

The hub for Boston's AI-powered development community.
Built by builders, for builders, using Cursor.

---

🚀	New here? Never coded before? Start here. You don't need to know how to code. AI tools like Cursor, Claude Code, and Codex can do the technical work for you. We wrote a step-by-step guide in plain, simple language — no jargon, no experience required. Read the Get Started Guide →

---

🏙️ What is Cursor Boston?

Cursor Boston is a community-led platform designed to bring together the most ambitious developers, students, and founders in the Boston area. We focus on AI-native development workflows—leveraging tools like Cursor to ship production code at the speed of thought.

🎯 Who is this for?

• 🌱 Beginners & Students: Pick up AI-assisted development from day one — no experience required.
• 💼 Interns & Early-Career Devs: Level up fast by building real features with real tools.
• 💻 Working Developers: Sharpen your workflow, contribute to open source, and connect with peers.
• 🧠 Senior Engineers & Experts: Mentor others, shape the project, and push the boundaries of AI-native development.
• 🚀 Founders & Indie Hackers: Prototype MVPs in hours and validate ideas fast.
• 🎨 Designers & PMs: Bridge the gap between design and production code.

Whether you're writing your first line of code or your ten-thousandth — if you care enough to open Cursor and do some work, you belong here.

---

🛠️ The Build Stack

This platform is a living example of what you can build with Cursor and modern web tech:

• Frontend: Next.js 16 (App Router), Tailwind CSS, TypeScript
• Backend: Firebase (Auth, Firestore, Storage)
• Integrations: Discord/GitHub OAuth, Luma API, Framer Motion

---

🏗️ Architecture

graph TB
    subgraph Client["Browser"]
        UI["Next.js 16 App Router<br/>(React + Tailwind CSS)"]
        Auth["Firebase Auth<br/>(Email, Google, GitHub)"]
    end

    subgraph Vercel["Vercel"]
        Pages["Pages & Layouts<br/>(SSR / Static)"]
        API["API Routes<br/>(63 endpoints)"]
        MW["Middleware<br/>(CSRF, Rate Limit, Logging)"]
    end

    subgraph Firebase["Firebase"]
        Firestore["Cloud Firestore<br/>(Users, Events, Posts, Teams)"]
        Storage["Cloud Storage<br/>(Avatars, Uploads)"]
    end

    subgraph External["External Services"]
        Discord["Discord OAuth + Webhooks"]
        GitHub["GitHub OAuth + Webhooks"]
        Luma["Luma Events"]
        Mailgun["Mailgun Email"]
        Leaflet["CARTO + Leaflet Maps"]
    end

    UI --> Pages
    UI --> Auth
    Auth --> Firestore
    Pages --> API
    API --> MW
    MW --> Firestore
    MW --> Storage
    API --> Discord
    API --> GitHub
    API --> Mailgun
    UI --> Luma
    UI --> Leaflet

Loading

---

🚀 Build Something

Want to add a major feature to the platform? We have 6 open feature projects ready for contributors to claim and build:

#	Feature	Issue
1	Prompt & Rules Cookbook — share and discover Cursor workflows	#78
2	Achievement Badge System — gamified milestones for community activity	#79
3	AI Pair Programming Matchmaker — find your coding partner	#80
4	Public Community Analytics Dashboard — visualize community growth	#81
5	Interactive Community Event Map — Boston venues on a live map	#82
6	Lightning Talk Timer & Speaker Queue — real-time event tool	#83

Each feature is fully isolated — new routes, new Firestore collections, no entanglement with existing code. Pick one, comment to claim it, and ship it. See the Contributing Guide for how to get started.

---

📚 Community

• Documentation index - Order of docs for newcomers vs maintainers
• Get Started (No Experience Needed) - Plain-language guide for complete beginners
• Development Guide - Setup, scripts, troubleshooting, architecture
• First Contribution - Step-by-step first PR walkthrough
• Contributing Guide - Contribution policy and code style
• Support - Where to ask questions (Discord, issues, email)
• Governance - Roles, decisions, and maintainer process
• Maintainers - Pointer to governance and releases
• GitHub Issues - Browse and claim open tasks
• Code of Conduct - Our community standards
• Security Policy - How to report security vulnerabilities
• Accessibility - Our accessibility commitment and WCAG targets
• Contributors - Everyone who has contributed code
• Architecture Decisions - Why the project is built the way it is
• Changelog - Version history
• Vercel deployments - Production-only deploys (PRs do not trigger Vercel builds)
• API Reference - Full list of API endpoints

---

🏃 Quick Start

1. Fork, then clone your fork

   git clone https://github.com/your-username/cursor-boston.git
   cd cursor-boston

2. Install & run (no Firebase account needed)

   npm install
   cp .env.local.demo .env.local    # zero-config demo mode
   npm run dev                       # open http://localhost:3000

The site loads fully in demo mode — pages, layouts, and styling all work. Firebase features (auth, data) are disabled until you set up credentials.

Want full functionality? See docs/DEVELOPMENT.md for Firebase setup, all npm scripts, troubleshooting, and more.

First time contributing? See docs/FIRST_CONTRIBUTION.md for a step-by-step walkthrough.

🐳 Docker

A production-ready multi-stage Dockerfile is available at docker/Dockerfile:

# Build the image (pass Firebase config as build args)
docker build -f docker/Dockerfile \
  --build-arg NEXT_PUBLIC_FIREBASE_API_KEY=your-key \
  --build-arg NEXT_PUBLIC_FIREBASE_AUTH_DOMAIN=your-domain \
  --build-arg NEXT_PUBLIC_FIREBASE_PROJECT_ID=your-project \
  --build-arg NEXT_PUBLIC_FIREBASE_STORAGE_BUCKET=your-bucket \
  --build-arg NEXT_PUBLIC_FIREBASE_MESSAGING_SENDER_ID=your-id \
  --build-arg NEXT_PUBLIC_FIREBASE_APP_ID=your-app-id \
  --build-arg NEXT_PUBLIC_FIREBASE_DATABASE_URL=your-db-url \
  -t cursor-boston .

# Run the container
docker run -p 3000:3000 cursor-boston

The image uses Node 22 Alpine, runs as a non-root user, and includes a health check at /api/health.

---

🧰 Operations

Rate-limit cleanup (internal maintenance)

Run the internal apiRateLimits cleanup endpoint from this repo:

CRON_SECRET=your-secret npm run rate-limit-cleanup

Optional environment variables:

• RATE_LIMIT_CLEANUP_BASE_URL (default: http://localhost:3000)
• RATE_LIMIT_CLEANUP_DRY_RUN (true for no-delete simulation)
• RATE_LIMIT_CLEANUP_BATCH_SIZE (clamped to 1-500)
• RATE_LIMIT_CLEANUP_MAX_BATCHES (clamped to 1-20)

Examples:

# Dry run against production URL
CRON_SECRET=your-secret RATE_LIMIT_CLEANUP_BASE_URL=https://cursorboston.com RATE_LIMIT_CLEANUP_DRY_RUN=true npm run rate-limit-cleanup

# Real cleanup with tighter bounds
CRON_SECRET=your-secret RATE_LIMIT_CLEANUP_BATCH_SIZE=200 RATE_LIMIT_CLEANUP_MAX_BATCHES=3 npm run rate-limit-cleanup

---

🗺️ Roadmap

• v0.1: Initial Community Hub & Event Tracking
• v0.2: Enhanced Member Profiles & Social Integration
• v0.3: Community Discussion Boards
• v0.4: PWA & Mobile Optimization

---

Made with ❤️ in Boston.
Join us on Discord or Luma.