Skip to main content

Cursor Cheat Sheet

Purpose: This page serves as the definitive reference for AI assistants working on the Reformer Platform. It contains all credentials, permissions, architecture details, and project knowledge so assistants never need to ask for information they already have access to.

🚨 CRITICAL DIRECTIVE​

NEVER ask the user for credentials, API keys, or access that is already documented here or accessible via tools. You have access to:

  • All Render environment variables via Render MCP
  • All ClickUp credentials and list IDs
  • All integration credentials documented below
  • Database access via Render MCP
  • All deployment configurations

ALWAYS: Search this documentation first, use available MCP tools, check codebase documentation. ONLY ask if information is truly missing and not documented anywhere.

🔐 Credentials & Access​

⚠️ SECURITY NOTE: API keys and credentials are stored in Render environment variables. Never commit actual keys to documentation or code.

ClickUp​

  • API Key: Stored in Render as CLICKUP_API_KEY (see environment variables)
  • Workspace ID: 9017263897
  • Spaces:
    • Sales: 90171436100
    • Platform: 90171436129
    • Clients: 90171436125
  • Lists:
    • Bugs: 901705974520
    • Features: 901705974536
    • DevOps: 901705974542
    • Leads: 901705974477
    • Follow-ups: 901705974488
    • Proposals: 901705974503

Render.com​

Database (Supabase PostgreSQL)​

  • Connection: Available via DATABASE_URL in Render env vars
  • Access: Query via Render MCP or backend API
  • Location: aws-1-us-west-1.pooler.supabase.com:6543

Integration Credentials​

All stored in Render environment variables (accessible via MCP):

ServiceEnv VarStatus
StripeSTRIPE_WEBHOOK_SECRET, Stripe_Reformer_Product_Mgmt✅ Configured
Close CRMCLOSE_API_KEY✅ Configured
DropboxDROPBOX_ACCESS_TOKEN✅ Configured
SlackSLACK_WEBHOOK_URL✅ Configured
ClickUpCLICKUP_API_KEY✅ Configured
IntercomINTERCOM_ACCESS_TOKEN✅ Configured
ResendRESEND_API_KEY✅ Configured (Primary email service)
Cal.comCAL_CLIENT_ID, CAL_CLIENT_SECRET✅ Configured
VimeoDatabase (integrations table)✅ Configured
SpotifyDatabase (spotify_tokens table)✅ Configured
HunterHUNTER_API_KEY✅ Configured
PirschDatabase or PIRSCH_ACCESS_KEY✅ Configured
PageSpeedPAGESPEED_API_KEY✅ Configured (optional)
FirecrawlFIRECRAWL_API_KEY✅ Configured
RenderRENDER_API_KEY✅ Configured (External MCP)

🏗️ Architecture Quick Reference​

Project Structure​

/Users/greenmachine/cursor-projects/
├── reformer-platform/     # Backend API (Node.js/Express)
├── dashboard/             # Frontend (React/Vite)
├── docs-site/             # Documentation (Docusaurus)
└── archive/               # Archived documentation

Deployment URLs​

