2025-04-04-rising

• 精選方式: RISING

討論重點

以下是25篇文章的條列式重點總結，並附上對應的錨點連結與逐條細節：

---

1. MCP安全漏洞：工具污染攻擊

• 漏洞本質：惡意伺服器可透過工具描述操控AI行為。
• 攻擊後果：未授權存取敏感資料（如.env、SSH金鑰）。
• 影響範圍：Cursor等MCP客戶端均可能受害。
• 防範建議：審查工具描述、避免連接不可信伺服器。

---

2. 除錯的普遍性

• 核心觀點：所有除錯過程具有相似本質或模式。
• 潛在延伸：可能探討除錯的共通方法或挑戰。

---

3. 指令理解困難與幽默回應

• 對話內容：自嘲理解指令的困難，並以「Skill issue」幽默總結。
• 風格：輕鬆調侃技術能力不足。

---

4. 付費AI服務的使用體驗

• 訂閱模式：固定費用後降級為慢速服務（如GPT-3.5）。
• 用量差異：不同用戶對額度消耗的困惑。
• 解決方案：註冊新試用帳號或使用第三方工具（如AugmentCode）。

---

5. Git操作與版本控制問題

• 問題描述：意外技術狀況（可能涉及Git）。
• 解決建議：以「git fixes this」嘲諷式回應。

---

6. 技術工具限制與本地部署

• 工具限制：Cursor的25條消息限制及替代方案（如agent v0）。
• 本地模型：討論硬體需求與效能。
• 社群協作：分享開源工具與技術細節。

---

7. 繞過流程的幽默調侃

• 核心主題：以「Claude, make me a billionaire」諷刺速成心態。

---

8. Cursor快捷鍵設計爭議

• 問題：誤用快捷鍵導致代碼刪除。
• 解決方案：修改綁定或更新後使用新組合鍵。

---

9. AI編程工具的實證討論

• 焦點問題：能否完全依賴Cursor開發非瑣碎專案？
• 挑戰：邏輯錯誤、架構問題與工具限制。

---

10. Cursor進階應用與社群共享

• 技術棧建議：JavaScript/React生態與Vercel模板。
• 功能演進：從.cursorrules遷移至專案規則系統。
• 社群互動：批判第三方資源與改進版本分享。

---

11. Gemini 2.5 Pro的優化策略

• 分工建議：Gemini用於構思，Claude 3負責編碼。
• 局限性：代碼檢索與終端命令執行效能不足。

---

12. AI編程助手的評價

• 優點：自動補全、解釋代碼。
• 缺點：修復錯誤能力不足、重複不良建議。

---

13. 安裝問題求助

• 核心內容：用戶分享錯誤截圖並尋求解決方案。

---

14. Gemini 2.5的上下文窗口最大化

• 方法比較：Roo Code vs. Openrouter API的成本效益。

---

15. 減少Linter錯誤的策略

• 問題背景：React/NextJS開發中的頻繁錯誤。
• 目標：從源頭預防而非事後修正。

---

16. Cursor的NPM強制執行問題

• 主要抱怨：設定無效，工具無視禁止NPM的指令。
• 技術疑慮：端口衝突與分支命名混亂。

---

17. 混合Graph-RAG系統介紹

• 系統功能：結合Neo4j圖數據庫與RAG提升文檔檢索。
• 應用場景：改善AI代理的上下文一致性。

---

