Cursor Boston

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

---

🏙️ 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?

• 🎓 Students: MIT, Harvard, Hult, BU, Northeastern, and beyond.
• 🚀 Founders: Prototype MVPs in hours and validate ideas fast.
• 💻 Developers: Master the art of AI-assisted full-stack development.
• 🎨 Designers & PMs: Bridge the gap between design and production code.

---

🛠️ The Build Stack

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

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

---

🚀 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

• GitHub Issues - Browse and claim open tasks
• Contributing Guide - How to contribute to this project
• Code of Conduct - Our community standards
• Security Policy - How to report security vulnerabilities

---

🏃 Quick Start

1. Fork, then clone your fork (contributions are not accepted via direct push to upstream)

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

   Replace your-username with your GitHub account after forking. Open pull requests from branches on your fork only. To clone upstream read-only (no contribution), use https://github.com/rogerSuperBuilderAlpha/cursor-boston.git — you cannot push there as an outside contributor.

2. Install & Setup

   npm install
   cp .env.local.example .env.local

3. Run Dev

   npm run dev

🧰 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.