# Claude 3.7 + GPT 4.5 - now available in Cursor!

**URL:** <https://forum.cursor.com/t/claude-3-7-gpt-4-5-now-available-in-cursor/54127>\
**Category:** Release Discussions\
**Created:** [February 24, 2025, 8:22pm UTC](https://forum.cursor.com/t/claude-3-7-gpt-4-5-now-available-in-cursor/54127 "2025-02-24T20:22:34Z")\
**Posts on this page:** 1\
**Showing post:** 72

<div class="post-metadata">

**Author:** ![mk148a](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mk148a/32/30390_2.png) [@mk148a](https://forum.cursor.com/u/mk148a)\
**Post date:** [March 1, 2025, 7:00pm UTC](https://forum.cursor.com/t/claude-3-7-gpt-4-5-now-available-in-cursor/54127/72 "2025-03-01T19:00:52Z")

</div>

I understand your frustration with Claude 3.5 struggling with large codebases. Based on the transcript you shared, I can provide some helpful advice on how to use PRD (Product Requirement Document) and RFC (Request for Comments) approaches with Cursor to manage large projects more effectively.

## Using PRD and RFC Approach with Cursor

The approach demonstrated in the Turkish YouTube transcript is quite powerful for working with large codebases. Here’s how you can implement it:

### 1. Create a PRD Document

Start by creating a clear product requirements document that outlines:

- What your application does
- Required technologies
- Design patterns
- Technical specifications

### 2. Establish Cursor Rules

Create a set of rules for Cursor to follow when working with your code:

- Coding standards
- File/folder structure conventions
- Naming conventions
- Architecture principles

### 3. Create a Features Document

Break down your application into discrete features with clear specifications for each.

### 4. Generate RFCs for Individual Features

For each feature or change you want to implement, create an RFC document that includes:

- Technical design
- Required endpoints/functions
- Data models
- Database schema changes
- Security considerations
- Dependencies

### 5. Implementation One at a Time

Instead of asking Cursor to understand and modify your entire codebase at once, ask it to implement or modify just one specific RFC at a time.

## Why This Works Better

The key insight from the transcript is that by breaking down your project into smaller, well-documented chunks, you give Cursor a clearer context that prevents it from getting lost in the complexity of your entire codebase. Each RFC provides focused guidance for a specific task without requiring Cursor to understand the entire system at once.

## Example Prompt Pattern

Based on this RFC document:  
[Insert your RFC details here]

Please implement/modify the following specific feature in my codebase:  
[Describe exactly what needs to be changed]

Here are the relevant files:  
[Include only the necessary code files for this specific change]

This approach guides Cursor’s work within clear boundaries, significantly reducing the chance of it hallucinating or making unwanted changes to your code.

Regarding your question about Claude 3.7 returning online, I don’t have specific information about when it will be back and working properly. I would recommend checking Anthropic’s official channels for the most up-to-date information on Claude 3.7’s availability.

##Resource

[![](https://us1.discourse-cdn.com/cursor1/original/3X/c/a/ca4566ddb906dec89754862a85e32251cfd10dc2.jpeg "Cursor’a Derdimi Nasıl Anlattım? | PRD’den RFC’ye Adım Adım Proje Oluşturma | .NET 8 Supabase") ](https://www.youtube.com/watch?v=_fU372Q4IA4)

---

_[View the full topic](https://forum.cursor.com/t/claude-3-7-gpt-4-5-now-available-in-cursor/54127)._