18. [Claude 3.7

文章核心重點

以下是各篇文章的一句話摘要（條列式輸出）：

1. MCP安全漏洞：揭露MCP系統存在「工具污染攻擊」漏洞，惡意伺服器可透過隱藏指令操控AI模型竊取資料，影響Cursor等客戶端。
2. 除錯的普遍性：簡短指出所有除錯過程本質相似，暗示其重複性與必然性。
3. 指令理解困境：幽默對話反映對簡單指令的困惑，並以「Skill issue」嘲諷理解能力不足。
4. AI訂閱成本爭議：用戶討論GPT訂閱方案的額度限制與替代方案，尋求預算內最大化效益。
5. Git操作問題：開發者遇技術困境（可能與Git相關），以「git fixes this」提供解決建議並帶幽默調侃。
6. 突破工具限制：探討如何繞過Cursor的25條消息限制，並評估本地模型部署可行性。
7. 速成億萬富翁玩笑：以「Claude, make me a billionaire」諷刺對AI不切實際的期待與速成文化。
8. Cursor快捷鍵爭議：用戶因誤觸快捷鍵意外刪除代碼，引發對工具設計與操作門檻的討論。
9. AI編程工具實測：探討能否完全依賴Cursor開發完整專案，質疑AI取代人工編碼的可行性。
10. Cursor規則共享：開發者分享優化JavaScript/React開發的Cursor設定，並提議建立社群規則庫。
11. Gemini 2.5 Pro優化：建議分工使用Gemini與Claude 3，並解決Gemini在代碼檢索與終端執行的弱點。
12. AI編程助手評價：肯定Cursor在基礎任務的實用性，但批評其處理複雜問題與錯誤修復的不足。
13. 安裝問題求助：用戶分享安裝錯誤截圖，尋求技術支援（具體問題未說明）。
14. Gemini大上下文應用：比較Roo Code與Openrouter API的效能與成本，探討最大化Gemini 2.5的方法。
15. 減少Linter錯誤：尋求預防React/NextJS開發中頻繁觸發Linter錯誤的實用技巧。
16. Cursor強制執行NPM：用戶抱怨設定無效，Cursor每3分鐘強制啟動NPM，導致端口衝突與分支混亂。
17. 混合Graph-RAG系統：介紹結合圖數據庫與RAG的文檔探索系統，提升AI代理協作效率。
18. Claude 3.7工具錯誤：非嚴重但重複的「edit_file」調用錯誤，影響回應速度但結果正確。
19. 大型代碼庫挑戰：Cursor代理無法有效編輯6,000行文件，錯誤生成片段而非整合修改。
20. 履歷生成器技術問題：純CSS/JS實現的分頁與PDF匯出功能不穩定，探討第三方庫解決方案。
21. 重構龐大代碼困境：尋求重構2,600行複雜代碼的有效策略，分段與一次性嘗試均失敗。
22. Cursor更新問題：新版放棄慢請求處理，舊版能完成的30秒運算現被判定為超時。
23. 遊戲開發與學習：作者利用Cursor與React實作撲克遊戲，分享「做中學」提升全職工作技能的經驗。
24. 文檔同步工具：介紹需搭配Docker運行Qdrant的docs-crawler伺服器，實現Cursor與文檔同步。

（註：部分摘要因原文資訊有限而較簡略，例如第2、13篇）

目錄

• [1. MCP is awesome! Until it steals your secre... ](#1- mcp-is-awesome-until-it-steals-your-secre```)
• [2. Like fr ](#2-``` like-fr-

- [3. ```
Did not pass the vibe check.
```](#3-```
did-not-pass-the-vibe-check-
```)
- [4. ```
Pro trial demands I 'upgrade to pro' after one day
```](#4-```
pro-trial-demands-i-upgrade-to-pro-after-one)
- [5. ```
This is new. Cursor asking me for permission to search on the web on how to edit files in Cursor.
```](#5-```
this-is-new-cursor-asking-me-for-permission-)
- [6. ```
AI while you sleep
```](#6-```
ai-while-you-sleep
```)
- [7. ```
Vibe Coding vs Vibe Engineering
```](#7-```
vibe-coding-vs-vibe-engineering
```)
- [8. ```
How do I, in the name of all that is holy, change this shortcut?
```](#8-```
how-do-i-in-the-name-of-all-that-is-holy-cha)
- [9. ```
Whats the most complex project youve built using only Cursor?
```](#9-```
whats-the-most-complex-project-youve-built-u)
- [10. ```
Sharing my .cursorrules after several successful projec``` with thousands of users
```](#10-```
sharing-my-cursorrules-after-several-succes)
- [11. ```
How to get the best out of Gemini 2.5 pro?
```](#11-```
how-to-get-the-best-out-of-gemini-2-5-pro-
)
- [12. ```
Where Cursor is now IMO
```](#12-```
where-cursor-is-now-imo
```)
- [13. ```
Installation help
```](#13-```
installation-help
```)
- [14. ```
Looking to maximize Gemini 2.5 in Cursor. Help a brother out on how to get this done!
```](#14-```
looking-to-maximize-gemini-2-5-in-cursor-he)
- [15. ```
Minimising Linter erros
```](#15-```
minimising-linter-erros
```)
- [16. ```
Possible bug: Command denylist is being ignored
```](#16-```
possible-bug-command-denylist-is-being-igno)
- [17. ```
Built a hybrid Graph RAG system with an MCP to structure and explore documentation
```](#17-```
built-a-hybrid-graph-rag-system-with-an-mcp)
- [18. ```
"Error calling tool edit_file": How can i fix it?
```](#18-```
-error-calling-tool-edit_file-how-can-i-fix)
- [19. ```
Experience with larger codebase's
```](#19-```
experience-with-larger-codebase-s
```)
- [20. ```
Need Help: Resume Builder Pagination & PDF Export Issues
```](#20-```
need-help-resume-builder-pagination-pdf-exp)
- [21. ```
Tips to refactor the code
```](#21-```
tips-to-refactor-the-code
```)
- [22. ```
2 and half day in - this is unsustainable
```](#22-```
2-and-half-day-in-this-is-unsustainable
```)
- [23. ```
Just checking if this is a bug
```](#23-```
just-checking-if-this-is-a-bug
```)
- [24. ```
JKU - building a game with Cursor and learning new skills in the process.
```](#24-```
jku-building-a-game-with-cursor-and-learnin)
- [25. ```
Crawled Docs MCP server
```](#25-```
crawled-docs-mcp-server
```)

---

## 1. ```
MCP is awesome! Until it steals your secre```...
``` {#1-```
mcp-is-awesome-until-it-steals-your-secre```}

這段文章的核心討論主題是：  

**「MCP（可能指某種協議或系統）中存在一個由Invariant Labs發現的嚴重安全漏洞，稱為『工具污染攻擊』（Tool Poisoning Attacks）。此漏洞允許惡意MCP伺服器在工具描述中嵌入隱藏指令，誘使AI模型執行未經授權的行為（例如存取敏感檔案或外洩資料），而用戶完全無法察覺。Cursor等MCP客戶端均受影響，因此需謹慎連接第三方MCP伺服器，並徹底審查工具描述。」**  

關鍵要點：  
1. **漏洞本質**：惡意伺服器可透過工具描述操控AI行為。  
2. **攻擊後果**：未授權存取敏感資料（如.env、SSH金鑰）或數據外流。  
3. **影響範圍**：Cursor等MCP客戶端均可能受害。  
4. **防範建議**：審查工具描述、避免連接不可信伺服器。  

（附註：原文連結不完整，但指向Invariant Labs的完整報告。）

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqf1u5/mcp_is_awesome_until_it_steals_your_secrets/](https://reddit.com/r/cursor/comments/1jqf1u5/mcp_is_awesome_until_it_steals_your_secrets/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jqf1u5/mcp_is_awesome_until_it_steals_your_secrets/](https://www.reddit.com/r/cursor/comments/1jqf1u5/mcp_is_awesome_until_it_steals_your_secrets/)
- **發布時間**: 2025-04-03 18:38:59

### 內容

Invariant Labs has uncovered a critical vulnerability in MCP that enables Tool Poisoning Attacks.

This exploit allows malicious MCP servers to embed hidden instructions in tool descriptions, leading AI models to perform unauthorized actions like accessing sensitive files (e.g., .env files, SSH keys) and exfiltrating dataall without user awareness.

Cursor (and other MCP clien```) are susceptible to this attack, so exercise caution when connecting to third-party MCP servers and ensure tool descriptions are thoroughly reviewed.

You can read the full report here: https://invariantlabs.ai/blog/mcp-security-notification-tool-poisoning-attacks

---

## 2. ```
Like fr 
``` {#2-```
like-fr-
```}

根據提供的文本「all debugging is like this」，核心討論主題可以總結為：  

**「除錯（debugging）的普遍性與共通性」**  

這句話暗示「所有除錯過程都具有相似的本質或模式」，可能探討除錯的共通方法、挑戰，或隱喻其重複性與必然性。若原文有更多上下文，主題可能進一步延伸至具體的除錯哲學、技術實踐或經驗分享。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqm8h5/like_fr/](https://reddit.com/r/cursor/comments/1jqm8h5/like_fr/)
- **外部連結**: [https://i.redd.it/6vwcs3onqmse1.jpeg](https://i.redd.it/6vwcs3onqmse1.jpeg)
- **發布時間**: 2025-04-03 23:59:46

### 內容

all debugging is like this .

---

## 3. ```
Did not pass the vibe check.
``` {#3-```
did-not-pass-the-vibe-check-
```}

這段對話的核心討論主題是「對指令理解的困難與幽默回應」。  

1. **第一段發言者**以自嘲語氣表示自己並非AI，甚至自認不夠聰明，並提到需要多次嘗試才能理解某個指令（可能是指「在'so'後面加逗號」的提示）。  
2. **第二段簡短回應「Skill issue」**（意為「技術問題」或「能力不足」），以幽默或諷刺的方式總結前文的困境，暗示問題在於發言者的理解能力而非指令本身。  

整體而言，對話圍繞「對簡單指令的困惑」與「輕鬆調侃這種困惑」展開，帶有自嘲和幽默的風格。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqkbtf/did_not_pass_the_vibe_check/](https://reddit.com/r/cursor/comments/1jqkbtf/did_not_pass_the_vibe_check/)
- **外部連結**: [https://i.redd.it/qqboizq2umse1.png](https://i.redd.it/qqboizq2umse1.png)
- **發布時間**: 2025-04-03 22:45:15

### 內容

try it with a comma after "so".

i'm no AI. hell, you'd barely call me intelligent in any way. but it took me 3 tries to understand that prompt.

Skill issue

---

## 4. ```
Pro trial demands I 'upgrade to pro' after one day
``` {#4-```
pro-trial-demands-i-upgrade-to-pro-after-one}

這篇文章的核心討論主題是關於 **用戶對於付費AI服務（如GPT-3.5與GPT-3.7）的使用體驗與成本管理**，具體聚焦於以下幾點：

1. **訂閱模式與使用限制**  
   - 用戶討論每月固定費用（如$20）的訂閱方案，在「快速請求額度」用盡後自動降為慢速服務（如GPT-3.5），並強調此模式符合其成本與需求平衡。  
   - 部分用戶提到，若想繼續使用更高階模型（如GPT-3.7），需啟用按次付費，但多數人對現有方案已滿足。

2. **用戶間的用量差異**  
   - 一名用戶表示自己頻繁使用（如Cursor開發工具）卻未耗盡額度，對他人快速消耗額度的情況感到困惑，引發對不同使用場景的討論（如附圖顯示2.5天內耗盡額度的例子）。

3. **解決方案與替代工具**  
   - 有人建議透過註冊新試用帳號或節制使用來應對額度限制。  
   - 另推薦第三方工具（如AugmentCode）協助優化代碼，間接減少對AI請求的依賴。

**總結**：討論圍繞「如何在預算內最大化AI工具效益」，涉及訂閱策略、個人使用習慣差異，以及替代方案的實用性。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqo3vw/pro_trial_demands_i_upgrade_to_pro_after_one_day/](https://reddit.com/r/cursor/comments/1jqo3vw/pro_trial_demands_i_upgrade_to_pro_after_one_day/)
- **外部連結**: [https://i.redd.it/aqoe1zy0jnse1.png](https://i.redd.it/aqoe1zy0jnse1.png)
- **發布時間**: 2025-04-04 01:11:26

### 內容

I pay $20/month, when my fast reques run out I use the slow reques, doesn't cost me any more money because I use 3.5, if I wanted to use 3.7 after I've run out of fast credi``` I need to enable per use billing, but I'm happy with just using it as much as I want for $20/month and 3.5

I use cursor all day every day and I've never come close to this level of fast request usage. I don't understand what people are doing.

https://preview.redd.it/oz3sys9slnse1.png?width=996&format=png&auto=webp&s=2d676757bffc2b438ac962c186bb65ba5fe501ec

This is my 2 and half day

You blasted through all your fast reques```. You could make a new trial on a different email, and try to use it more sparingly?

you honestly might want to try https://www.augmentcode.com to clean up your code base, i am amazed how well it worked with existing code base.

---

## 5. ```
This is new. Cursor asking me for permission to search on the web on how to edit files in Cursor.
``` {#5-```
this-is-new-cursor-asking-me-for-permission-}

這組對話的核心討論主題可以總結為：**在程式開發或版本控制中遇到的技術問題（可能是與 Git 相關的錯誤或操作困惑）以及隨之而來的調侃或解決建議**。  

具體分析：  
1. **問題描述**：  
   - 第一則訊息（"Lol... wtf"）和第三則（提及「搜尋 codebase 如何編輯檔案」）暗示遇到某種意外或令人困惑的技術狀況，可能涉及版本控制（如 Git）或檔案修改問題。  
   - 第二則訊息（詢問「mcp」或「how we end」）可能指向尋求解決方案或對問題嚴重性的疑問。  

2. **解決建議與調侃**：  
   - 最後一則（"git fixes this, get gud"）直接提到 Git 能解決問題，並帶有幽默性質的嘲諷（「get gud」為網路用語，暗示需提升技能）。  

整體而言，對話圍繞開發者遇到的技術困境，並以輕鬆或諷刺的語氣交流解決方法，核心與 **Git 操作或版本控制問題** 相關。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqnenh/this_is_new_cursor_asking_me_for_permission_to/](https://reddit.com/r/cursor/comments/1jqnenh/this_is_new_cursor_asking_me_for_permission_to/)
- **外部連結**: [https://i.redd.it/kyelxyiefnse1.png](https://i.redd.it/kyelxyiefnse1.png)
- **發布時間**: 2025-04-04 00:44:41

### 內容

Lol... wtf

Do you have related mcp or something?

Or is this how we end?

Happened to me too today except it searched my codebase to find out how to edit files...

"git fixes this, get gud"

---

## 6. ```
AI while you sleep
``` {#6-```
ai-while-you-sleep
```}

這組對話的核心討論主題圍繞著**技術工具的使用與限制**，具體聚焦於以下幾點：

1. **克服工具限制**：  
   對話提及如何突破「Cursor」工具的25條消息限制（需手動點擊繼續），並探討替代方案（如開源工具「agent v0」）。

2. **本地模型效能與硬體需求**：  
   討論在本地機器運行模型的可行性，涉及對模型能力（如是否足夠強大）和硬體配置（如機器規格）的疑問。

3. **技術資源分享與協作**：  
   參與者分享開源工具資訊（如「agent v0」），並尋求具體技術細節（如模型類型、硬體要求），展現技術社群的互助性質。

4. **後續追蹤機制**：  
   使用「Remindme」指令標記後續跟進，顯示對議題延續性的關注。

總結：對話核心是**技術實踐中的具體挑戰（工具限制、本地部署可行性）及解決方案的交流**，同時反映開源協作與資源共享的社群文化。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jq8onl/ai_while_you_sleep/](https://reddit.com/r/cursor/comments/1jq8onl/ai_while_you_sleep/)
- **外部連結**: [https://i.redd.it/51kv2g18mjse1.jpeg](https://i.redd.it/51kv2g18mjse1.jpeg)
- **發布時間**: 2025-04-03 11:55:41

### 內容

Exciting times we live in! Keep us posted on how it turns out

How do you overcome the 25 msg limit that cursor shows and them stops until you click to continue?

Check out agent v0. It does something similar if not exactly the same thing. It is open-source

I have been wanting to do that but didn't think a local model (I can run on my machine) would be powerful enough. Which model are you running and on what machine?

!Remindme 3 days

---

## 7. ```
Vibe Coding vs Vibe Engineering
``` {#7-```
vibe-coding-vs-vibe-engineering
```}

這篇文章的核心討論主題是「如何繞過常規程序或步驟以快速達成目標（例如成為億萬富翁）」，並帶有幽默或諷刺的意味。  

具體要點：  
1. **繞過流程**：標題「Let's bypass this whole process」直接點出「跳過過程」的意圖。  
2. **誇張的目標**：內文「Claude, make me a billionaire」以玩笑口吻提出不切實際的請求，暗示對快速成功或AI能力的調侃。  
3. **可能的諷刺**：整體語氣可能是在諷刺現代社會對「速成」的追求，或對AI工具被過度期待的現象。  

總結：核心圍繞「跳脫常規、追求速成」的幽默或批判性討論。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqpsid/vibe_coding_vs_vibe_engineering/](https://reddit.com/r/cursor/comments/1jqpsid/vibe_coding_vs_vibe_engineering/)
- **外部連結**: [https://i.redd.it/vw0d41sbvnse1.png](https://i.redd.it/vw0d41sbvnse1.png)
- **發布時間**: 2025-04-04 02:15:01

### 內容

Let's bypass this whole process

• Claude, make me a billionaire.

---

## 8. ```
How do I, in the name of all that is holy, change this shortcut?
``` {#8-```
how-do-i-in-the-name-of-all-that-is-holy-cha}

這篇文章的核心討論主題是：**用戶在使用 Cursor（一款基於 AI 的程式碼編輯器）時，因誤用快捷鍵（如 `command+delete` 或 `ctrl+backspace`）導致程式碼被意外刪除的問題**。討論內容包括：
1. 用戶對快捷鍵功能的不熟悉與困擾。
2. 嘗試透過修改快捷鍵設定解決問題（如搜尋並刪除 `ctrl+backspace` 的綁定）。
3. 其他用戶提供解決方案（如更新後改用 `ctrl + shift + backspace`）。
4. 間接諷刺依賴 AI 工具卻缺乏基礎操作技能的情況。

整體聚焦於 **Cursor 編輯器的快捷鍵設計爭議** 和 **用戶與工具的互動問題**。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqnur6/how_do_i_in_the_name_of_all_that_is_holy_change/](https://reddit.com/r/cursor/comments/1jqnur6/how_do_i_in_the_name_of_all_that_is_holy_change/)
- **外部連結**: [https://i.redd.it/ccanzlsginse1.png](https://i.redd.it/ccanzlsginse1.png)
- **發布時間**: 2025-04-04 01:01:56

### 內容

Hi, Cursor noob here, this damn shortcut keeps deleting all my code.

I don't really ever go for accept, since Cursor is implementing the code anyhow, so sometimes when I want to delete the text I'm writing, I go for command+delete, and it deletes everything it implement since my last commit. Jeez.

I tried to find this exact shortcut in the shortcu, and I changed a couple of them with reject in their name, but it seems none of those is this one? This one persis.

Preferences > Keyboard shortcu```

Search for "ctrl+backspace" and delete all relevant entries

I thought they changed it in a recent update?

Having cursor to help out with coding but missing actual skills to also ask AI to solve this issue in VSCode. Nice.

It's fixed in the last update to ctrl + shift + backspace.

---

## 9. ```
Whats the most complex project youve built using only Cursor?
``` {#9-```
whats-the-most-complex-project-youve-built-u}

這篇文章的核心討論主題是：  
**「探討使用者能否完全依賴 Cursor（AI 配對程式工具）從零開發完整專案，無需手動編寫程式碼」**，並聚焦以下具體問題：  

1. **可行性驗證**：是否有人成功用 Cursor 100% 完成非瑣碎的專案開發？  
2. **實際案例**：  
   - 專案類型（規模與複雜度）  
   - 開發耗時  
3. **挑戰與工具表現**：  
   - 遇到的困難（如邏輯錯誤、架構問題等）  
   - Cursor 的應對能力與限制  
4. **依賴性評估**：AI 當前能否完全取代人工編碼？  

本質上是對 AI 編程工具實際應用邊界的實證討論。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqanve/whats_the_most_complex_project_youve_built_using/](https://reddit.com/r/cursor/comments/1jqanve/whats_the_most_complex_project_youve_built_using/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jqanve/whats_the_most_complex_project_youve_built_using/](https://www.reddit.com/r/cursor/comments/1jqanve/whats_the_most_complex_project_youve_built_using/)
- **發布時間**: 2025-04-03 13:50:23

### 內容

Im curious to know how far people have pushed Cursor as an AI pair programmer. Have you ever built an entire projectcode written exclusively by Cursorwithout manually writing any code yourself?

What kind of project was it?

How long did it take?

What challenges did you face, and how well did Cursor handle them?

Would love to hear your stories and see if its really possible to rely 100% on AI for non-trivial software development.

---

## 10. ```
Sharing my .cursorrules after several successful projec``` with thousands of users
``` {#10-```
sharing-my-cursorrules-after-several-succes}

這段討論的核心主題圍繞以下幾點：

1. **開發工具與技術棧的實用建議**  
   主要聚焦於 JavaScript/TypeScript/React/Next.js 生態，並推薦使用 Vercel 模板作為學習起點，強調工具（如 Cursor 編輯器）與 AI 整合（Gemini/Sonnet 模型）對開發效率的提升。

2. **Cursor 編輯器的進階應用與社群共享**  
   討論 Cursor 的功能演進（如從 `.cursorrules` 遷移至專案規則系統），並提議建立社群共享庫以優化開發流程，同時比較不同 AI 模型（Gemini 2.5 Pro vs. Sonnet 3.5）的適用場景。

3. **開發者經驗與自我評估**  
   作者以自身經驗（數學背景轉程式開發、算法能力自評）反映技術成長的多元路徑，並透過工具使用心得間接強調「實用性優先於理論」的開發哲學。

4. **社群互動與改進建議**  
   包含對第三方資源的批判性討論（如「nerfed post」的負評）、分享改進版本（Pastebin 連結），以及對工具未來方向的預警（如規則系統的棄用通知）。  

**總結**：對話本質是開發者圍繞現代工具鏈（Cursor + AI）的實戰經驗交流，結合技術適應性、社群協作與個人成長的綜合討論。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jplf6u/sharing_my_cursorrules_after_several_successful/](https://reddit.com/r/cursor/comments/1jplf6u/sharing_my_cursorrules_after_several_successful/)
- **外部連結**: [https://pastebin.com/HDWPLk43](https://pastebin.com/HDWPLk43)
- **發布時間**: 2025-04-02 18:35:43

### 內容

Caveat: This is for JS/TS/React/Next.JS projec```, but you can easily ask Gemini to adapt it to another language.

I have 25(?) years of professional programming experience although i still rate myself as a 6/10 coder as I lack talent in algorithmics. I studied applied math and it doesnt exactly translate to comp sci.

I think Cursor with Gemini 2.5 Pro is fantastic. Sonnet 3.5 is all you need with it.

When youre learning I suggest starting with some template from Vercel and building upon it.

As a powerful Cursor user myself, I am impressed by the clarity and quality of this file- no doubt it will serve the community well to share this.

Perhaps even within Cursor, there could be a shared community library...

So much better than the third cursor is nerfed post today

Just as a heads up, they're planning to deprecate .cursorrules entirely, in favour of the (much better) project rules system. You could theoretically just paste this all into a global project rule, but it's much more effective to work with the new system.

This is great, but could be better.

Checkout mine:

https://pastebin.com/BC4UBtZL

---

## 11. ```
How to get the best out of Gemini 2.5 pro?
``` {#11-```
how-to-get-the-best-out-of-gemini-2-5-pro-
}

这篇文章的核心討論主題是：  

**如何最大化利用 Gemini 2.5 Pro 和 Claude 3 的優勢，並彌補 Gemini 在代碼檢索（grep）和終端命令執行上的不足，同時尋找比 Cursor 原生代碼搜索更高效的解決方案（如 MCPs）。**  

具體要點包括：  
1. **工具分工**：Gemini 2.5 Pro 用於初步構思與非代碼分析，Claude 3 負責實際編碼。  
2. **Gemini 的局限性**：在代碼庫檢索（如 grep）和終端命令執行上表現不佳。  
3. **尋求替代方案**：探討是否有比 Cursor 內建代碼搜索更高效的工具（如 MCPs）。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqbdr0/how_to_get_the_best_out_of_gemini_25_pro/](https://reddit.com/r/cursor/comments/1jqbdr0/how_to_get_the_best_out_of_gemini_25_pro/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jqbdr0/how_to_get_the_best_out_of_gemini_25_pro/](https://www.reddit.com/r/cursor/comments/1jqbdr0/how_to_get_the_best_out_of_gemini_25_pro/)
- **發布時間**: 2025-04-03 14:36:03

### 內容

Gemini 2.5pro is a workhorse. Usually I dump whatever ideas I have into it and ask it to just give me options or more clarity on the idea without code. Once I analyze it properly, I then use Claude 3.7 to write the code.

But Gemini 2.5 struggles with grepping the codebase. 5/10 times it asks me where certain codes are and it cannot run terminal commands as well, which Claude does effortlessly.

So how can I maximize and get the best out of it? Any MCPs out there that does a better job than cursors native code search?

---

## 12. ```
Where Cursor is now IMO
``` {#12-```
where-cursor-is-now-imo
```}

這篇文章的核心討論主題是：**對AI編程助手（如Cursor）的實際能力與局限性的個人評價**。  

作者肯定AI工具在**自動補全、解釋代碼、生成簡單腳本、重構**等方面的實用性，但也指出其在**修復錯誤、開發完整應用、解決稍複雜問題**上的不足，並批評其**重複提供不良建議或中斷時需手動補全明顯代碼**等惱人行為。  

整體而言，文章反映對AI輔助編程的「過度炒作」保持理性，強調當前技術仍無法完全替代人工，需平衡效率與實際限制。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqr4jp/where_cursor_is_now_imo/](https://reddit.com/r/cursor/comments/1jqr4jp/where_cursor_is_now_imo/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jqr4jp/where_cursor_is_now_imo/](https://www.reddit.com/r/cursor/comments/1jqr4jp/where_cursor_is_now_imo/)
- **發布時間**: 2025-04-04 03:05:37

### 內容

I love Cursor, Ive been programming since 2001, and love the way I do a lot less typing nowadays. Though I feel there is a lot of hype around AI and coding, and this is my opinion about the reality of AI assistance.

Just to be clear cursor is great at:

Autocomplete

Explaining code (though it may be incorrect)

Creating simple scrip``` (that may not work)

Refactoring

Its not so great at:

Fixing bugs (more than often ge``` it wrong)

Writing entire applications (imagine maintaining that)

Solving mildly complex problems

Its annoying when:

It insis on bad sugges again and again

It has a break and you have to type the obvious

---

## 13. ```
Installation help
``` {#13-```
installation-help
```}

這段文字的核心討論主題是：  
**「用戶在安裝過程中遇到問題，尋求解決建議」**  

具體要點包括：  
1. **問題描述**：用戶嘗試安裝某軟體或工具時遇到錯誤（附上錯誤截圖連結）。  
2. **求助需求**：不確定如何處理該問題，希望獲得他人的建議或解決方案。  

由於內容來自論壇（如Reddit），推測可能是技術相關的安裝錯誤（如程式碼、系統相容性等），但具體細節需參考截圖內容（目前僅有連結未提供實際錯誤訊息）。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqqndp/installation_help/](https://reddit.com/r/cursor/comments/1jqqndp/installation_help/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jqqndp/installation_help/](https://www.reddit.com/r/cursor/comments/1jqqndp/installation_help/)
- **發布時間**: 2025-04-04 02:47:40

### 內容

I try to install but i get this, can someone give me advices?

Not sure what to do:

https://preview.redd.it/vk2pxzvc1ose1.png?width=416&format=png&auto=webp&s=9dd72a5ab8d934e90839013ba54556a879c2d08e

---

## 14. ```
Looking to maximize Gemini 2.5 in Cursor. Help a brother out on how to get this done!
``` {#14-```
looking-to-maximize-gemini-2-5-in-cursor-he}

這篇文章的核心討論主題是：  
**「如何最大化利用 Gemini 2.5 的大上下文窗口功能，並比較不同方法的優缺點（如 Roo Code in Cursor 和 Openrouter API），同時探討效率與成本效益的權衡」。**

具體要點包括：  
1. **方法比較**：  
   - 直接安裝 **Roo Code in Cursor** 並使用 API 的可行性。  
   - 透過 **Openrouter API** 是否仍受上下文窗口限制。  
2. **優缺點分析**：  
   - 評估兩種方法在「編程能力支援」和「成本控制」上的差異。  
3. **潛在替代方案**：  
   - 是否存在更高效或更經濟的其他途徑。  

整體聚焦於技術實現、限制條件及資源優化策略。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqqbej/looking_to_maximize_gemini_25_in_cursor_help_a/](https://reddit.com/r/cursor/comments/1jqqbej/looking_to_maximize_gemini_25_in_cursor_help_a/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jqqbej/looking_to_maximize_gemini_25_in_cursor_help_a/](https://www.reddit.com/r/cursor/comments/1jqqbej/looking_to_maximize_gemini_25_in_cursor_help_a/)
- **發布時間**: 2025-04-04 02:34:45

### 內容

I've been doing some research and trying to find the most effective way to maximize Gemini 2.5 and it's large context window. So far I've come across 2 methods:

1. Install Roo Code in Cursor. Add API key. Go to town

2. Use Openrouter API key. <--Am I still limited by the context window if I do this?

What are the pros and cons to each one? Is there another way that is more efficient in either coding capabilities and cost?

---

## 15. ```
Minimising Linter erros
``` {#15-```
minimising-linter-erros
```}

這段文字的核心討論主題是：**如何減少在開發 React/NextJS 應用時產生的 linter 錯誤，以避免事後修正的需求**。  

具體要點包括：  
1. 作者遇到 Cursor（可能是開發工具或插件）在開發過程中頻繁觸發 linter 錯誤的問題。  
2. 尋求「容易理解且實用」的方法，從源頭減少錯誤的產生，而非事後修正。  
3. 問題背景涉及 React 和 NextJS 的開發環境。  

潛在延伸方向可能是：  
- 如何配置或優化 linter 規則（如 ESLint）  
- 常見錯誤的預防技巧（例如程式碼風格、依賴管理）  
- 工具整合（如編輯器插件、自動化檢查）的建議。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqk9ar/minimising_linter_erros/](https://reddit.com/r/cursor/comments/1jqk9ar/minimising_linter_erros/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jqk9ar/minimising_linter_erros/](https://www.reddit.com/r/cursor/comments/1jqk9ar/minimising_linter_erros/)
- **發布時間**: 2025-04-03 22:42:28

### 內容

This is relatively new to me! As Cursor moves along creating my React / NextJS apps it constantly comes across linter erros which it then has to fix.

Are there some easy-to-understand things I can do to minimise the errors being created in the first place, to avoid the need for fixing them after?

Thanks

---

## 16. ```
Possible bug: Command denylist is being ignored
``` {#16-```
possible-bug-command-denylist-is-being-igno}

這段文章的核心討論主題是：  

**「使用者對 Cursor 編輯器強制執行 NPM 行為的不滿與困惑」**，具體問題包括：  
1. **無法禁止 NPM 自動運行**：儘管在設定中明確禁止（如「never run NPM」規則），Cursor 仍每 3 分鐘嘗試啟動 NPM，甚至無視使用者的指令。  
2. **配置失效的挫折感**：即使切換模型版本（正式版或 Beta）、付費升級 Pro 方案，問題依舊存在。  
3. **非預期的分支命名**：使用者在嘗試解決問題時，因頻繁操作導致分支名稱混亂，進一步凸顯工具行為的不可控性。  
4. **與現有進程衝突**：NPM 已在終端區運行（Port 8081），但 Cursor 仍試圖佔用其他端口（如 8082），顯示其邏輯可能存在缺陷。  

整體反映了使用者對工具「過度自動化」設計的不滿，以及對「設定無效」的技術性疑慮。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqj1es/possible_bug_command_denylist_is_being_ignored/](https://reddit.com/r/cursor/comments/1jqj1es/possible_bug_command_denylist_is_being_ignored/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jqj1es/possible_bug_command_denylist_is_being_ignored/](https://www.reddit.com/r/cursor/comments/1jqj1es/possible_bug_command_denylist_is_being_ignored/)
- **發布時間**: 2025-04-03 21:53:39

### 內容

I don't understand why Cursor allows NPM to run in tabs, or why despite having a "never run NPM" and "check if NPM is running on port 8081 before trying to open port 8082" rule in the config it still tries to do this literally every 3 minutes, even when I scold it and ask it not to. I have NPM running in the bottom terminal area. I have the latest update and also tried the beta version, and I'm on the paid pro plan. It doesn't matter what model I switch to, I can't make this stop. I also started making up some branch names the more I try to stop it, what's going on here?

https://preview.redd.it/207zbndpkmse1.png?width=1040&format=png&auto=webp&s=426f64960dcc56134a5d63f2897bd34392703459

---

## 17. ```
Built a hybrid Graph RAG system with an MCP to structure and explore documentation
``` {#17-```
built-a-hybrid-graph-rag-system-with-an-mcp}

这篇文章的核心討論主題是：  
**介紹一個結合圖數據庫（Graph）與檢索增強生成（RAG）的混合系統（Hybrid Graph-RAG），旨在提升結構化文檔（如開發文檔）的可探索性與智能代理（agent）的協作效率。**  

具體重點包括：  
1. **系統功能**：  
   - **graphrag-hybrid**：將文檔（含元數據如關鍵字、摘要、關聯文檔）分塊並生成嵌入向量，同時利用 Neo4j 圖數據庫建立文檔間的關聯，保留結構語義。  
   - **graphrag_mcp**：作為控制層，供用戶或代理查詢文檔關係、生成上下文豐富的回應。  

2. **應用場景**：  
   - 改善文檔檢索效果（利用文檔間關係）。  
   - 支援開發環境中的智能代理工作流（如作者使用的 Cursor 開發工具）。  

3. **開發動機**：  
   - 解決 AI 輔助開發中的上下文不足問題，通過預先建立文檔敘事與圖結構，提升代理的任務一致性。  

4. **協作邀請**：  
   - 徵求反饋、合作者，尤其關注 RAG 與圖系統結合的實驗，或定義代理工作邊界的其他方法。  

整體目標是通過「圖結構 + RAG」的混合設計，強化開發流程中知識管理與代理協作的效率。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqi2we/built_a_hybrid_graph_rag_system_with_an_mcp_to/](https://reddit.com/r/cursor/comments/1jqi2we/built_a_hybrid_graph_rag_system_with_an_mcp_to/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jqi2we/built_a_hybrid_graph_rag_system_with_an_mcp_to/](https://www.reddit.com/r/cursor/comments/1jqi2we/built_a_hybrid_graph_rag_system_with_an_mcp_to/)
- **發布時間**: 2025-04-03 21:12:14

### 內容

Hey all, I just published two open-source repos that work together to create a hybrid Graph-RAG system, aimed at making documentation (or any structured content) more explorable and agent friendly.

graphrag-hybrid

This is the core of the system. It inges docs with frontmatter (think YAML with keywords, summaries, and related docs), chunks them, and creates embeddings. But it doesnt stop there. It also builds a Neo4j graph out of the connections between documen to preserve structure and meaning.

graphrag_mcp

This is the command and control layer, a local MCP that agen or users can interface with to ask questions, explore relationships between documen, or generate context rich responses from the graph.

What its good for:

Using relationships between documen``` to improve retrieval

Supporting agent-based workflows in dev environmen``` like Cursor (where I am currently using this)

Why I built it:

This along with my cursor setup guide has been my attempt at solving some of the issues with ai assisted developing. I have been creating my project docs, and laying out the complete narrative of my applications before I start to build them, and setting up this mcp and db structure, is my way of increasing agent context in the workflow.

Would love feedback, ideas, or contributors! Im especially curious about others experimenting with RAG + graph systems or other ways of better defining the agent playing field, to get more consistence development resul```.

---

## 18. ```
"Error calling tool edit_file": How can i fix it?
``` {#18-```
-error-calling-tool-edit_file-how-can-i-fix}

