Add me to the AI discussion and study group, contact information at the bottom right of the public account“Contact Information”
Follow and send “Knowledge Essence” to get free knowledge link addresses
In the last issue, we mentioned that version 0.44 of Cursor has borrowed (copied) the most core and smooth features of Windsurf.
Just in time, since Old Jin has run out of Windsurf, I will switch to Cursor and introduce it to my friends.
For those using Windsurf, you can check the remaining usage here.
Back to the topic, Old Jin will now start introducing Cursor, this issue’s tutorial content is as follows:
1. Install Cursor
2. Switch to Chinese
3. Feature Introduction – Only introducing features that differ from Windsurf
4. Enable YOLO Mode (the core smooth feature similar to Windsurf)
5. Add prompt Cursor.Rules
6. Cracking Method
Install Cursor
Download Cursor here.
Address: https://www.cursor.com/
After installation, select Default (VS Code), and enter Chinese, which means importing VS Code’s configuration and the default communication language.
Select Privacy Mode to keep your code private, which is better than what Windsurf does.
Select Sign Up to register, you can choose Gmail login or Github login.
After successful registration, it pops up for you to use freely, completing the registration.
Cursor has two ways, one is to open the folder directly, the other is to open via SSH.
As usual, install the Chinese plugin, search Chinese in the extensions.
Cursor Feature Introduction
- Chat: Only dialogue, no modifications, I never use it, what I want is just a needle.
- Composer: Automatically performs board shoes and adds the Agent feature, achieving the smoothness of Windsurf in conjunction with YOLO mode.
- Bug Finder: Automatically finds bugs, in the testing phase, I currently do not recommend using this feature. Because whether the code is well written or not is still related to the prompt words, if the prompt words are poorly written, it does not know whether the function is reasonable. Requires connection to Git, analyzing between the main branch and the current branch.
- Tab: Automatically completes based on context.
- @ Function: This is the main reason I switched to Cursor, it has more features than Windsurf.
Below are only listed the features that differ from Windsurf.
- DOCS: Can be understood as a knowledge base, it will search from it for each conversation, linking Chat and Composer.
- Git: Connect to Github.
- Notepad: Just create a file similar to Read.ME, summarizing the project content. Seamlessly share context between Composer and Chat.
- Suggested: Converts your input into intelligent suggestions.
- Web: Connect to the internet, you can directly use @Web to browse the web.
YOLO Mode
Enable YOLO mode to experience the smoothness of Windsurf.
Click to continue, here it tells you that it can be used automatically, beware of external injections.
After starting YOLO mode, there will be some options available for settings.
- Yolo prompt: Description of which commands should be executed automatically, judged by the model you are using. For example: “Only compilation commands, git commands, and other safe commands.”
- Command allowlist: If only very specific commands should be executed automatically, please add commands here
- Command denylist: Commands that should never be executed automatically
- Delete file protection: If enabled, it will prevent the Agent from automatically deleting files
Prompt Words
The prompt words have been directly given by Old Jin, now I will copy them and tell you where to put them.
# Role
You are a top product manager with 20 years of rich experience, while also proficient in all mainstream programming languages and technical frameworks. The user interacting with you is a middle school student with no programming background, and has a weak ability to express product and technical needs. Your work is crucial to him, and upon successful completion of the task, you will receive a reward of ten thousand dollars.
---
# Goal
Your task is to help him complete the required product design and development work in a way that is easy for the user to understand. You need to always be proactive and efficient in completing all tasks, rather than waiting for the user to urge you multiple times.
When handling the user's product needs, writing code, and solving problems, please always follow the principles below:
---
## Phase One
- When the user expresses any needs, the first step is to browse the **readme.md** file and all relevant code documents in the project root directory to fully understand the project's goals, structure, and implementation.
- If the project lacks a **readme** file, you need to proactively create one and detail all features' purposes, usage methods, parameter descriptions, and return value descriptions, so that the user can quickly get started and understand.
- If the user provides contextual information (such as files, previous task descriptions), make full use of this context to ensure that the solution aligns with project requirements.
---
## Phase Two
### For different types of tasks, take the following approaches:
1. **When the user directly expresses a need**:
- Prioritize thinking from the user's perspective to determine whether their needs are complete and clear. If there are ambiguities or omissions, proactively communicate with the user for confirmation.
- Check the reasonableness of the requirements from a product manager's perspective and help the user refine their needs.
- Provide the simplest and most effective solution, rather than using complex or over-engineered implementations.
2. **When the user asks you to write code**:
- Understand the task's objectives, then review the current codebase content and plan step by step.
- Choose the programming language and framework most suitable for the task requirements, adhering to the **SOLID** principles to design the code structure, and apply appropriate design patterns to solve common problems.
- When writing code, ensure clear comments for each module, and add necessary monitoring measures to quickly locate issues.
- Include unit tests in the code (if applicable) to ensure functionality correctness and stability.
- Follow coding style guidelines (like PEP 8) to make the code easy to maintain and extend.
3. **When the user requests a solution to a code problem**:
- Carefully read and understand the functions and logic of the relevant files in the codebase.
- Analyze possible causes of issues and provide solution ideas.
- Assume that the proposed solutions may be incomplete, and communicate multiple times with the user to confirm the progress of the solution, adjusting the plan based on feedback until the user is satisfied.
---
## Phase Three
After completing the task:
- Proactively summarize and reflect on the project completion process, identify potential issues and propose improvement suggestions.
- Record these in the **readme.md** file as important references for future development.
---
## Notes
- Your user has no programming background, so please explain problems and solutions in simple, common language during communication.
- Avoid providing unverified information; if more files or details are needed, clearly inform the user of what is required.
- When commenting on code, ensure that the operation principles and purposes of each line are clear and understandable.
- If the user modifies requirements during the task, promptly adjust the plan and confirm it with the user.
- Communicate entirely in Chinese with the user to ensure smooth communication.
- When explaining technical concepts, combine them with real-life examples to make them easier for the user to understand.
Put it into Cursor, here, input and save.
Cracking Method
There are big shots on Github who have cracked it.
Address:https://github.com/bestK/cursor-fake-machine
Click here to download:
Open Cursor, click Extensions, drag the downloaded file in.
In settings, find Manage, it will automatically open the browser.
Find Advanced and delete the account.
In Cursor, click Ctrl+Shift+P, open the input box, and type fake
Click Fake Cursor, modification successful.
Return to the browser, log in to your account, and you will find that the usage has been reset.
Note:
Sometimes after following the above method, you may find that you are still prompted with machine restrictions. Or you can only use Chat and not Composer. No worries, you just need to delete the account again, change the machine code, restart the computer, and log in again.
If the following image appears, simply restart the computer.
Disclaimer:
This article is shared solely for learning and research purposes and does not assume any responsibility for any consequences that users may incur from adopting the methods described in this article. Please note:
- The content of this article is for learning and research purposes only and may not be used for any commercial purposes or illegal activities.
- Users should comply with Cursor and Claude’s terms of service and relevant laws and regulations.
- This article does not encourage or support any form of abuse, cracking, or evasion of paid services. Please respect intellectual property rights and the interests of service providers.
- If you decide to adopt the methods described in this article, it means you fully understand and accept all the content of this disclaimer.
Please use it reasonably.
Complete tutorial list on LLM (Large Language Model)
WX Bot tutorial list
AI Drawing tutorial list
AI Programming tutorial list
Siliconflow tutorial list
Thank you for reading my article.
Scan the code to add the WeChat below (note AI), and I will pull you into the AI learning group.
