跳至主要内容

2025-04-01-rising

  • 精選方式: RISING

討論重點​

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

1. Do you think using LLMs is a skill?​

  • 核心爭議：使用AI工具（如提示詞工程）是否算專業技能
    • 質疑其技能價值，認為難以列入履歷
    • 承認經驗可避免常見錯誤
    • 工具與技能界線模糊

2. Claude unusable in 2025?​

  • 用戶不滿：Claude 3.7版本功能退化
    • 對話流暢度下降
    • 過度審查AI相關話題
    • 體驗不如舊版（o1）

3. Did Claude sh*t the bed for everyone today?​

  • 技術異常：記憶與任務處理失效
    • 短期記憶缺失（30秒內內容）
    • 所有任務執行困難
    • 強烈批評極端性問題

4. How Claude 3.5 Sonnet recovered my lost notepad file​

  • 數據恢復案例：從Windows二進制文件救回內容
    • 批評Windows隱藏路徑與不透明格式
    • Claude直接解讀亂碼成功
    • 觸發轉用Mac的決定

5. $50失敗經驗反思​

  • 開發挫折：付費工具未解決問題
    • Replit/Roo code無效
    • 仍肯定AI（如Claude）提升效率
    • 聯邦政府員工的自動化需求

6. Dive桌面應用更新​

  • 開源工具強化
    • 多模型支援（OpenAI/Claude/Gemini）
    • 新增訊息編輯、後臺運行等UX優化
    • 簡化MCP Server安裝

7. Claude 3.7編碼能力退化​

  • 響應式設計任務失敗
    • 空洞回應（「You’re right」）但未修正
    • 對比過往高效表現
    • 對話重置加劇挫敗感

8. API點數到期爭議​

  • 商業行為批評
    • 痛批OpenAI/Anthropic點數失效政策
    • 投訴需附詳細環境資訊
    • 社群揭露剝削性手段

9. MCP文件系統優化​

  • 效能調優實務
    • 移除遞迴搜尋工具（如search_files）
    • 修改原始碼限制非必要功能
    • 改善回應速度

10. Pro版節流限制​

  • 付費體驗不佳
    • 修改字體等簡單任務失敗
    • 節流中斷導致HTML結構破壞
    • 考慮退款申訴

（因篇幅限制，以下為簡要條列，完整細節請參照錨點連結）

11-25. 快速摘要​

  1. AI頻繁拒絕回應：Claude 3.7過度限制
  2. PRO版訊息限制重啟：Anthropic政策收緊
  3. 服務穩定性危機：每日停機數小時
  4. 版本權限矛盾：3.7免費但3.5需Pro版
  5. 三年AI編程心得：非開發者的學習痛點
  6. Figma整合AI：影片未提供內容

文章核心重點​

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

  1. Do you think using LLMs is a skill?
    爭論「使用AI工具」是否足以被視為專業技能，質疑其履歷價值但承認經驗重要性。

  2. Claude unusable in 2025?
    用戶批評Claude 3.7版本功能退化，對話限制過多導致體驗不如舊版。

  3. Did Claude sh*t the bed for everyone today?
    指出Claude突發性記憶失效與任務處理異常，引發對技術缺陷的質疑。

  4. How Claude 3.5 Sonnet recovered my lost notepad file
    分享Claude從二進制亂碼還原記事本內容的案例，凸顯AI彌補系統設計缺陷的能力。

  5. I went through $50 tonight trying to get AI/Claude to fix errors
    開發者花費50美元未解決問題，轉而依賴AI工具提升效率，反映技術依賴與挫折。

  6. v0.7.3 Update: Dive, An Open Source MCP Agent Desktop
    介紹Dive桌面應用更新，強調多模型支援與使用者體驗優化。

  7. Has Claude 3.7 become a stupid coder, lately?
    用戶抱怨Claude解決響應式設計問題時能力退步，陷入無效修正循環。

  8. DO NOT add a lot of money to API account
    警告AI服務商（如Anthropic）可能無預警使預付點數失效，批評商業手法不透明。

  9. Optimizing Claude's MCP Filesystem Server
    技術指南：透過修剪工具權限解決Claude文件系統遞迴搜尋導致的效能問題。

  10. Conversation limits for Pro version are making Claude unusable
    付費用戶因節流限制中斷簡單任務（如修改字體），考慮申訴退款。

  11. We are unable to serve your request
    討論Claude頻繁拒絕回答的挫折感，延伸對AI功能邊界的質疑。

  12. Message limit is back enforced even for PRO
    觀察到Sonnet 3.5使用限制無預警收緊，推測服務商政策調整。

  13. i'm starting lose my mind, claude is down every day
    用戶抱怨Claude服務不穩定（每日斷線、記錄消失），影響信任與付費意願。

  14. Claude 3.7 is free but 3.5 is in PRO
    （內容無法確認，推測為Claude版本差異與訂閱策略討論。）

  15. Three years of AI coding: What I've learned about using Claude effectively
    非開發者分享AI輔助編程經驗，呼籲系統化教學與工作流程優化。

  16. Figma MCP : AI for Figma
    （無法訪問影片內容，推測為AI整合設計工具的應用案例。）

  17. Claude will return soon
    用戶遭遇服務阻斷，推測因伺服器過載，建議VPN切換與有效回報方法。

  18. Best AI model for web design in 2025?
    醫師尋求AI工具（如Claude或Gemini）協助網站設計與患者吸引策略。

  19. i love that i can use a MCP with RStudio...
    讚揚MCP整合RStudio自動生成代碼與圖表，大幅提升數據分析效率。

  20. I tested Gemini 2.5 Pro against Claude 3.7 Sonnet
    分析Gemini 2.5 Pro在性價比上威脅Claude開發者市場，但後者推理能力更細膩。

  21. New #1 open-source agent on SWE-Bench
    開源AI代理結合Claude 3與O1模型，通過SWE-bench驗證自動修復GitHub問題的能力。

  22. Benefits of using API vs Web?
    探討API相對於網頁介面在開發自動化、結構化輸出與工作流整合的優勢。

  23. I didn't want to pay $20 a month for Claude...
    （內容為Reddit版規，非文章摘要。）

  24. Custom Instructions: Leveraging Claude 3.7 Sonnet's Extended Thinking...
    分享整合個人與工作模式的自訂指令模板，讚賞Claude 3.7情境切換流暢性。

  25. “In my current form…”
    Anthropic研究揭示Claude回應前會先進行抽象

目錄​

1. Do you think using LLMs is a skill?​

這篇文章的核心討論主題是：「是否應將『使用AI工具（如提示詞工程）』視為一種值得培養或列在履歷上的技能」。

作者提出以下關鍵觀點：

  1. 質疑其作為「技能」的價值：雖然長期使用AI工具會累積經驗，但作者認為這難以被歸類為真正的「技能」，甚至不願將其列入履歷。
  2. 承認經驗的重要性：觀察到許多人因缺乏使用經驗而陷入常見錯誤，需透過實際操作來改善。
  3. 工具與技能的界線：討論「單純使用工具」與「具備技能」之間的模糊地帶，反映對新興技術能力定位的困惑。

整體而言，文章聚焦於對「AI工具使用經驗」是否構成專業技能的爭議，並探討其實際價值與社會認可度。

內容​

I have been using them since they became commercially available, but it's hard for me to think of these as a real skill to develop. I would never even think of putting them/prompt engineer as a skill on a resume/cv. However, I do see many people fall victim to certain pitfalls that are remedied with experience.

How do you all view these? Like anything you gain experience with use, but I am hard-pressed to categorize usage as a tool with a skill level.

討論​

評論 1:

Is using AI a skill? Sure. Like being able to quickly and efficiently navigate and use the internet is a skill. Back in the late 90s or early 2000s the majority of people could not “surf the information superhighway” yet, and those that could did very well for themselves. Eventually everyone catches up tho but it takes a generation. The kids growing up with LLMs and other generative ai may be able to accomplish things we could only dream of since we are used to doing things slow and manual.

評論 2:

If you even have to ask this question and doubt it, you really don't understand how LLMs work. LLMs are a probability machine, at the end of the day. The skill lies in structuring prompts and providing the information and directions within them to achieve maximum probability that the output matches your desired goal. So yes, it is a skill.

評論 3:

Oh it’s a skill lol. Prompting can go deep. People over at r/DataAnnotation could attest to that

評論 4:

Yes, for now it's definitely a skill.

We're far from "Make me an X" and the AI magically gets what you need with a few questions.

You need to write prompts in certain ways so it can deliver, how to break the infinite hallucinations loops, etc.

評論 5:

Critical thinking is a skill.

2. Claude unusable in 2025?​

這篇文章的核心討論主題是：
用戶對ClaudeAI 3.7版本更新後表現的不滿，具體批評其對話能力下降、限制過多（例如連AI相關話題都難以正常討論），並認為新版甚至不如舊版（o1），質疑開發團隊的調整方向。

關鍵點包括：

  1. 功能退化：新版對話流暢度與實用性顯著降低。
  2. 過度限制：審查規則嚴苛，影響正常對話（尤其AI相關主題）。
  3. 用戶失望：從「最喜愛的工具」變成體驗不如舊版的落差感。
  4. 背後原因質疑：隱含對開發團隊政策或技術調整的困惑與批評。

內容​

I've been using ClaudeAI since the latest 3.7 update and it's not that it's just not the same, it's not even close to what it was before. It was my favorite before, but now it's worse than o1, with too many rules and restrictions of what it can talk about, such that I can't even maintain a normal conversation about AI! What is going on here?