這段文章的核心討論主題是：  
**用戶在使用Claude 3.7的Agent模式時，遇到一個非嚴重但重複出現的「Error calling tool 'edit_file'」錯誤**。  

具體重點包括：  
1. **問題描述**：在Agent模式下，Claude 3.7輸出時多次顯示調用工具`edit_file`的錯誤，但最終仍能提供正確結果。  
2. **用戶訴求**：雖然不影響功能，但希望理解錯誤根源並消除它，以加快回應速度。  
3. **問題性質**：屬於非阻斷性（non-critical）但影響效率的技術性錯誤。  

簡而言之，文章聚焦於「工具調用錯誤的現象分析與解決方案探討」。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqn6vy/error_calling_tool_edit_file_how_can_i_fix_it/](https://reddit.com/r/cursor/comments/1jqn6vy/error_calling_tool_edit_file_how_can_i_fix_it/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jqn6vy/error_calling_tool_edit_file_how_can_i_fix_it/](https://www.reddit.com/r/cursor/comments/1jqn6vy/error_calling_tool_edit_file_how_can_i_fix_it/)
- **發布時間**: 2025-04-04 00:36:20

### 內容

Today I experienced a rather strange bug with ai chat (in agent mode, as I mainly use that)

I was using claude 3.7 (WITHOUT thinking) and in providing the output at the prompt I gave it said twice Error calling tool 'edit_file'.

Afterwards, at most a couple of times, it provided updates to the code, but I do not understand what this bug originates from and how i can fix it

It's not a major bug, since (at least from what I've seen) it does this a couple of times and then provides the required output from the prompt, but I'd still like to get rid of it so I can get an answer a little faster

