🧙♀️ Field Expansion: Advanced Coding AI 1/n Origin: After the astonishing rise of intelligent coding assistants like Cursor and Windsurf, claims like "Noobs with zero basics can build an app in a day," "Front-end is dead," and "Everyone is a programmer" have been constantly on everyone's nerves. Controversy and doubts ensue, a truly boring daily routine. So, is it possible that everyone's arguing about the wrong thing? Why use programming tools for programming? Beyond the pre-defined boundaries, there's a vast new world. I decided to use "personalized, long-form interpretation guides" to spark discussion and explore even more fascinating possibilities. 🔮 Example: Using four "continues," distill a professional, illustrated report (pictured). 📝 Materials: Mr. Fu Peng's "HSBC Private Wealth Planning" 🔧 Tools: Windsurf Design Methodology⬇️
2/n Thoughts: The original document is a whopping 34,000 words long. Is it enough to just throw it all to the AI? Of course, you can. For example, using an LLM like Gemini, which excels at processing long texts, usually yields acceptable results, but it's a very random average—not what I'm looking for. 1. Choose the right tool: First, let's deconstruct Cursor-like AI. It's essentially "model + interaction," with efficient RAG (search enhancement) and network supplementation. Therefore, it's perfectly acceptable to treat the original document as a "knowledge base" and extract it with the tool's LLM. 2. Migrate to a usable pipeline: We have a small group for "Cursor Programming," where we frequently exchange the latest "best practices." The shared approaches we come up with are extremely valuable. Among these, a standardized build process (SOP) based on the product PRD is a magic formula for turning ideas into reality. State your requirements clearly, and everything will fall into place!
3/n Design: 1. Requirements Document: What do I want? First, read the entire document manually—even without AI, I know roughly what I want. Using this as a supportive tool, I can tell directly from the framework-based development process whether I've truly "thought through" the entire text or whether I'm just making up nonsense. This is how accuracy and quality are guaranteed. Bring out the document https://t.co/xhE0jqDmqe (see Figure 1 below), draw a milestone path, and draw the bow! 2. User Profile: Who am I? "What do I want?" What does the "I" in front of it mean? Personalized guidance. Go to the settings of ChatGPT or Claude, and look for the part about telling the model "About Me." That's what you do. The method is very simple: create a document and "quantify" yourself. Refer to: > [Who am I?] ... 3. Financial Information: What additional dimensions should be considered? This section is an extended dimension extracted from the user portrait and is part of the enhanced design. The raw material topic is wealth planning, so it is just a good opportunity for targeted optimization. Investment advice, risk preferences, asset allocation structure... these can all be written in general. Of course, the vision does not have to be limited here, and can be extended to various industries and roles. You can write about "how to go in the second half of your career", "business thinking", and "entrepreneurship difficulties". Just list a few points and you're done. The core principle is: clarity is better than verbosity. 4. Writing style: How to write? You can list the basic materials, but the output cannot be messy. Put the writing style used for Claude (see Figure 2 below) into a folder in the form of a document, and you're done! For details, please refer to my recent sharing.
4/n output: The arrow is "enchanted". The first arrow is shot with a full bow: read the requirements, start to interpret this arrow, and only take the framework. By the way, I will aim for the next rake. If it deviates, calibrate the posture through the requirements document. 4 arrows fired in succession: all "continue". There are only two ways to do it here: Output → Review → Continue to discuss → Reach a new milestone Output → Review → Reach a new milestone → Continue to output. The most important one is the result of the first "continue". The "requirements document" is used to correct the direction and posture. 📝 For output: It is recommended to press .md by default, that is, Markdown-tagged documents. The editor can render them into beautiful documents and charts. Cursor AI, Windsurf, and VS Code, which are designed based on VS Code, can do this. Adults don't make choices, I want them all.
5/n Unlimited Firepower: The end of the road is where you're no longer willing to go. After receiving the complete summary, you can further visualize these documents, transforming them into rich and colorful materials to guide decision-making and initiate sharing. Or, you can continue the discussion in depth. For example, in the following example, "Should I pay off my mortgage early?" With this complete design, the raw materials and production lines are all in place, legally exploiting the silicon-based guys 24/7, you say: Is this excessive? Where is the law? Are you here to play?
6/n Quick Start: 1. Download Windsurf or Cursor. 2. Create a new folder. Treat each topic as a project, one folder per project, and establish a structure. 3. Add your materials: documents, multimedia, and anything else. 4. State your needs. Simple questions should be addressed briefly. Complex questions should be addressed in a PRD document. What code? It's okay if you forget. 😏
7/n Graphics and Text: Use auxiliary tools to create a good reading experience and turn the md document full of symbols into: 1. Rich Mermaid charts: Markdown Preview Mermaid Support 2. Interactive mind map: Markmap Setting method: Plugin → Search [Plugin Name] → Install and activate it 🎉
When working on a project using this all-purpose SOP, MD documents account for a significant portion of the project. They are crucial for clarifying requirements and accumulating data that can't be purchased. Those who understand will understand.