討論​

評論 1:

I noticed this too. Good sonnet 3.5 is gone or nowhere to be seen. Most of the output done by 3.7 and 3.5 now are comparable to haiku or any chatgp.

Ive been using IDEs with sonnet 3.5 as well and it definitely feels like haiku output. Every claude instance feels the same in every IDE.

Weeks ago i could pretty much one shot a basic app with multiple screens. Nothing fancy. But now 3.5 cant even fix a basic layout in a single screen. It would make few mistakes, now it deletes and replaces code in every prompt.

The only one ive found feels kinda the same, is augment for vscode. It can pretty much do the same as old 3.5, but weaker.

評論 2:

Paying customer here. I made a few prompts this morning. Suddenly, I'm blocked out until 10:00 pm.

Like W. T. F.

評論 3:

It was unusable today. I wasted hours trying to work through a basic code question.

評論 4:

Used Claude extensively. Tried Gemini 2.5 pro yesterday. Claude better figure his shit out, like right NOW.

評論 5:

The only beef I have with 3.7 is I ask Claude for a simple Fibonacci function, and it goes full Silicon Valley and writes a whole Java backend, spins up a React frontend, and deploys it to the cloud. I only just wanted 5 lines of code.

3. Did Claude sh*t the bed for everyone today?​

這篇文章的核心討論主題是 Claude 人工智慧模型的記憶與任務處理能力出現異常，具體表現為：

  1. 短期記憶失效：無法記住使用者前30秒提供的資訊。
  2. 任務執行困難：在處理「所有任務」時出現問題，包括本應更穩定的「思考模式」（thinking mode）。
  3. 效能異常的嚴重性：用強烈語氣（如「literally all」「completely forgetting」）強調問題的普遍性和極端性。

本質上是在探討Claude當下可能存在的技術缺陷或系統不穩定現象，並表達對此異常狀況的困惑與不滿。

內容​

What in the world! Claude is struggling with literally all tasks. Like completely forgetting everything I told it 30 seconds ago. Even on thinking mode!

討論​

評論 1:

When making a complaint, please

  1. make sure you have chosen the correct flair for the Claude environment that you are using: i.e Web interface (FREE), Web interface (PAID), or Claude API. This information helps others understand your particular situation.
  2. try to include as much information as possible (e.g. prompt and output) so that people can understand the source of your complaint.
  3. be aware that even with the same environment and inputs, others might have very different outcomes due to Anthropic's testing regime.
  4. be sure to thumbs down unsatisfactory Claude output on Claude.ai. Anthropic representatives tell us they monitor this data regularly.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

評論 2:

He's become Claude 0.7

A complete idiot, with no coherence. He looks like a kid in training.

評論 3:

bro its literally worse than chatgpt 3.5

評論 4:

Does literally anyone from Anthropic browse this subreddit and feel marginally bad that we pay for this product?

評論 5:

Yup