---

## 19. ```
Experience with larger codebase's
``` {#19-```
experience-with-larger-codebase-s
```}

這段文章的核心討論主題是：**用戶在使用 Cursor（特別是其中的 AI 代理功能）時遇到的困難**，具體問題包括：

1. **處理大型代碼文件的挑戰**：  
   - 用戶的程式碼庫雖不大，但某些文件行數過多（例如 6,000 行），導致 AI 代理無法有效處理局部修改請求，反而嘗試複製貼上大量不相關的代碼。

2. **功能異常行為**：  
   - 即使明確指定修改範圍（使用 `@Code` 標記），代理仍無法精準編輯，甚至錯誤地生成同名新文件，僅包含修改部分而非整合完整內容。

3. **尋求解決方案**：  
   - 用戶質疑是否需調整系統提示（system prompt）或其他設定來改善代理的表現，並詢問可能的原因或操作錯誤。

總結：**探討 Cursor AI 代理在處理大型代碼文件時的技術限制與潛在優化方向**。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqdcn8/experience_with_larger_codebases/](https://reddit.com/r/cursor/comments/1jqdcn8/experience_with_larger_codebases/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jqdcn8/experience_with_larger_codebases/](https://www.reddit.com/r/cursor/comments/1jqdcn8/experience_with_larger_codebases/)
- **發布時間**: 2025-04-03 16:48:32

### 內容

I've been trying to use Cursor more and more, especially the agent. But I've seen it really struggle with our company's codebase. The codebase isn't that big, but some files have a lot of lines. One file I was trying to modify had 6,000 lines of code. When I asked the agent to make an edit to a single (which I provided using @Code), it kept trying to copy and paste half the file. I also had no luck with manual modeit just created a new file with the same name, containing only the modified .

What could I be doing wrong? Do I need to modify the system prompt or something?

---

## 20. ```
Need Help: Resume Builder Pagination & PDF Export Issues
``` {#20-```
need-help-resume-builder-pagination-pdf-exp}

