Read docs in this order depending on your goal:
| Order | Doc | Who it’s for |
|---|---|---|
| 1 | GET_STARTED.md | First-time contributors, no coding background |
| 2 | DEVELOPMENT.md | Developers — setup, scripts, hooks, architecture |
| 3 | FIRST_CONTRIBUTION.md | Step-by-step first pull request |
| 4 | API.md | API route reference |
| 5 | API_CACHING.md | API cache TTLs, tags, and invalidation rules |
| 6 | RELEASING.md | Maintainers — versioning and GitHub Releases |
| 7 | SUPPLY_CHAIN.md | Security automation, dependencies, and trust signals |
| 8 | VERCEL.md | Why PRs do not deploy to Vercel; production-only settings |
| 9 | Architecture Decision Records | Why the project is built the way it is |
| 10 | STYLE_GUIDE.md and A11Y_PATTERNS.md | Contributors writing docs or client-side UI |
Site visitor map: USER_GUIDE.md lists every public section on cursorboston.com with one-line descriptions — start here when you're trying to find where something lives.
Feature contracts: PROMPT_TEMPLATE_LIBRARY_CONTRACT.md defines the proposed persistence, moderation, voting, and API surface for member-submitted prompt templates.
Generals (the strategy game at /game): open contribution surface for lore, units, spells, artifacts, castes, buildings, and UI. Start at generals/README.md.
Operations / events (not required for typical code contributions):
Repository policy docs (under .github/):
- Contributing · Support · Governance · Security · Changelog