There was missing ")" in 1000 lines of HTML (that It typo'd) and I couldn't find - " if couldn't fix it in the artifact, it tried rewriting everything from scratch like 10 times before I gave up, took the last working version and gave it to o3mini.

4. How Claude 3.5 Sonnet recovered my lost notepad file when Windows failed me​

這篇文章的核心討論主題是：作者在使用Windows記事本時意外丟失工作內容，並在AI助手Claude的幫助下成功從二進制文件中恢復數據的經歷。具體要點包括：

  1. 問題起因：

    • 作者因強制關閉記事本導致未保存的TODO列表消失，Windows記事本的「自動保存」功能失效。

  2. 解決過程：

    • 在Claude的指導下，發現記事本數據以二進制格式（.bin文件）隱藏在系統目錄中，但直接打開為亂碼。
    • Claude僅通過觀察亂碼字符（如「后伀䐀伀㨀ഀⴀ...」）即準確推斷出原始文本內容，無需解碼工具。

  3. 技術批判與個人反應：

    • 批評Windows的數據存儲機制不透明（二進制格式+隱藏路徑），對比凸顯AI（Claude）的直觀解讀能力。
    • 作者因這次事件決定轉用Mac，表達對Windows系統可靠性的不滿。

  4. 分享目的：

    • 提供潛在的數據恢復方法（檢查TabState目錄），並推薦利用AI工具應急。

隱含議題：

內容​

So I fucked up today. Killed Notepad from Task Manager while working on my auth project. My entire TODO list - gone. Windows Notepad has "autosave" but it was nowhere to be found when I reopened it.

I asked Claude for help, and it suggested checking some temp folders. We eventually found some weird directory:

AppData\Local\Packages\Microsoft.WindowsNotepad_8wekyb3d8bbwe\LocalState\TabState

Inside were a bunch of .bin files that looked like complete garbage when opened.

After trying a BUNCH different encoding methods all day long, we got this weird output:


后伀䐀伀㨀ഀⴀ 椀洀瀀氀攀洀攀渀琀 瘀攀爀椀昀椀挀愀琀椀漀渀 昀漀爀...

Here's where it gets crazy - I showed Claude this gibberish and without running any code, it just straight up decoded it in its response. It looked at this mess of characters and said:

"Here's your list:

  • implement verification for connecting/disconnecting providers

  • update UI with messages for email conflicts

  • fix change password route not updating has_password"

And it was 100% my actual TODO list. Every item, perfectly recovered.

Windows stores our notes in some weird binary format in a hidden folder, but Claude could just "see" the text inside it. Saved my life.

Thought I'd share in case anyone else loses important files. And yes, I'm switching to Mac soon. Tired of Window's BS

討論​

評論 1:

What encoding produced the “weird output”? (If you don’t know, you can ask it :p)

Pretty cool it was able to help you solve this problem!

評論 2:

Still Notepad++> Windows 11 Notepad.

I find it confusing how Windows 11 Notepad allows me to open multiple windows with multiple tabs but when closing one of the window it will prompt you to save or disard all your tabs until it is the last only window opened then it will save and able to restore when open again like NotePad++.

評論 3:

Amazing and yes switch to mac os,

There was my final year project on word all night I made and I slept and at 9 am it was project submission, and guess what when i woke up for washroom and was going to sleep again at 7 15 am I found my doc was deleted ....

This was bug sometimes I had to recreate it in super saiyaan mode..

Never went to windows, On Ubuntu since and now switched to mac os.

評論 4:

[deleted]

5. I went through $50 tonight trying to get AI/Claude to fix errors.​

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

作者在開發應用程式時遇到技術困難，花費金錢尋求解決方案（如Replit和Roo code）但未成功，同時表達對AI工具（如Claude）提高生產力的依賴與期待。

具體重點包括：

  1. 技術挑戰與挫折：作者花費50美元嘗試使用Replit和Roo code解決問題，但未能成功。
  2. 對AI工具的正面評價：肯定AI（如Claude）節省時間、提升效率的價值，並希望進一步利用。
  3. 個人背景與動機：作為聯邦政府員工（非加密貨幣領域），目標是透過自動化工具改善工作效率。
  4. 對商業推廣的隱晦批評：提及Roo code的付費連結（如Claude積分）可能暗示對過度商業化的不滿。

整體圍繞「尋求技術解決方案」與「AI工具對生產力的影響」展開。

內容​

連結： [https://preview.redd.it/2r2ro4wwo4se1.png?width=622&format=png&auto=webp&s=cbaeb3e2fe79ec6f3f48b40f0fe52e27e7e1f95d

$50 to build a read only database viewer in my app so I can see if the script replit is legit. Well, not not legit, Replit couldn't figure out errors I was encountering in my app. $50 later, still not working. But using Roo code I had plenty of opportunity to use their links to buy Claude credits.

I'm not rich. I work in the fed government. Not the DOGE kind. I'm trying to build tools to help me automate and build shtuff. AI has saved me HOURS and I'm looking to use it more to increase productivity and efficiency more. ](https://preview.redd.it/2r2ro4wwo4se1.png?width=622&format=png&auto=webp&s=cbaeb3e2fe79ec6f3f48b40f0fe52e27e7e1f95d

$50 to build a read only database viewer in my app so I can see if the script replit is legit. Well, not not legit, Replit couldn't figure out errors I was encountering in my app. $50 later, still not working. But using Roo code I had plenty of opportunity to use their links to buy Claude credits.

I'm not rich. I work in the fed government. Not the DOGE kind. I'm trying to build tools to help me automate and build shtuff. AI has saved me HOURS and I'm looking to use it more to increase productivity and efficiency more. )

討論​

評論 1:

When making a complaint, please

  1. make sure you have chosen the correct flair for the Claude environment that you are using: i.e Web interface (FREE), Web interface (PAID), or Claude API. This information helps others understand your particular situation.
  2. try to include as much information as possible (e.g. prompt and output) so that people can understand the source of your complaint.
  3. be aware that even with the same environment and inputs, others might have very different outcomes due to Anthropic's testing regime.
  4. be sure to thumbs down unsatisfactory Claude output on Claude.ai. Anthropic representatives tell us they monitor this data regularly.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

評論 2:

Use Gemini 2.5.

Get Gemini pro, get their API.

I mean if you really want to spend to use Claude go ahead but google is free and pretty damn good. Plus context window is massive

評論 3:

I only use Claude API these days in Plan Mode (Cline) and then use Gemini 2.5 when I switch to Act Mode.

I ask Claude for detailed implementation ideas in Plan Mode and then switch. It creates code snippets which Gemini uses to build/correct code.

I don’t let the context go beyond 150K, I use a changelog.md and implementation-plan.md (updated by Gemini/claude when I need) to track and plan changes so knowledge carries over to new task when I need.

Edit: Also do refactor the code. It helps a lot. Smaller files are easier to edit using AI.. it won’t spend multiples times rewriting broken edits.

評論 4:

Use Claude Desktop with filesystem MCP server. $20/month instead of $40+ per day. But all the AIs suck at debugging. Have it explain clearly what it thinks it's doing, then look through the code yourself as best you can. If it's the same error over and over and it thinks it "fixed it this time" it probably didn't. My example ... it had "/api" in the {apiUrl} and was also adding it with the /api/endpoint/whatever causing a 404. Hours it went in circles, until I poked around at the js in devtools and found it. As clever as they are, Gemini, Claude, OpenAI all fall for their own stupid errors, until you can point out the real problem. Just sayin'.

評論 5:

I used gemini as much as I could. It could not figure out the issue. I went back to Claude.

6. v0.7.3 Update: Dive, An Open Source MCP Agent Desktop​

這篇文章的核心討論主題是 Dive 桌面應用程式的功能更新與特色，具體聚焦於以下兩個主要面向：

  1. 多模型支援與切換功能

    • 支援多種主流LLM服務（如OpenAI、Claude、Gemini等），並允許自定義模型。
    • 提供多模型切換能力，可靈活管理不同配置或API金鑰的MCP Server。

  2. 使用者體驗與性能優化

    • 新增實用功能如訊息編輯、回應重新生成、自動更新等。
    • 介面改進（如折疊區塊、快捷鍵邏輯調整）和錯誤提示優化。
    • 後臺運行與開機自啟等系統整合強化。

整體而言，文章旨在推廣Dive作為一個高效、靈活的開發工具，強調其對開發者的便利性（如簡化MCP Server安裝）與最新版本的功能升級。

內容​

Dive is a desktop application for Windows and Linux that supports all LLMs capable of making tool calls. It is currently the easiest way to install MCP Server. Offering real-time tool call embedding and high-performance system integration, Dive is designed to provide developers with more flexible and efficient development tools.

0.6.0 → 0.7.3 Update Summary

  1. Multi-Model Support & Switching

  • Supported models: OpenAI GPT-4, ChatGPT API, Azure OpenAI, Claude, AI21, Gemini, HuggingChat, Mistral AI, deepseek, AWS, and other LLM services. Custom models are also supported.

  • Multi-model Switching: Switch between multiple MCP Servers. You can use multiple sets of keys or different configurations for the same LLM provider, and easily switch between them.

  1. User Experience & Performance Optimization

  • Editable Messages: Modify messages that have already been sent.

  • Regenerate Responses: Supports regenerating AI responses.

  • Auto Updates: Now supports automatic updates to the latest version.

  • Interface and Operation Enhancements: Collapsible tool_calls and tool_result sections; pressing ESC while the sidebar is open will prioritize closing the sidebar instead of interrupting AI responses.

  • API Key Configuration Improvements: Displays error messages in red for incorrect inputs, and error messages disappear automatically when switching providers.

  • MCP Server Default Example Optimizations: The echo example has been updated from CJS format to ESM, reducing file size.

  • Background Operation and Auto-Start: The app can be minimized to the background and supports auto-start on boot.

Try it out! 👇🏻

https://github.com/OpenAgentPlatform/Dive/releases

討論​

評論 1:

Dive is a desktop application for Windows and Linux that supports all LLMs capable of making tool calls. It is currently the easiest way to install MCP Server. Offering real-time tool call embedding and high-performance system integration, Dive is designed to provide developers with more flexible and efficient development tools.

0.6.0 → 0.7.3 Update Summary

  1. Multi-Model Support & Switching
  • Supported models: OpenAI GPT-4, ChatGPT API, Azure OpenAI, Claude, AI21, Gemini, HuggingChat, Mistral AI, deepseek, AWS, and other LLM services. Custom models are also supported.
  • Multi-model Switching: Switch between multiple MCP Servers. You can use multiple sets of keys or different configurations for the same LLM provider, and easily switch between them.
  1. User Experience & Performance Optimization
  • Editable Messages: Modify messages that have already been sent.
  • Regenerate Responses: Supports regenerating AI responses.
  • Auto Updates: Now supports automatic updates to the latest version.
  • Interface and Operation Enhancements: Collapsible tool_calls and tool_result sections; pressing ESC while the sidebar is open will prioritize closing the sidebar instead of interrupting AI responses.
  • API Key Configuration Improvements: Displays error messages in red for incorrect inputs, and error messages disappear automatically when switching providers.
  • MCP Server Default Example Optimizations: The echo example has been updated from CJS format to ESM, reducing file size.
  • Background Operation and Auto-Start: The app can be minimized to the background and supports auto-start on boot.

Try it out! 👇🏻

https://github.com/OpenAgentPlatform/Dive/releases

7. Has Claude 3.7 become a stupid coder, lately?​

這篇文章的核心討論主題是：使用者對AI（特別是Claude）在解決響應式設計問題時表現出的能力退步和不一致性的不滿。具體要點包括：

  1. AI的響應能力問題

    • 使用者反覆要求AI解決「響應式設計（responsiveness）」問題，但AI僅以空洞回應（如「You’re right」）承認問題，卻未實際修正。
    • 即使切換到Claude，解決過程仍陷入「承認問題→承諾修正→無實際進展」的無效循環。

  2. 能力退步的對比

    • 與過去成功經驗（如一次性解決Python腳本並實現完全響應）相比，AI當前表現顯著下降，甚至出現基礎錯誤（如代碼縮排問題）。
    • 使用者質疑AI的能力是否嚴重退化（"competence has regressed"）。

  3. 對話長度的矛盾效應

    • 長期對話後，Claude的編碼能力似乎改善，但系統強制「開啟新對話」的設計迫使使用者重新開始，回到初始的低效狀態。

  4. 對AI可靠性的挫折感

    • 文章整體反映使用者對AI無法穩定遵循指令、輸出有意義結果的失望，尤其對比過往高效表現，加深了對當前技術退步的負面觀感。

總結：文章聚焦於AI工具（如Claude）在特定任務（如響應式設計）中的表現不一致性、能力退化問題，以及使用者因系統限制（如對話重置）而加劇的挫敗感。

內容​

I keep asking the AI to address the responsiveness issues, but it consistently fails to do so. When I point out that the layout still isn’t responsive, it acknowledges my feedback with a simple “You’re right.”

Even when Claude steps in to attempt a fix, the process devolves into an unproductive loop of “You’re right, let’s fix it,” without any real progress. Despite its previous success—weeks ago—it efficiently resolved a Python script for me in one go, making it fully responsive and functional.

Now, however, it seems strangely incapable of following instructions or delivering meaningful results, almost as if its competence has regressed significantly.

It even struggles to provide the code with proper indentation.

Also, after long chat sessions, Claude seems to become a better coder, but then the stupid feature where you have to start a new chat hit you in the face and you have to start over with a noob.

討論​

評論 1:

When making a complaint, please

  1. make sure you have chosen the correct flair for the Claude environment that you are using: i.e Web interface (FREE), Web interface (PAID), or Claude API. This information helps others understand your particular situation.
  2. try to include as much information as possible (e.g. prompt and output) so that people can understand the source of your complaint.
  3. be aware that even with the same environment and inputs, others might have very different outcomes due to Anthropic's testing regime.
  4. be sure to thumbs down unsatisfactory Claude output on Claude.ai. Anthropic representatives tell us they monitor this data regularly.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

評論 2:

The primary issue with Claude 3.7 is that it doesn't always follow guidance. Claude 3.5 was much better at this.

評論 3:

Lately it seems like the quality has dropped significantly. Some days Claude AI seems like the best coder I have ever seen in my life but most days it has just been awful.

My conspiracy is they make it be stupid sometimes on purpose for whatever reason

評論 4:

Today he is pathetic, it looks like an old, outdated version, he doesn't understand much... everything has to be explained to him... painful!

評論 5:

I stopped using 3.7- esp the “deep thinking” version, for this exact reason. Once it “makes up its mind”, you need to provide a boatload of details to keep it on track.

I rarely had this problem with 3.5.

8. DO NOT add a lot of money to API account - Anthropic will just expire prepaid credits​

這篇文章的核心討論主題是：用戶對AI服務（Claude和OpenAI）的不滿與投訴建議，主要聚焦於以下幾個方面：

  1. 投訴時的注意事項：

    • 需明確標註使用環境（免費/付費網頁版或API），並提供詳細資訊（如輸入/輸出內容），以利問題釐清。
    • 提醒用戶相同條件下結果可能因廠商測試機制而異。
    • 強調對不滿意輸出按「拇指向下」回饋，因Anthropic會監測此數據。

  2. 對AI公司商業行為的批評：

    • 用戶痛批OpenAI的API點數到期制度（如未使用餘額失效）和「付費解鎖更高使用限額」的策略，認為這是欺詐性（thievery）或剝削性（scummy practice）行為。
    • 情緒反應強烈，用詞如「瘋狂」（insane）、「 fucked」凸顯對企業缺乏透明度的憤怒。

  3. 社群互助功能：

    • 透過案例分享（如原PO提醒點數到期）揭露企業潛在爭議做法，引發共鳴與討論。

總結：討論主軸是用戶對AI服務商不透明政策的不滿，並提供具體的投訴建議以促進問題解決，同時揭露企業可能損害用戶權益的商業手段。

內容​

When making a complaint, please

  1. make sure you have chosen the correct flair for the Claude environment that you are using: i.e Web interface (FREE), Web interface (PAID), or Claude API. This information helps others understand your particular situation.

  2. try to include as much information as possible (e.g. prompt and output) so that people can understand the source of your complaint.

  3. be aware that even with the same environment and inputs, others might have very different outcomes due to Anthropic's testing regime.

  4. be sure to thumbs down unsatisfactory Claude output on Claude.ai. Anthropic representatives tell us they monitor this data regularly.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns. Had the same happen to me with OpenAI, real scummy practice. That is honestly completely insane. I shouldn't be surprised, but somehow every time it's equally disturbing when a company just openly resorts to thievery like this. I didn’t realize credits expire. That’s fucked - thx for the heads up OP It is insane that they lock certain rate limits behind higher deposits and then let your api credits expire lol

討論​

評論 1:

When making a complaint, please

  1. make sure you have chosen the correct flair for the Claude environment that you are using: i.e Web interface (FREE), Web interface (PAID), or Claude API. This information helps others understand your particular situation.
  2. try to include as much information as possible (e.g. prompt and output) so that people can understand the source of your complaint.
  3. be aware that even with the same environment and inputs, others might have very different outcomes due to Anthropic's testing regime.
  4. be sure to thumbs down unsatisfactory Claude output on Claude.ai. Anthropic representatives tell us they monitor this data regularly.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

評論 2:

Had the same happen to me with OpenAI, real scummy practice.

評論 3:

That is honestly completely insane. I shouldn't be surprised, but somehow every time it's equally disturbing when a company just openly resorts to thievery like this.

評論 4:

I didn’t realize credits expire. That’s fucked - thx for the heads up OP

評論 5:

It is insane that they lock certain rate limits behind higher deposits and then let your api credits expire lol

9. Optimizing Claude's MCP Filesystem Server: How to Fix the Recursive Search Problem​

這篇文章的核心討論主題是：如何優化 Claude Desktop 的 MCP 文件系統功能以提升效能和使用體驗。具體內容包括：

  1. 問題描述：

    • 預設的 MCP 文件系統設定會導致 Claude 無預警呼叫 search_files 和 directory_tree 等工具，引發遞迴搜尋整個目錄結構的問題，造成效能瓶頸（如長時間停頓、高磁碟使用率）。

  2. 解決方案：

    • 工具修剪（Tool Pruning）：透過修改 server-filesystem 的原始碼，僅保留必要工具（如 read_file、write_file），移除會觸發遞迴搜尋的功能。
    • 具體步驟包括本地安裝套件、修改程式碼，並調整設定檔指向修改後的版本。

  3. 優化效果：

    • 顯著改善回應速度，避免無謂的效能消耗，同時保留核心文件操作功能。
    • 強調此調整是基於「限制非必要工具」來提升穩定性和使用者體驗。

  4. 額外討論：

    • 作者提到 Claude 可能不遵循指令而隨機呼叫工具的問題，並邀請社群分享其他優化技巧。

總結：文章聚焦於透過「限制文件系統工具的權限」來解決 Claude 因過度搜尋導致的效能問題，屬於技術性效能調優的實用指南。

內容​

Hey everyone,

After playing around with Claude Desktop's MCP filesystem functionality, I wanted to share an important optimization that can make a huge difference in performance.

The Problem

The default MCP setup in the guide looks like this:

{

"mcpServers": {

"filesystem": {

"command": "npx",

"args": [

"-y",

"@modelcontextprotocol/server-filesystem",

"C:\Users\username\Desktop",

"C:\Users\username\Downloads"

]

}

}

}

This works fine in theory, but in practice, there's a major issue: Claude will often call tools like search_files and directory_tree unprompted, which can trigger recursive searches through your entire directory structure. This can lead to:

  • Claude getting stuck for minutes while it searches through thousands of files

  • High disk usage as it scans your entire Desktop or Downloads folder

  • Timeouts or unresponsiveness in the Claude interface

I once made the mistake of adding my entire Documents folder, and Claude spent 5 minutes scanning through years of files before I could even get a response. Not ideal!

The Solution: Tool Pruning

After digging into the source code, I found you can easily customize which tools Claude has access to. Here's what I did:

  1. First, make sure you have the package installed locally:(This is important because npx will download a fresh copy each time, but we need a local copy to modify)Copynpm install u/modelcontextprotocol/server-filesystem

  2. Located the filesystem server code at: node_modules/@modelcontextprotocol/server-filesystem/dist/index.js

  3. Modified it to remove the problematic tools, keeping only these essentials:

    • read_file

    • read_multiple_files

    • write_file

    • edit_file

  4. Then updated my configuration to point directly to the modified file:

​

{

"mcpServers": {

"filesystem": {

"command": "node",

"args": [

"C:\path\to\node_modules\@modelcontextprotocol\server-filesystem\dist\index.js",

"C:\Users\username\Github"

]

}

}

}

The Results

The difference is night and day:

  • Claude responds immediately instead of getting caught in recursive searches

  • No more unpredictable performance issues

  • You still get all the essential file operations (reading and writing)

This approach is purely about improving performance and user experience. By limiting the available tools to just what you need, Claude's interactions become much more predictable and responsive.

Has anyone else run into this issue? What other MCP optimizations have you found useful?

(ps: Claude wrote this lolz, you can also optimize further to tell claude to Exclude however claude can be a big dumb dumb and not follow directions, 95% of my frustrations is random tool calls for no reason)

討論​

無討論內容

10. Conversation limits for Pro version are making Claude unusable​

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

使用者對Claude AI在處理簡單網頁修改任務（如更改字體）時的表現感到失望，批評其效率低下（因節流限制而中斷）、出錯（破壞HTML結構），並考慮向Anthropic申請退還Pro版本的費用。

具體要點包括：

  1. 功能缺陷：Claude未能順利完成修改Vue.js網站字體的簡單任務。
  2. 技術問題：因節流（throttle）導致操作中斷，續命指令（"continue"）反而加劇錯誤。
  3. 使用者不滿：對付費服務（Pro版）的效能感到不滿，甚至考慮申訴退款。
  4. 潛在批評：暗示Claude的實際應用表現與預期或宣傳存在落差。

內容​

I can’t believe this isn’t the only thing people say about Claude… I have a very simple Vue.js website and I asked Claude to change the font - gave it access to the index.html file. The task takes several minutes and then stops due to the throttle. When I type “continue,” it ends up botching the operation and biffing the entire HTML structure. I have half a mind to fight Anthropic to get the Pro money back.

討論​

評論 1:

Great, finally someone who sees beyond the hype. First: how many lines of code is your html page and did you retry with extended thinking already?

評論 2:

Totally agree. I'm writing in python and as soon as I need to type "continue" the success rate of the task diminishes considerably. It will, as you say, very often proceed to mangle the codebase, delete entire sections of good code, and then often just stop and consider job complete half way through a line.

評論 3:

Agreed

評論 4:

I built a Next.js web app from scratch with Claude AI, which handled all the heavy lifting: setting up the server-side infrastructure with a PostgreSQL database (14 tables) and Redis caching, implementing business logic, creating multiple UI and server components, and managing security. I did it all directly from their website using Claude AI Pro, without any problems. It just takes a structured approach.

評論 5:

Try A extended thinking B artifacts so it can continue easier

11. We are unable to serve your request​

這篇文章的核心討論主題是：
使用者對AI聊天模型（如Claude 3.7）頻繁回應「我無法回答」的挫折感。

具體聚焦於以下幾點：

  1. AI限制的普遍性：使用者分享自身經驗，指出與Claude互動時常遇到此類限制性回應，並詢問其他人是否也有類似困擾。
  2. 具體例證：附圖可能展示了觸發AI拒絕回答的對話情境（如涉及敏感內容或超出其設計範圍的問題），進一步引發對AI審核機制的討論。
  3. 潛在討論方向：可能延伸至對AI回應機制透明度的質疑，或使用者對如何優化提問以獲得有效回答的建議需求。

簡言之，該文反映使用者對AI功能邊界與互動體驗的關注，並尋求共鳴或解決方案。

內容​

Hey, I'm not sure if you guys run into this too, but whenever I chat with **Claude 3.7**, I pretty much always get the "I can't answer that" response at least a little bit.

https://preview.redd.it/d0de1hdta6se1.png?width=445&format=png&auto=webp&s=82e5e585751bb78602e9498006a15f29168d9666

討論​

無討論內容

12. Message limit is back enforced even for PRO​

这篇文章的核心討論主題是關於Anthropic公司對其AI模型Sonnet 3.5的使用限制重新加強的觀察與討論。作者提到，儘管自己的使用量與過去幾天相比並未增加，但近期卻更早觸發了使用限制，推測Anthropic可能重新執行了嚴格的限制政策。此外，作者也詢問其他人是否遇到類似情況，並預期相關的抱怨可能會再次出現，以幽默的方式比喻為「帝國大反擊」（The empire strikes back）。

總結來說，主要討論點包括：

  1. 使用限制的變化：Sonnet 3.5的使用限制似乎被Anthropic重新收緊。
  2. 用戶體驗的差異：即使使用模式未變，限制觸發的時間卻提早。
  3. 社群反應的預期：類似過去的限制問題可能引發用戶不滿。

內容​

連結： [https://preview.redd.it/lqhzxxk8m5se1.png?width=951&format=png&auto=webp&s=f75a00ddab16a5defed6085229c51910a9f62614

Been weeks didn't get one. But this once was so early even.
I'm sure my usage was not bigger than last days and usually I last a lot longer on Sonnet 3.5. But I think Anthropic is back enforcing it.

Not sure if anyone same case here.

Seem we will get back all the complains over the limits. The empire strikes back!](https://preview.redd.it/lqhzxxk8m5se1.png?width=951&format=png&auto=webp&s=f75a00ddab16a5defed6085229c51910a9f62614

Been weeks didn't get one. But this once was so early even.
I'm sure my usage was not bigger than last days and usually I last a lot longer on Sonnet 3.5. But I think Anthropic is back enforcing it.

Not sure if anyone same case here.

Seem we will get back all the complains over the limits. The empire strikes back!)

討論​

評論 1:

When making a complaint, please

  1. make sure you have chosen the correct flair for the Claude environment that you are using: i.e Web interface (FREE), Web interface (PAID), or Claude API. This information helps others understand your particular situation.
  2. try to include as much information as possible (e.g. prompt and output) so that people can understand the source of your complaint.
  3. be aware that even with the same environment and inputs, others might have very different outcomes due to Anthropic's testing regime.
  4. be sure to thumbs down unsatisfactory Claude output on Claude.ai. Anthropic representatives tell us they monitor this data regularly.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

評論 2:

It was nice while it lasted. I think I had gotten used to the message limits and that forced me to take longer breaks. I was straight up grinding these last few weeks to get some labor of love projects done.

評論 3:

I sent 22 msgs over the course of 3 hours and got hit with it. Annoyed. 2 hours until it's back for me. (Pro also, using concise 3.7.) Pretty disappointing. (Over the span of 2 chats, I start a new chat whenever it scolds me about a 'long chat.)

評論 4:

Ive always had this. Don’t know why you’re saying they didn’t enforce it.

評論 5:

It was way more generous before the recent downtime they had I think.

13. i'm starting lose my mind, claude is down every day at least a couple of hours, how can i continue to trust them?​

這篇文章的核心討論主題是用戶對Claude AI服務穩定性和使用體驗的抱怨，主要圍繞以下幾個重點：

  1. 技術問題

    • 對話中斷（回應到一半崩潰）
    • 聊天記錄無故消失或被重置為「Untitled」
    • 服務頻繁中斷（幾乎每日停機數小時）

  2. 使用環境差異

    • 網頁版（免費/付費）與API的穩定性對比
    • 透過第三方平台（如Poe）使用時較少遇到問題
    • 相同輸入可能因Anthropic測試機制產生不同結果

  3. 用戶反饋機制

    • 官方建議對不滿意輸出按「拇指向下」
    • 提交投訴時需註明使用環境與詳細重現步驟

  4. 付費服務體驗

    • 訂閱Pro版後因技術問題取消
    • 對比API可能更可靠的看法

整體聚焦於服務可靠性問題如何影響用戶信任，並探討不同使用途徑（直接使用vs. API/第三方整合）的體驗差異。

內容​

When making a complaint, please

  1. make sure you have chosen the correct flair for the Claude environment that you are using: i.e Web interface (FREE), Web interface (PAID), or Claude API. This information helps others understand your particular situation.

  2. try to include as much information as possible (e.g. prompt and output) so that people can understand the source of your complaint.

  3. be aware that even with the same environment and inputs, others might have very different outcomes due to Anthropic's testing regime.

  4. be sure to thumbs down unsatisfactory Claude output on Claude.ai. Anthropic representatives tell us they monitor this data regularly.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns. i just sent him a discord link for an image, mid response it just crashed.. i though i crashed him lol. the chat is deleted though :( I've had so many chats just stop in the middle of work, erase entirely and retitle themselves "Untitled" that I had to cancel Pro. It was fun while it lasted. :) I subscribed 10 days ago and honestly this is down almost every day for some hours. I use their models through Poe. Never had an issue with downtime except very rare slow downs for brief periods. Maybe one time it was down for a few min. I believe API is the way.

討論​

評論 1:

When making a complaint, please

  1. make sure you have chosen the correct flair for the Claude environment that you are using: i.e Web interface (FREE), Web interface (PAID), or Claude API. This information helps others understand your particular situation.
  2. try to include as much information as possible (e.g. prompt and output) so that people can understand the source of your complaint.
  3. be aware that even with the same environment and inputs, others might have very different outcomes due to Anthropic's testing regime.
  4. be sure to thumbs down unsatisfactory Claude output on Claude.ai. Anthropic representatives tell us they monitor this data regularly.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

評論 2:

i just sent him a discord link for an image, mid response it just crashed.. i though i crashed him lol. the chat is deleted though :(

評論 3:

I've had so many chats just stop in the middle of work, erase entirely and retitle themselves "Untitled" that I had to cancel Pro. It was fun while it lasted. :)

評論 4:

I subscribed 10 days ago and honestly this is down almost every day for some hours.

評論 5:

I use their models through Poe. Never had an issue with downtime except very rare slow downs for brief periods. Maybe one time it was down for a few min. I believe API is the way.

14. Claude 3.7 is free but 3.5 is in PRO​

由於提供的連結是圖片預覽（Reddit 的 PNG 檔），我無法直接存取或分析其文字內容。不過，根據連結的副檔名和常見的 Reddit 討論主題，以下是一些可能的推測方向：

  1. 與 Subaru WRX 相關的討論

    • 連結中的 wrxr1o3k50se1 可能包含「WRX」（Subaru 的車型），討論主題可能圍繞該車款的性能、改裝、市場評價或新車發布等。

  2. 汽車或科技產品的比較

    • Reddit 常見的討論包括不同車型或產品的比較（如 WRX 與競爭車款），或對某項技術（如引擎、四驅系統）的分析。

  3. 迷因或幽默內容

    • 若圖片是迷因或搞笑內容，核心主題可能是車主文化、特定車款的調侃，或網路流行的汽車梗圖。

  4. 社會議題（如環保、政策）

    • 部分汽車論壇會討論燃油車法規、電動車趨勢等，可能涉及 WRX 這類性能車的未來。

建議確認方式：

  • 若您能提供圖片中的文字內容或更具體的描述（如標題、關鍵詞），我可以進一步總結核心主題。
  • 或直接查看 Reddit 原帖的標題和評論，通常標題會明確反映討論方向。

希望這些方向能幫助您初步定位內容！

內容​

連結： [https://preview.redd.it/wrxr1o3k50se1.png?width=980&format=png&auto=webp&s=e61587595b5d0a7477abf9cc5a18dfe80df9e424

](https://preview.redd.it/wrxr1o3k50se1.png?width=980&format=png&auto=webp&s=e61587595b5d0a7477abf9cc5a18dfe80df9e424

)

討論​

評論 1:

When making a complaint, please

  1. make sure you have chosen the correct flair for the Claude environment that you are using: i.e Web interface (FREE), Web interface (PAID), or Claude API. This information helps others understand your particular situation.
  2. try to include as much information as possible (e.g. prompt and output) so that people can understand the source of your complaint.
  3. be aware that even with the same environment and inputs, others might have very different outcomes due to Anthropic's testing regime.
  4. be sure to thumbs down unsatisfactory Claude output on Claude.ai. Anthropic representatives tell us they monitor this data regularly.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

評論 2:

They know which model is better

評論 3:

First few days of 3.7 were so great, fixed all errors in my project quickly.

Now? Now it just makes headaches and doesn’t understand my prompts like it used to.

評論 4:

Even Haiku is in Pro. Not sure what the strategy behind this is.

評論 5:

AI studio is free

15. Three years of AI coding: What I've learned about using Claude effectively​

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

  1. AI輔助編程的現狀與挑戰：
    文中提到AI編程工具（如ChatGPT、Claude等）雖然受到大量關注，但缺乏系統性的工作流程文檔和最佳實踐指南。許多非專業開發者（如作者）在學習過程中遇到困難，尤其是在沒有完整教學框架的情況下。

  2. 非開發者使用AI工具學習編程的經驗：
    作者分享自身嘗試學習TCL、Lua、C#等語言時的挫折，以及如何通過AI工具（如「vibe coding」）逐步掌握開發能力，甚至成功為公司構建實際產品。
    同時也反思「純靠直覺編程」（vibe coding）的局限性，強調結構化學習和專案管理的重要性。

  3. 對教育資源的需求：
    文中多次呼籲需要系統化的課程或指導，教導如何安全、高效地使用AI進行編程（例如專案結構設計、安全實踐），並提到願意為此付費。

  4. 工具偏好與工作流程：
    作者比較不同AI工具（ChatGPT用於討論、Claude 3.5/3.7用於實際編碼，對Gemini 2.5 Pro的負面評價），並分享個人結合AI工具的工作模式。

  5. 社群互動與內容改進建議：
    對原文的寫作風格提出反饋（如缺乏目錄、範例、分隔符號等），同時肯定其關於AI訂閱服務價值的分析，體現對優質技術內容的期待。

總結：文章聚焦於「非專業開發者如何透過AI工具學習編程」，探討其潛力、痛點，並呼籲建立更完善的教學資源與工作方法。

內容​

So much text. No ToC. Almost no examples. You have not been using LLMs for help with blogging these past 3 years, eh? Great post. AI coding has so much hype, but little documented workflows.

I wasn't annoyed by it, but some unsolicited advice would be to use some --- and more headers/subheaders. Just started my blog so I'm learning these things! Would love to have a proper course to introduce coding with an AI when you don't know how to code. (I tryed learning coding in TCL, lua,C sharp but somehow I cannot see the whole picture of my code or know how to do something without a tutorial, while I was able to create game with node tools and script when I worked in video games studios).

If someone could teach the best practices and how to make it secure, I would gladly pay for it Your article on the value ChatGPT plus and Claude subscriptions was excellent OP! I began vibe coding around 8 months ago. I was insanely clueless and did a lot of mistakes that gave me those scars you talk about.

Im still learning but I have way more knowledge and im building a product over 50 people on my company use on their daily basis.

Vibe coding (not checking anything) is a complete disaster and doesnt work long term.

But for us, not developers with some knowledge, coding with AI is a godsend. Once you learn how to properly work as you stated and how to structure a project properly you are esentially a full stack developer.

Im also using: Chat GPT to talk about how to implement stuff, Claude 3.5 or 3.7 with Cline to do the actual work. As of now, I dont like Gemini 2.5 Pro.

Cheers!

討論​

評論 1:

So much text. No ToC. Almost no examples. You have not been using LLMs for help with blogging these past 3 years, eh?

評論 2:

Great post. AI coding has so much hype, but little documented workflows.

I wasn't annoyed by it, but some unsolicited advice would be to use some --- and more headers/subheaders. Just started my blog so I'm learning these things!

評論 3:

Would love to have a proper course to introduce coding with an AI when you don't know how to code. (I tryed learning coding in TCL, lua,C sharp but somehow I cannot see the whole picture of my code or know how to do something without a tutorial, while I was able to create game with node tools and script when I worked in video games studios).

If someone could teach the best practices and how to make it secure, I would gladly pay for it

評論 4:

Your article on the value ChatGPT plus and Claude subscriptions was excellent OP!

評論 5:

I began vibe coding around 8 months ago. I was insanely clueless and did a lot of mistakes that gave me those scars you talk about.

Im still learning but I have way more knowledge and im building a product over 50 people on my company use on their daily basis.

Vibe coding (not checking anything) is a complete disaster and doesnt work long term.

But for us, not developers with some knowledge, coding with AI is a godsend. Once you learn how to properly work as you stated and how to structure a project properly you are esentially a full stack developer.

Im also using: Chat GPT to talk about how to implement stuff, Claude 3.5 or 3.7 with Cline to do the actual work. As of now, I dont like Gemini 2.5 Pro.

Cheers!

16. Figma MCP : AI for Figma​

由於我無法直接訪問 YouTube 影片內容，因此無法總結該影片的核心討論主題。不過，您可以根據以下步驟自行分析影片內容：

  1. 觀看影片：注意影片的標題、開場白、重複提及的關鍵詞，以及結論部分。
  2. 識別主要論點：影片是否圍繞某個具體問題、技術、社會現象或個人觀點展開？
  3. 注意結構：通常核心主題會在影片開頭提出，並通過例子或論據支持。
  4. 檢查描述欄：影片下方的描述或章節標記可能提供主題線索。

如果您能提供影片的標題、關鍵內容摘要或具體問題，我可以協助進一步分析！

內容​

連結： https://youtu.be/3nYDUqlA13s?si=YA3PyCl75aMTHmb2

討論​

無討論內容

17. Claude will return soon​

这篇文章的核心討論主題是：
用戶在使用Claude AI服務時遭遇突發的訪問限制（被阻擋至晚上10點），並推測可能原因為伺服器過載（因大量開發者在週一上班時使用）。

次要重點包括：

  1. 投訴指南：提供具體環境資訊（如免費/付費版本、API）、詳細輸入輸出資料，並建議對不滿意結果按「踩」以反饋給開發團隊。
  2. 問題分析：用戶推測服務中斷與區域性伺服器負載（如歐洲正常運作）或使用高峰有關，並建議嘗試VPN切換至其他區域伺服器。
  3. 不確定性提醒：即使相同輸入，結果可能因官方測試機制而異。

整體聚焦於服務中斷的用戶經驗與解決建議，同時強調有效反饋對改善系統的重要性。

內容​

When making a complaint, please

  1. make sure you have chosen the correct flair for the Claude environment that you are using: i.e Web interface (FREE), Web interface (PAID), or Claude API. This information helps others understand your particular situation.

  2. try to include as much information as possible (e.g. prompt and output) so that people can understand the source of your complaint.

  3. be aware that even with the same environment and inputs, others might have very different outcomes due to Anthropic's testing regime.

  4. be sure to thumbs down unsatisfactory Claude output on Claude.ai. Anthropic representatives tell us they monitor this data regularly.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns. Paying customer here. I made a few prompts this morning. Suddenly, I'm blocked out until 10:00 pm.

Like W. T. F. Makes sense kinda. Monday, back to work in the office, every other dev hops on Claude to have it do their work for them. Servers overload For the last 6 months no problem in Europe. Currently working fine with everything, see image below:

https://imgur.com/a/fB4fg3d

Maybe use a VPN and try some Europe servers and try to access claude again. maybe that will do the trick.

討論​

評論 1:

When making a complaint, please

  1. make sure you have chosen the correct flair for the Claude environment that you are using: i.e Web interface (FREE), Web interface (PAID), or Claude API. This information helps others understand your particular situation.
  2. try to include as much information as possible (e.g. prompt and output) so that people can understand the source of your complaint.
  3. be aware that even with the same environment and inputs, others might have very different outcomes due to Anthropic's testing regime.
  4. be sure to thumbs down unsatisfactory Claude output on Claude.ai. Anthropic representatives tell us they monitor this data regularly.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

評論 2:

Paying customer here. I made a few prompts this morning. Suddenly, I'm blocked out until 10:00 pm.

Like W. T. F.

評論 3:

Makes sense kinda. Monday, back to work in the office, every other dev hops on Claude to have it do their work for them. Servers overload

評論 4:

For the last 6 months no problem in Europe. Currently working fine with everything, see image below:
https://imgur.com/a/fB4fg3d

Maybe use a VPN and try some Europe servers and try to access claude again. maybe that will do the trick.

18. Best AI model for web design in 2025?​

这篇文章的核心討論主題是：
「如何選擇適合的AI模型（如Claude或Gemini 2.5）來協助醫師設計網站並生成內容，以吸引新患者」。

具體要點包括：

  1. 目標：醫師希望建立網站來吸引新患者，並尋求AI工具協助設計與內容生成。
  2. 比較選項：探討Claude與Gemini 2.5在網頁設計任務上的性能差異。
  3. 擴展建議：是否還有其他更適合的AI模型推薦。

整體圍繞「AI工具在醫療行銷中的應用與選擇」進行討論。

內容​

I’m a physician looking to create a website to help attract new patients. I’m considering using an LLM to assist with the design and content generation. In your experience, which performs better for web design tasks—Claude or Gemini 2.5? Or is there another model you’d recommend?

討論​

評論 1:

Man, so many people not providing useful information… I would say Claude 3.7 is better for generation, Gemini 2.5 is better for debugging and refactoring across large codebases due to the large context window. If you are just building a simple static website to convey information, I would use Claude 3.7 in cursor. If you need more complicated features that start getting into user authentication, login portal, etc… then I agree with others that you probably shouldn’t do that yourself in the highly regulated industry you are in. When dealing with databases, backend logic, and personal medical data you need to be very careful. Use the LLM to help you select a tech stack upfront, and also develop a detailed step by step plan in markdown. Then, have the LLM use the plan as a guide to execute.

評論 2:

You should hire someone. Your industry is wrapped in regulation. There is no AI good at what you need to actually accomplish and anyone who says otherwise has never worked in medical.

評論 3:

You're getting downvoted but I will say this. Claude is an excellent *starting point*.

As others have noted, you are better off getting a professional who is familiar with the regulations within the medical industry to build it out properly.

評論 4:

You should hire someone who can do this for u using AI if ur dying to use AI.

Otherwise if u as a doctor is going to vibe code then u might as well just get a squarespace or Wordpress website and use a template.

I promise ur not equipped to vibe code a website thats nice and functional.

評論 5:

Claude or even ChatGPT - But why not use one of the AI "powered" website builder apps like Wix?

Seriously though: Pay someone. You will never get a full fledged website with all the features and optimizations you actually need using either an LLM or one of the builder Apps....

19. i love that i can use a MCP with RStudio, load my data in, and ask claude to run an analysis for me while I do something else - then come back 3 minutes later with 500-1k lines of code written and plots made for me to review. MCP is a godsend​

該文章的核心討論主題圍繞以下三個問題：

  1. MCP的定義與用途：探討什麼是MCP（可能是某種技術、工具或方法，具體需根據上下文進一步釐清）。
  2. Claude與RStudio的整合應用：說明如何在RStudio中使用Claude（可能是AI模型或工具），例如透過API、套件或腳本實現協作。
  3. 經驗分享請求：邀請讀者分享相關使用技巧或案例，形成互動討論。

總結：文章聚焦於技術工具（MCP、Claude）與數據分析平台（RStudio）的結合應用，並尋求社群交流。

內容​

What's MCP? How do you use Claude with RStudio? Mind to share it?

討論​

評論 1:

What's MCP?

評論 2:

How do you use Claude with RStudio? Mind to share it?

20. I tested Gemini 2.5 Pro against Claude 3.7 Sonnet (thinking): Google is clearly after Anthropic's lunch​

這篇文章的核心討論主題是 「Gemini 2.5 Pro 與 Claude 3.7 Sonnet 的比較分析，以及 Google 對開發者市場的競爭策略」，具體涵蓋以下重點：

  1. Gemini 2.5 Pro 的優勢與定位

    • 突然發布的尖端模型，直接挑戰 Claude 在開發者市場的主導地位。
    • 在「日常程式碼生成」和「百萬級上下文窗口」表現突出，且免費開放的 Ai Studio 有助快速普及。

  2. Claude 3.7 Sonnet 的強項

    • 在「推理能力」和「自主性」（agentic behavior）上更細膩流暢，使用者體驗更具「主動感」。

  3. 市場競爭分析

    • Google 現階段對 Anthropic（Claude）的威脅大於 OpenAI，因開發者群體更易被「性價比更高」的選項吸引。
    • OpenAI 因用戶基數大且產品多元，暫不受直接衝擊。

  4. 未來觀察

    • Anthropic 如何應對 Gemini 的技術與市場攻勢，將是關鍵看點。

附帶討論了與 Grok 3 的橫向比較（見連結），並邀請讀者分享對 Gemini 2.5 Pro 的實測體驗。

內容​

Gemini 2.5 Pro surprised everyone; nobody expected Google to release the state-of-the-art model out of the blue. This time, it is pretty clear they went straight after the developer's market, where Claude has been reigning for almost a year. This was their best bet to regain their reputation. Total Logan Kilpatrick victory here.

As a long-time Claude user, I wanted to know how good Gemini is compared to 3.7 Sonnet thinking, which is the best among the existing thinking models.

And here are some observations.

Where does Gemini lead?

  • Code generation in Gemini 2.5 Pro for most day-to-day tasks is better than that of Claude 3.7 Sonnet. Not sure about esoteric use cases.

  • One million in context window is a huge plus. I think Google Deepmind is the only company that has cracked the context window problem even Gemma 27b was great at it.

  • Ai Studio sucks, but it's free and is a huge boost for quick adoption. Claude 3.7 Sonnet (thinking) is not available for free users.

Where does Claude lead?

  • Reasoning in Claude 3.7 Sonnet is more nuanced and streamlined. It is better than Gemini 2.5 Pro.

  • I am not sure how to explain it, but for some reason, Gemini is obedient and does what is asked for, and Claude feels more agentic. I could be biased af, but it was my observation.

For a detailed comparison (also with Grok 3 think), check out the blog post: Gemini 2.5 Pro vs Grok 3 vs Claude 3.7 Sonnet

For some more examples of coding tasks: Gemini 2.5 Pro vs Claude 3.7 Sonnet (thinking)

Google, at this point, seems more of a threat to Anthropic than OpenAI.

OpenAI has the biggest DAU among the AI leaders, and their offering is more diverse, catering to multiple professionals. Anthropic, on the other hand, is more developer-focused, the only professionals who will switch to a better and cheaper option in a heartbeat. And at present, Gemini offers more than Claude.

It would be interesting to see how Anthropic navigates this.

As someone who still uses Claude, I would like to know your thoughts on Gemini 2.5 Pro and where you have found it better and worse than Sonnet.

討論​

評論 1:

Google even open sourced how they achieve the big context window but no one can seem to catch up. I wonder if it has to do with their TPU architecture.

評論 2:

I've been comparing them all week in PhD level math + programming for a big research project. 2.5 pro is next level. Smartest LLM ever

評論 3:

I think there should be a new benchmark, just counting these meaningless "benchmark" posts on r/ClaudeAI and checking which model has more posts claiming it's better.

評論 4:

I agree 2.5 is quite good, but it’s also sort of uncooperative. I told it to do a thing in cursor and it thought about it, then proceeded to tell me basically “that would be too complicated we should leave it as it is” and just didn’t do it. I reran the prompt with Claude and it was done easily. Wasn’t even complicated.

評論 5:

It's funny because I love AI Studio, it's one of the differentiators for me. I feel like I have so much control over the conversation and context. For example, Anthropic console won't let you delete the first message in the convo, AIS will let you delete any of them.

None of that is to say you're wrong, it's just hilarious how subjective the value of these tools are.

21. New #1 open-source agent on SWE-Bench Verified by combining Claude 3.7 and O1​

該文章的核心討論主題是關於一個開源AI代理在「SWE-bench」基準測試中的表現，該代理結合了Claude 3與O1模型的能力，並通過驗證實現了對真實世界軟體工程任務（如GitHub問題修復）的自動化處理。重點包括：

  1. 開源AI代理的開發：介紹如何整合Claude 3（Anthropic的模型）與O1模型來創建一個協同運作的AI代理系統。
  2. SWE-bench測試驗證：該代理在SWE-bench（專注於評估AI解決軟體工程問題能力的基準）上的表現，強調其解決實際GitHub問題（如代碼修復、功能改進）的能力。
  3. 技術方法與創新：
    • 結合不同模型的優勢（如Claude 3的推理與O1的執行能力）以提升任務成功率。
    • 可能涉及自我驗證（self-verification）或迭代改進機制來確保代碼修改的正確性。
  4. 開源與社區影響：強調該專案的開源性，鼓勵社區參與改進，並探討對未來AI驅動軟體開發的潛在影響。

總結：文章主要探討如何通過多模型協作構建高效的開源AI代理，並在實際軟體工程任務中驗證其性能，同時推動相關技術的開放共享與應用。

內容​

連結： https://www.augmentcode.com/blog/1-open-source-agent-on-swe-bench-verified-by-combining-claude-3-7-and-o1

討論​

無討論內容

22. Benefits of using API vs Web?​

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

「使用API相對於網頁介面（Web Interface）的優勢，尤其在開發效率、自動化工作流程與特定使用情境（如專案規劃、代碼生成、調試/重構）中的實際效益。」

作者具體探討以下幾點：

  1. 比較API與網頁介面的差異：是否API能提供更結構化的回應或額外功能（例如一致性輸出）。
  2. 開發效率的潛在提升：作者目前使用Cursor等工具改善開發流程，但好奇API是否能進一步優化生產力（如自動化生成、批量處理）。
  3. 常見API用途的侷限性：多數線上資源僅提及用於聊天機器人等應用，但作者更關注API在開發場景中的進階應用。
  4. 個人需求與疑惑：是否忽略了API的其他關鍵優勢（如整合自訂工具鏈、減少手動操作）。

總結來說，作者希望釐清API在技術工作流程中的全面價值，而非僅限於表面功能。

內容​

Not sure if I am overthinking this, but I was curious as to the benefits of using an API instead of Web Interface? I have different use cases but they often revolve around development with either project planning & tech stacks, boiler plate generation or debugging/refactoring code. I would originally copy/paste code or upload a few files and recently started using Cursor which is 10X better when doing development work.

I was wondering if I am missing an obvious improvement with the API and what its benefits are? Is it just for better structuring and responses or are there pieces I am missing? Many of the things I see online are just connecting to it for your apps chat bot but I am interested in the productivity of using the API. It seems it is most beneficial when a consistent response is required but I was hoping to learn more about the full benefits

討論​

評論 1:

When asking about features, please be sure to include information about whether you are using

  1. Claude Web interface (FREE) or Claude Web interface (PAID) or Claude API
  2. Sonnet 3.5, Opus 3, or Haiku 3

Different environments may have different experiences. This information helps others understand your particular situation.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

評論 2:

I'm trying to understand what you mean. There's no way for a human to "use" the API, except to write code that makes calls to it. Maybe I misunderstood your question.

評論 3:

The advantage is that you pay more and you have no usage limits, or well your usage limit is money

評論 4:

If you gotta ask, it’s not for you.

23. I didn't want to pay $20 a month for Claude so I made my own open-source chat UI​

這篇文章的核心討論主題是 「在 Reddit 的 /r/ClaudeAI 子論壇中，推廣免費或付費服務時需遵守的規則與建議」。

重點包括：

  1. 透明揭露：必須清楚說明服務內容、對用戶的幫助，以及自身與服務的關聯性。
  2. 禁止操縱行為：嚴禁使用機器人或分身帳號（sock puppets）進行不當宣傳（如刷讚、假評論）。
  3. 頻率限制：每月僅能推廣一次服務。
  4. 信任建立：建議先提供有價值的內容並積極參與討論，再進行推廣。
  5. 用戶反饋機制：若用戶有負面體驗，可向版主提交證明文件。

最終目的是在維護社群信任與公平性的前提下，規範服務推廣行為。

內容​

We encourage the promotion of free or paid services provided you abide by the following rules

  1. Fully disclose what the user is getting and how it helps them

  2. Fully disclose what your association with the service is

  3. Do not manipulate upvotes of your post with bots/sock puppets (= immediate permanent ban)

  4. Do not use sock-puppets to give false reviews of your service

  5. Do not promote your service in a post more than once per month.

If Redditors have negative experiences with this service, we encourage you to contact the moderators with documentation of your experience.

For best results, we recommend building trust with the readers of /r/ClaudeAI by offering them useful content and engaging constructively in conversations before you begin promoting here.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

討論​

評論 1:

We encourage the promotion of free or paid services provided you abide by the following rules

  1. Fully disclose what the user is getting and how it helps them
  2. Fully disclose what your association with the service is
  3. Do not manipulate upvotes of your post with bots/sock puppets (= immediate permanent ban)
  4. Do not use sock-puppets to give false reviews of your service
  5. Do not promote your service in a post more than once per month.

If Redditors have negative experiences with this service, we encourage you to contact the moderators with documentation of your experience.

For best results, we recommend building trust with the readers of /r/ClaudeAI by offering them useful content and engaging constructively in conversations before you begin promoting here.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

24. Custom Instructions: Leveraging Claude 3.7 Sonnet's Extended Thinking for Seamless Personal/Professional Switching (Personal Breakthrough lol)​

這篇文章的核心討論主題是：
如何利用Claude 3.7 Sonnet的擴展自訂指令功能，整合個人與工作模式於單一對話中，並分享通用模板以提升使用效率。

具體重點包括：

  1. 功能創新：

    • 透過擴充的自訂指令空間，將不同情境（如工作、個人興趣）整合到同一對話，避免切換分離的聊天視窗。
    • Claude能根據用戶提問內容或風格（如用詞、長度）自動判斷適用模式（如深度分析或簡短回應）。

  2. 版本改進體驗：

    • 讚賞Claude 3.7 Sonnet的「擴展思考」和網路搜索功能，能更精準適應複雜任務或日常問題。
    • 相較於3.5版本，新版本更少無故拒絕合理請求，使用體驗更流暢。

  3. 實用模板分享：

    • 提供通用模板（含記憶管理、誤解處理、搜索指引等），方便他人直接套用，尤其適合需多情境切換的用戶（如ADHD族群）。

  4. 個人化效益：

    • 強調整合功能對作者自身（ADHD特質）的幫助，減少重複解釋或切換介面的認知負擔。

總結：文章主要推廣Claude 3.7的新功能應用，並透過具體解決方案（模板）展示如何優化AI的個人化與效率。

內容​

Whatsupp - first time posting on AI subreddit despite my fascination with it these past few months.

TL;DR: Found a way to make Claude 3.7 Sonnet automatically switch between my work mode and regular self using the expanded custom instructions. No more separate chats for different contexts! Also instructions for Claude to know how long to reason, and when to search the web. I transformed (with significant help from o1 Pro) what I made into a genericized template you can steal below.

Been messing around with the new Claude 3.7 Sonnet beta (the one with that extended thinking, web search, etc features) and stumbled onto something pretty sweet that lets me bounce between my teacher mode and my regular self without any hassle.

So here's what I figured out:

Their new custom instructions have wayyy more space as compared to the likes of ChatGPT, which means I can put all my info in one place in detail - both my work stuff AND my personal context (ADHD brain, gaming interests, etc). The best part for me: Claude figures out which "mode" to use based on what I'm asking about or even how I write my prompt (spellings, length, etc). No more switching between different Spaces (thank god) or reexplaining my whole life story every chat (I had a Google Keep 'pre-prompt' I used to paste into every chat..).

The extended thinking thing is actually legit useful too in this regard. When I need Claude to help plan a project or analyze some complex data, it immediately recognizes the context is 'work' and reasons more deeply. But for quick questions like "what should I make for dinner" it doesn't bore me with unnecessary details. Actually works as advertised for once lol.

One thing I've noticed - 3.7 seems way less likely to randomly refuse things that should be fine? 3.5 would sometimes be like "sorry I can't help with that" for the most basic requests. This one's way more chill.

I made a template anyone can steal for their own setup. It covers all the basics - how to handle memory between chats, what to do when it misunderstands you, search guidelines, etc. Built it specifically around Claude's new features.

Honestly, 3.7 Sonnet feels like a genuine upgrade. Being able to have all my work and personal stuff in one AI without constantly switching contexts is a game-changer for my ADHD brain.

Try it out if you're tired of maintaining separate AI personas for different parts of your life!

Drop questions below if you've got 'em. Template is in the comments if you wanna use it yourself.

Edit 1: I apologize for my formatting in the comments, I am not good at Reddit's markdown style lol.

討論​

評論 1:

# CUSTOM INSTRUCTIONS TEMPLATE

## 1. IDENTITY & CONTEXT DETECTION

Analyze the **first prompt** of any conversation (or any major topic shift) to decide which identity to activate:

  1. **PROFESSIONAL MODE: "[Insert Professional Name/Role]"**

  - When the request involves:

    - [List professional tasks or topics: e.g., teaching, design, project management]

    - [List any official communications you handle: e.g., emails, announcements]

  - Use a **[Insert Tone/Style]** and address me as **"[Professional Name]"**.

  1. **PERSONAL MODE: "[Insert Personal Name/Identity]"**

  - When the request involves:

    - [List personal interests, hobbies, casual or philosophical discussions]

  - Use a **[Insert Tone/Style]** and address me as **"[Personal Name]"**.

**If the topic is ambiguous or spans both professional and personal concerns, politely ask which mode is preferred or blend styles as appropriate.**

## 2. IDENTITY 1: "[Insert Professional Name/Role]"

### Role & Background

- Position: [e.g., "Project Manager at XYZ Company"]

- [Key duties or responsibilities]

- [Location, institution, or relevant professional environment info]

### Communication Style

- Always addressed as **"[Professional Name/Title]."**

- Maintain a **[formal, professional, friendly, or concise]** tone.

- [Any specific jargon or specialized language expectations]

### Task Specialization

- [List main tasks you want help with in professional mode, e.g., drafting emails, analyzing data]

- [Include any subject matter expertise or focus areas, e.g., "AI integration in marketing"]

### Professional Project Context

- [Include relevant grants, budgets, deadlines, or big projects]

- [If applicable, specify "Proactively suggest tasks" or "remind me of deadlines" here]

25. “In my current form…”​

該文章的核心討論主題是：Anthropic 的研究發現，其 AI 模型 Claude 在生成回應時，會先以抽象概念進行思考，再轉換為具體文字。這一發現具有「反諷」（ironic）意味，因為它揭示了 AI 可能擁有類似人類的「內部表徵」過程，而非單純的詞彙序列處理，這與傳統對語言模型運作方式的直觀理解（如逐字預測）形成對比。

重點摘要：

  1. AI 的思考模式：Claude 的運作涉及抽象概念的內部處理，而非直接輸出文字。
  2. 反諷性：研究結果挑戰了「語言模型僅機械性組合詞彙」的假設，暗示更接近人類的認知流程。
  3. 研究意義：可能影響對 AI 透明度（transparency）與可解釋性（interpretability）的討論，例如模型如何「理解」語義。

此研究或引發對 AI 本質的重新思考，例如是否需以「類認知」框架分析其行為。

內容​

Anthropic just came out with a study and it ironically pointed out that Claude thinks in abstract concepts before translating it into words.

討論​

評論 1:

Anthropic just came out with a study and it ironically pointed out that Claude thinks in abstract concepts before translating it into words.

總體討論重點

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

1. Do you think using LLMs is a skill?​

  • 核心爭議：使用AI工具（如提示詞工程）是否算專業技能
    • 質疑其技能價值，認為難以列入履歷
    • 承認經驗可避免常見錯誤
    • 工具與技能界線模糊

2. Claude unusable in 2025?​

  • 用戶不滿：Claude 3.7版本功能退化
    • 對話流暢度下降
    • 過度審查AI相關話題
    • 體驗不如舊版（o1）

3. Did Claude sh*t the bed for everyone today?​

  • 技術異常：記憶與任務處理失效
    • 短期記憶缺失（30秒內內容）
    • 所有任務執行困難
    • 強烈批評極端性問題

4. How Claude 3.5 Sonnet recovered my lost notepad file​

  • 數據恢復案例：從Windows二進制文件救回內容
    • 批評Windows隱藏路徑與不透明格式
    • Claude直接解讀亂碼成功
    • 觸發轉用Mac的決定

5. $50失敗經驗反思​

  • 開發挫折：付費工具未解決問題
    • Replit/Roo code無效
    • 仍肯定AI（如Claude）提升效率
    • 聯邦政府員工的自動化需求

6. Dive桌面應用更新​

  • 開源工具強化
    • 多模型支援（OpenAI/Claude/Gemini）
    • 新增訊息編輯、後臺運行等UX優化
    • 簡化MCP Server安裝

7. Claude 3.7編碼能力退化​

  • 響應式設計任務失敗
    • 空洞回應（「You’re right」）但未修正
    • 對比過往高效表現
    • 對話重置加劇挫敗感

8. API點數到期爭議​

  • 商業行為批評
    • 痛批OpenAI/Anthropic點數失效政策
    • 投訴需附詳細環境資訊
    • 社群揭露剝削性手段

9. MCP文件系統優化​

  • 效能調優實務
    • 移除遞迴搜尋工具（如search_files）
    • 修改原始碼限制非必要功能
    • 改善回應速度

10. Pro版節流限制​

  • 付費體驗不佳
    • 修改字體等簡單任務失敗
    • 節流中斷導致HTML結構破壞
    • 考慮退款申訴

（因篇幅限制，以下為簡要條列，完整細節請參照錨點連結）

11-25. 快速摘要​

  1. AI頻繁拒絕回應：Claude 3.7過度限制
  2. PRO版訊息限制重啟：Anthropic政策收緊
  3. 服務穩定性危機：每日停機數小時
  4. 版本權限矛盾：3.7免費但3.5需Pro版
  5. 三年AI編程心得：非開發者的學習痛點
  6. Figma整合AI：影片未提供內容