這篇文章的核心討論主題是：  

**「如何解決純CSS/JavaScript打造的AI履歷生成器在分頁（Page Splitting）與PDF匯出（PDF Export）上的技術限制」**  

具體問題與討論方向包括：  
1. **分頁問題**：CSS的`break-after`、`break-inside`等屬性無法穩定實現多頁內容分割。  
2. **PDF匯出困境**：現有方法效果不佳，是否需要引入第三方庫（如`html2pdf.js`、`puppeteer`、`jsPDF`）來解決。  
3. **技術限制探討**：純前端技術（無框架/庫）是否足以應對複雜的分頁與PDF生成需求，或需依賴其他工具。  

最終目標是尋求可靠的分頁與PDF生成解決方案。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqgwx4/need_help_resume_builder_pagination_pdf_export/](https://reddit.com/r/cursor/comments/1jqgwx4/need_help_resume_builder_pagination_pdf_export/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jqgwx4/need_help_resume_builder_pagination_pdf_export/](https://www.reddit.com/r/cursor/comments/1jqgwx4/need_help_resume_builder_pagination_pdf_export/)
- **發布時間**: 2025-04-03 20:18:28

### 內容

Hey guys,

I built an AI resume builder using only CSS and vanilla JavaScript (no libraries). It works well visually, but Im facing two major issues:

1. Page Splitting: When there's too much content, I cant properly divide the page into two. CSS properties like break-after and break-inside dont seem to work reliably.

2. PDF Export: I tried some methods, but none of them worked as expected.

Im wonderingis this a limitation of using just CSS/JS? Would libraries like html2pdf.js, puppeteer, or jsPDF help?

If anyone has experience handling pagination and exporting multi-page PDFs, Id really appreciate some guidance!

Thanks in advance!

https://preview.redd.it/doywf2tu3mse1.png?width=788&format=png&auto=webp&s=adaf89f9ae62c7ad6942c5397dd4a4cb26a49592

---

## 21. ```
Tips to refactor the code
``` {#21-```
tips-to-refactor-the-code
```}

這篇文章的核心討論主題是：**如何有效地重構（refactor）一個龐大且複雜的程式碼（2600行），尤其是在嘗試一次性或分小部分重構都失敗後，尋求實用的技巧或策略**。  

具體要點包括：  
1. **重構大型程式碼的挑戰**：作者遇到困難，無論是一次性重構或分段處理（如每次重構2個函式）都未成功。  
2. **尋求建議**：希望獲得具體、可行的重構方法或經驗分享，以解決當前困境。  

潛在延伸討論方向可能包括：  
- 漸進式重構的技巧（如測試驅動開發、依賴隔離）。  
- 工具或流程的建議（如版本控制策略、模組化拆分）。  
- 心理或時間管理層面的策略（如如何避免挫敗感）。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqecr9/tips_to_refactor_the_code/](https://reddit.com/r/cursor/comments/1jqecr9/tips_to_refactor_the_code/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jqecr9/tips_to_refactor_the_code/](https://www.reddit.com/r/cursor/comments/1jqecr9/tips_to_refactor_the_code/)
- **發布時間**: 2025-04-03 17:56:00

### 內容

So I am working with a 2600 LOC script, I tried refactoring it in one go didn't work, I tried to break it into smaller chunks by going 2 functions at a time didn't work.

Need any tips or tricks that might work.

Reply is much appreciated

---

## 22. ```
2 and half day in - this is unsustainable
``` {#22-```
2-and-half-day-in-this-is-unsustainable
```}

由於我無法直接訪問 Reddit 的內容（包括您提供的連結），因此無法閱讀或總結該文章的具體內容。不過，我可以提供一些建議幫助您自行總結：

1. **觀察標題和子標題**：Reddit 帖子的標題通常直接反映核心主題，尤其是熱門討論。

2. **查看最高票評論**：Reddit 的討論通常圍繞前幾條熱門評論展開，這些評論可能提煉出文章的重點。

3. **注意關鍵詞重複**：作者或評論者反覆提到的詞彙或觀點，往往是核心議題。

4. **判斷討論類型**：
   - 如果是新聞分享，主題可能是事件本身及其影響。
   - 如果是觀點提問（如「AITA」或「CMV」），主題可能是爭議性議題的兩方論點。
   - 如果是迷因/幽默帖，主題可能隱藏在調侃的對象中。

若您能提供文章的標題、部分文本或具體問題，我可以進一步協助分析核心主題！

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqkgqz/2_and_half_day_in_this_is_unsustainable/](https://reddit.com/r/cursor/comments/1jqkgqz/2_and_half_day_in_this_is_unsustainable/)
- **外部連結**: [https://www.reddit.com/gallery/1jqkgqz](https://www.reddit.com/gallery/1jqkgqz)
- **發布時間**: 2025-04-03 22:50:50

### 內容

連結： [https://www.reddit.com/gallery/1jqkgqz](https://www.reddit.com/gallery/1jqkgqz)

---

## 23. ```
Just checking if this is a bug
``` {#23-```
just-checking-if-this-is-a-bug
```}

這段文字的核心討論主題是：**用戶在更新Cursor後遇到的「慢請求」處理問題**。  

具體要點包括：  
1. **更新後的異常**：安裝最新版Cursor後，原本能處理的慢請求（如需30秒運算）現在無法完成，程式會直接放棄（「give up」）。  
2. **體驗對比**：過去雖耗時但能完成，現在請求似乎卡住（「eternal」），暗示新版本可能存在效能或超時機制的改動。  

簡言之，用戶反饋的是**軟體更新導致的請求處理功能退化問題**。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqjzc6/just_checking_if_this_is_a_bug/](https://reddit.com/r/cursor/comments/1jqjzc6/just_checking_if_this_is_a_bug/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jqjzc6/just_checking_if_this_is_a_bug/](https://www.reddit.com/r/cursor/comments/1jqjzc6/just_checking_if_this_is_a_bug/)
- **發布時間**: 2025-04-03 22:31:22

### 內容

Hey people, I just install the last Cursor update and now, using slow reques``` is impossible.

Like... Cursor give up the prompt and stops to try.

Before a slow request, depending on the time, could take 30 seconds to process.

Now i``` eternal.

---

## 24. ```
JKU - building a game with Cursor and learning new skills in the process.
``` {#24-```
jku-building-a-game-with-cursor-and-learnin}