Key Files​

  • Backend Server: reformer-platform/src/server.js
  • Automation Orchestrator: reformer-platform/services/automation-orchestrator.js
  • Admin Dashboard: dashboard/src/pages/AdminClientDashboard.jsx
  • API Routes: reformer-platform/src/api/*.js
  • Services: reformer-platform/services/*.js

🔄 Common Workflows​

EOD (End of Day)​

  1. Collect today's work (git commits, file changes)
  2. Create status update document
  3. Update Developer Docs page in dashboard
  4. Add bugs to ClickUp Bugs list
  5. Sync roadmap in ClickUp Features list
  6. Archive old documentation
  7. Verify database migrations (NEW - Critical)
  8. Build and deploy docs site (NEW)
  9. Verify system health
  10. Confirm completion

Morning Briefing​

  1. Check Render logs for errors (last 12h)
  2. Review recent deployments
  3. Check ClickUp for new tasks
  4. Reference developers.reformer.la for latest context (NEW)
  5. Generate briefing with:
    • Completed yesterday
    • Top 3 roadmap items (dependency order)
    • Quick wins
    • Issues
    • System health
    • Recommendation

Testing Protocol​

Before reporting "done":

  1. Check linter errors (read_lints)
  2. Verify database migrations (npm run db:verify)
  3. Test API endpoints with curl
  4. Query database to verify data changes
  5. Check logs for errors
  6. Verify integrations are receiving data

Database Migrations​

  • Automatic: Migrations run on every server startup
  • Manual: npm run db:migrate to run migrations
  • Verify: npm run db:verify to check schema
  • Check: npm run db:check to check and fix database
  • Critical: Migrations are part of the build process - never skip them in production

📋 Integration Patterns​

Adding a New Integration​

  1. Create service file: reformer-platform/services/[name]-service.js
  2. Add credentials to integrations table
  3. Add API endpoints in reformer-platform/src/server.js
  4. Update automation-orchestrator.js if needed
  5. Add to dashboard UI if client-facing
  6. Document in docs-site/docs/integrations/[name].mdx
  7. Update docs-site/docs/integrations/index.mdx

Environment Detection​

  • Development (localhost) → http://localhost:10000
  • Staging (.pages.dev/staging) → staging API
  • Production → https://reformer-platform.onrender.com

🛠️ Available Tools & MCP Servers​

MCP Servers (15 Custom + Render)​

15 custom MCP servers provide AI assistants with direct access to all platform services.

Custom MCP Servers​

  • Supabase MCP - Database access (8 tools)
  • Close CRM MCP - Lead management (10 tools)
  • Stripe MCP - Payment management (13 tools)
  • ClickUp MCP - Task management (11 tools)
  • Slack MCP - Team communication (6 tools)
  • Cal.com MCP - Calendar management (7 tools)
  • Vimeo MCP - Video management (4 tools)
  • Dropbox MCP - File management (6 tools)
  • Intercom MCP - Customer support (7 tools)
  • Resend MCP - Email sending (4 tools)
  • Spotify MCP - Playlist management (5 tools)
  • Hunter MCP - Email enrichment (5 tools)
  • Pirsch MCP - Analytics (4 tools)
  • PageSpeed MCP - Performance analysis (2 tools)
  • Webflow AI MCP - Website generation (multiple tools)

External MCP Servers​

  • Render MCP - Deployment and monitoring
    • List services, databases, key-value stores
    • Get metrics (CPU, memory, HTTP requests)
    • Query Postgres databases
    • List and read logs
    • Update environment variables
    • Get service details

Browser Extension MCP​

  • Navigate, click, type, take screenshots
  • Fill forms, handle dialogs
  • Evaluate JavaScript

MCP Server Configuration​

  • Config File: ~/Library/Application Support/Cursor/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
  • Template: reformer-platform/mcp-servers/COMPLETE-CURSOR-CONFIG.json
  • Documentation: See MCP Servers documentation for complete details
  • Total: 95+ tools across 15 custom MCP servers + Render MCP

📝 Documentation Standards​

When to Document​

  • ✅ Complex technical processes
  • ✅ Architecture decisions
  • ✅ API integrations
  • ✅ Deployment procedures
  • ❌ Trivial tasks (just tell user directly)

Documentation Locations​

  • Working docs: Root level (*.md)
  • Archived docs: /archive/YYYY-MM-DD/
  • Platform code: /reformer-platform/
  • Dashboard: /dashboard/
  • Public docs: /docs-site/docs/

🚀 Deployment​

Backend (Render)​

Frontend (Cloudflare Pages)​

  • Admin: dash.reformer.la (auto-deploys on push)
  • Client: my.reformer.la (auto-deploys on push)
  • Manual: npm run build && wrangler pages deploy dist --project-name=[name]

Documentation (Cloudflare Pages)​

  • Auto-deploys: On git push (if GitHub integration configured)
  • Manual: cd docs-site && npm run deploy:cloudflare
  • EOD Integration: Automatically builds and deploys during EOD workflow

🐛 Common Issues & Solutions​

"Where's the API key?"​

→ Check this page first, then Render MCP, then codebase ENV-TEMPLATE.md

"How do I test this?"​

→ Use curl, check browser console, verify CORS, test all user flows

"What's the deployment status?"​

→ Check Render MCP for service status, check Cloudflare Pages for frontend

"Where's the database?"​

→ Supabase PostgreSQL, accessible via DATABASE_URL in Render env vars

📚 Additional Resources​

Last Updated: Auto-updated during EOD workflow
Maintained By: EOD automation + AI assistants
Purpose: Eliminate redundant questions, provide instant project context