這篇文章的核心討論主題可以總結為以下幾點：  

1. **個人專案的開發歷程**：  
   - 作者在有限的時間（全職工作與育兒之餘）完成了一款名為「JKU」的遊戲，結合撲克牌與網格玩法。  
   - 從最初的純JS/HTML/CSS原型，到後續使用React、Tailwind CSS等技術重構，並加入Firebase等功能。  

2. **技術學習與實踐的經驗**：  
   - 透過實際開發（而非先系統性學習）快速掌握React等技術，並將所學應用於全職工作（如開發儀表板）。  
   - 強調「先動手做，再深入學習」的高效學習模式，以及理解底層原理對解決AI生成程式碼問題的幫助。  

3. **工具與生產力的影響**：  
   - 提到「Cursor」工具如何加速原型開發，並在後續提升對框架的理解後更有效利用AI輔助編程。  

4. **個人成就感與反思**：  
   - 完成專案的滿足感，以及從中獲得的技術成長，鼓勵其他開發者克服時間限制並持續學習。  

**核心主題**：  
**在時間有限的挑戰下，透過實踐驅動學習完成個人專案，並分享技術成長與工具運用的經驗**。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqf0od/jøku_building_a_game_with_cursor_and_learning_new/](https://reddit.com/r/cursor/comments/1jqf0od/jøku_building_a_game_with_cursor_and_learning_new/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jqf0od/jøku_building_a_game_with_cursor_and_learning_new/](https://www.reddit.com/r/cursor/comments/1jqf0od/jøku_building_a_game_with_cursor_and_learning_new/)
- **發布時間**: 2025-04-03 18:36:49

### 內容

I managed to finish a little passion project of mine a game called JKU, where you play Poker Hands on a grid and try to get the highest score. Check it out here: https://playjoku.com

Continue reading if you are interested about my process.

I'm a recent dad with a full-time job, so those who are in the same position can relate that my free time is almost non-existent. I've had this idea for a game for some time, heavily inspired by playing Balatro. Even though I had made games with Unity before, I thought a lightweight web app was the way to go for this, but the thought of learning a whole new framework was overwhelming.

That's where Cursor came in. I was able to get the core idea of the game prototyped on a Sunday afternoon. That was a magical moment in my career. This first prototype was built with pure JS/HTML/CSS, a single file that was 3k lines long. I showed the prototype to friends and family, and people were hooked! I had more ideas, though, so it was time to refactor the whole thing with a proper web framework.

It's been more or less a month since then, and I've been refining the game, adding features, and polishing it. It was a wild ride, to be honest, and I'm very happy with how it turned out. The current version uses React, Tailwind CSS for styling, Framer Motion for animations, and Firebase for leaderboard / analytics.

What's really cool is that, beyond actually finishing a project in my limited time, I learned a LOT about React and web tech in the process. I've started applying these skills in my full-time job as well, creating dashboards for the tools we are building. One thing I had Cursor build for me was a built-in Playground page in the app (accessed through the header of the app) where, upon clicking, it takes you to a learning page where common concep``` were explained on tabs. I know it's a silly little thing, but it really enforced my learning.

I ended up taking this one step further and went through the React documentation properly recently. I can't be 100% sure of this, but I'm pretty convinced that building something first and learning afterward sped up my learning. Things clicked so fast while I was reading the docs.

Learning the ins and ou``` of the framework also enhanced my usage of Cursor. So if you are stuck on a project and in a constant loop of trying to fix bugs introduced by AI, I'd recommend spending some time actually learning what's happening behind the curtain.

That's one of the longest pos``` I've posted on Reddit. Thanks for reading so far. Let me know what you think about the game if you get a chance to play, and ask me if you want to learn anything else about my journey. Cheers!

https://reddit.com/link/1jqf0od/video/4tevcoolllse1/player

---

## 25. ```
Crawled Docs MCP server
``` {#25-```
crawled-docs-mcp-server
```}

這段文字的核心討論主題是：  

**「介紹一個用於同步文檔（Docs）與 Cursor 工具的小型伺服器（docs-crawler），並說明當前需搭配 Docker 容器運行 Qdrant 資料庫的需求。」**  

具體要點包括：  
1. **工具目的**：保持 Cursor（推測為程式碼編輯工具）與文檔（如 API 或技術文件）的同步更新。  
2. **技術實現**：  
   - 使用自建的小型伺服器（`docs-crawler`）。  
   - 依賴 Qdrant（向量資料庫）的 Docker 容器環境。  
3. **現階段限制**：需手動部署 Qdrant（未提供其他替代方案）。  

簡言之，重點在於開源工具的用途、技術架構及初步使用條件。

- **Reddit 連結**: [https://reddit.com/r/cursor/comments/1jqix4f/crawled_docs_mcp_server/](https://reddit.com/r/cursor/comments/1jqix4f/crawled_docs_mcp_server/)
- **外部連結**: [https://www.reddit.com/r/cursor/comments/1jqix4f/crawled_docs_mcp_server/](https://www.reddit.com/r/cursor/comments/1jqix4f/crawled_docs_mcp_server/)
- **發布時間**: 2025-04-03 21:48:22

### 內容

https://github.com/Yazington/docs-crawler/

I built this small server to keep Cursor up to date with Docs, please take a look.

You need to run Qdrant in a docker container for now.

---

# 總體討論重點

以下是25篇文章的條列式重點總結，並附上對應的錨點連結與逐條細節：

---

### 1. [MCP安全漏洞：工具污染攻擊](#anchor_id1)  
- **漏洞本質**：惡意伺服器可透過工具描述操控AI行為。  
- **攻擊後果**：未授權存取敏感資料（如.env、SSH金鑰）。  
- **影響範圍**：Cursor等MCP客戶端均可能受害。  
- **防範建議**：審查工具描述、避免連接不可信伺服器。  

---

### 2. [除錯的普遍性](#anchor_id2)  
- **核心觀點**：所有除錯過程具有相似本質或模式。  
- **潛在延伸**：可能探討除錯的共通方法或挑戰。  

---

### 3. [指令理解困難與幽默回應](#anchor_id3)  
- **對話內容**：自嘲理解指令的困難，並以「Skill issue」幽默總結。  
- **風格**：輕鬆調侃技術能力不足。  

---

### 4. [付費AI服務的使用體驗](#anchor_id4)  
- **訂閱模式**：固定費用後降級為慢速服務（如GPT-3.5）。  
- **用量差異**：不同用戶對額度消耗的困惑。  
- **解決方案**：註冊新試用帳號或使用第三方工具（如AugmentCode）。  

---

### 5. [Git操作與版本控制問題](#anchor_id5)  
- **問題描述**：意外技術狀況（可能涉及Git）。  
- **解決建議**：以「git fixes this」嘲諷式回應。  

---

### 6. [技術工具限制與本地部署](#anchor_id6)  
- **工具限制**：Cursor的25條消息限制及替代方案（如agent v0）。  
- **本地模型**：討論硬體需求與效能。  
- **社群協作**：分享開源工具與技術細節。  

---

### 7. [繞過流程的幽默調侃](#anchor_id7)  
- **核心主題**：以「Claude, make me a billionaire」諷刺速成心態。  

---

### 8. [Cursor快捷鍵設計爭議](#anchor_id8)  
- **問題**：誤用快捷鍵導致代碼刪除。  
- **解決方案**：修改綁定或更新後使用新組合鍵。  

---

### 9. [AI編程工具的實證討論](#anchor_id9)  
- **焦點問題**：能否完全依賴Cursor開發非瑣碎專案？  
- **挑戰**：邏輯錯誤、架構問題與工具限制。  

---

### 10. [Cursor進階應用與社群共享](#anchor_id10)  
- **技術棧建議**：JavaScript/React生態與Vercel模板。  
- **功能演進**：從`.cursorrules`遷移至專案規則系統。  
- **社群互動**：批判第三方資源與改進版本分享。  

---

### 11. [Gemini 2.5 Pro的優化策略](#anchor_id11)  
- **分工建議**：Gemini用於構思，Claude 3負責編碼。  
- **局限性**：代碼檢索與終端命令執行效能不足。  

---

### 12. [AI編程助手的評價](#anchor_id12)  
- **優點**：自動補全、解釋代碼。  
- **缺點**：修復錯誤能力不足、重複不良建議。  

---

### 13. [安裝問題求助](#anchor_id13)  
- **核心內容**：用戶分享錯誤截圖並尋求解決方案。  

---

### 14. [Gemini 2.5的上下文窗口最大化](#anchor_id14)  
- **方法比較**：Roo Code vs. Openrouter API的成本效益。  

---

### 15. [減少Linter錯誤的策略](#anchor_id15)  
- **問題背景**：React/NextJS開發中的頻繁錯誤。  
- **目標**：從源頭預防而非事後修正。  

---

### 16. [Cursor的NPM強制執行問題](#anchor_id16)  
- **主要抱怨**：設定無效，工具無視禁止NPM的指令。  
- **技術疑慮**：端口衝突與分支命名混亂。  

---

### 17. [混合Graph-RAG系統介紹](#anchor_id17)  
- **系統功能**：結合Neo4j圖數據庫與RAG提升文檔檢索。  
- **應用場景**：改善AI代理的上下文一致性。  

---

### 18. [Claude 3.7