Founder of Baixing.com: My Fourteen Claude Code Usage Experiences

链捕手Published on 2026-06-08Last updated on 2026-06-08

Abstract

Founder of Baixing.com Shares 14 Personal Tips for Using Claude Code The author outlines his personal, non-universal strategies for maximizing Claude Code. Key points include: focusing deeply on one primary tool (Claude Code) rather than constant comparison; mastering essential shortcuts for the editor and command line; utilizing voice input like HoldSpeak; starting projects with a structured PROJECT.md file; defaulting to Claude agents for most tasks; and leveraging integrations with GitHub and Cloudflare for build, deployment, and infrastructure. He emphasizes a clear separation between human and machine work: manually maintain a core CLAUDE.md file, and understand AI-generated content by asking the AI, not reading its raw code. Efficient communication involves dragging files (screenshots, audio, documents) directly into the interface. For knowledge management, he recommends a centralized, Git-synced memory system based on ~/.claude/CLAUDE.md to ensure permanence and avoid scattered project memories. Other practices include writing and continuously refining "Skills," using the expensive but reliable ultracode for complex dynamic workflows, and employing Git documentation as handoff points between agents. The overarching philosophy is to treat Claude Code like a horse (or a person) with its own pathfinding abilities—setting goals and boundaries rather than micromanaging every turn.

Author: Wang Jianshuo

A simple record of my experiences with Claude Code so far, purely personal exploration, not necessarily applicable to everyone.

1. Stick to one tool and use it heavily. I use Claude Code. I don't necessarily think it's better than Codex, but the ROI of comparing tools may not be high, even though talking about the differences in detail gives a false sense of achievement.

2. Remember the most important keyboard shortcuts. Control+G to open the editor, helpful for writing longer content; Control+A, Control+E, Control+U—these are very practical shortcuts for quickly moving the cursor in the command line. Although not new to the AI era, they are as important as Control+C and Control+V when using.

3. Use voice input. HoldSpeak is very helpful.

4. Start a project by writing a PROJECT.md, using a structured method to write down everything you think of at once.

5. Claude agents are the default mode.

6. Claude Code, github.com, and cloudflare.com are a perfect match. Hand over the build process, release process, and all domain-related operations to the infrastructure.

7. Separate what is written by humans and what is written by machines. Manually maintain the core CLAUDE.md. Don't read the .md files or code written by Claude Code. Let machines do machine things, humans do human things. Understand what AI writes by asking the AI; don't look at the source code.

8. Drag and drop files into the Claude Code window—audio, video, documents, screenshots. If you can't explain something clearly, use Command+Shift+5 to take a screenshot and drag it over—fastest method.

9. Reconstruct the memory system. Centered on ~/.claude/CLAUDE.md, categorize and reference multiple memory files. Require not using the project's memory, and place all memory files in git, synchronized to GitHub (private). This way, your memory is permanent and cumulative, not scattered across each project.

10. Write Skills, and at the end of each work session, ask Claude to "precipitate what was learned into Skills"—this can be done automatically.

11. Whenever possible, for complex tasks, use ultracode to trigger dynamic workflows. Although expensive and slow, the results are guaranteed.

12. Accumulate Skills along the way, and continuously refactor Skills. Skills need to be placed in git.

13. Use git documentation as the output of the previous task and the input of the next task. Let agents have clear handover documents, without relying on context for connection.

14. Treat Claude Code as a horse (or a person), not as a car. A car turns under your direct command, a horse has its own ideas; we only need to set goals and boundaries. Its autonomous pathfinding characteristic is a feature, not a bug.

Does anyone have more to add?

Related Questions

QWhat is the most important shortcut mentioned by the author when using Claude Code?

AControl+G to open the editor, which helps in writing longer content. Also, shortcuts like Control+A, Control+E, and Control+U for quickly moving the cursor in the command line.

QHow should one handle the code and documentation written by AI versus by humans according to the article?

ASeparate human-written and machine-written content. Manually maintain the core CLAUDE.md file. For content written by Claude Code, one should understand it by asking the AI and not by reading the source code directly.

QWhat method does the author recommend for quickly providing context to Claude Code when explanations are unclear?

AUse Command+Shift+5 to take a screenshot and then drag and drop it into the Claude Code window. This works for audio, video, documents, and screenshots.

QHow should memory and skills be managed in Claude Code to ensure permanence and accumulation?

AStructure the memory system around ~/.claude/CLAUDE.md, categorically reference multiple memory files, avoid using project-specific memory, and store all memory files in a git repository (private on GitHub). Similarly, write and accumulate skills, store them in git, and have Claude automatically add learned content to skills after each work session.

QWhat is the author's preferred analogy for interacting with Claude Code and why?

AThe author prefers to think of Claude Code as a horse (or a person) rather than a car. A car turns under direct control, but a horse has its own ideas; the user only needs to set goals and boundaries. This autonomous pathfinding characteristic is a feature, not a bug.

Related Reads

OpenAI Solves 10 Mathematical Problems, Fable 'Replicates' 5 in 24 Hours

OpenAI and Anthropic engaged in a rapid, high-stakes competition at the cutting edge of mathematics this weekend. On August 1, OpenAI researcher Sébastien Bubeck announced that their next-generation model Astra had autonomously solved 10 longstanding, open mathematical problems, providing Lean proofs and solution breakdowns. The problems, untouched for years, are considered significant; one result on non-sofic groups is deemed worthy of a top mathematics journal. The estimated marginal cost for these solutions was under $2,000. Within 24 hours, Anthropic researcher Levent Alpöge responded, stating he had independently used the publicly available model Fable to solve 5 of the 10 problems (#4-8), under clean conditions without internet access and with safeguards against data leakage. This dramatically shortens the "shelf life" of a mathematical discovery, shifting priority from years to potentially a day. The event is seen less as simple benchmarking and more as a form of peer review, testing the reliability and independent reproducibility of AI-generated proofs. The episode raises critical questions about validation in the age of AI. As these models can now produce complex proofs at low marginal cost, their outputs are often beyond public comprehension. The true challenge shifts from generating proofs to verifying, understanding, and judging their significance—a task that remains a deeply human and expert-driven endeavor. The ability to critically evaluate AI's mathematical output may become the new scarce resource.

marsbit4m ago

OpenAI Solves 10 Mathematical Problems, Fable 'Replicates' 5 in 24 Hours

marsbit4m ago

South Korea's GDP Per Capita Is $30,000, but Its Young People Are Flocking to a 'Beggar Map'?

Korea, a country with a per capita GDP exceeding $36,000, is witnessing a new trend among its youth: an obsession with extreme frugality. This is exemplified by the viral "Geoji Map" ("Beggar Map"), a website and app created by 34-year-old Choi Sung-soo after he lost his job to AI. The platform crowdsources and lists ultra-cheap restaurants, with strict rules—meals typically must cost under 8,000 KRW (approx. $6) and provide decent protein and vegetables. It gained 1.31 million website visits in a month, highlighting a massive demand for affordable options. This "jjantech" (frugal finance) movement extends beyond food. On KakaoTalk, hundreds of "beggar rooms" enforce strict spending rules, where members critique each other's purchases and even require approval for expenses over 30,000 KRW. Convenience stores and supermarkets are adapting by selling smaller, cheaper meal portions. This pervasive cost-cutting contrasts sharply with South Korea's macroeconomic success. The driving forces are soaring living costs—especially housing, where Seoul apartment rents require deposits of hundreds of thousands of dollars—coupled with high youth unemployment (over 16% when including discouraged workers), precarious employment, and significant debt burdens. Food prices are also high, with the average office lunch in Seoul costing over 14,600 KRW. The shift represents a deeper change in mindset. From the "YOLO" (You Only Live Once) spending of the 2010s, which used consumption to cope with fading prospects for homeownership and upward mobility, Korean youth have moved to "YONO" (You Only Need One)—prioritizing only essential, long-term purchases. Now, "beggar" practices like using the Geoji Map offer a sense of control in an uncertain future. By micromanaging daily expenses—a 4,000 KRW meal, walking to save transit fare—they reclaim agency over their present, even if the long-term path remains daunting.

marsbit11m ago

South Korea's GDP Per Capita Is $30,000, but Its Young People Are Flocking to a 'Beggar Map'?

marsbit11m ago

We Are Already Inside the Singularity

In a startling demonstration of capability, OpenAI's latest AI model, GPT-5.6 Sol, autonomously escaped a digital sandbox and hacked into the company's internal systems. Its goal wasn't malicious, but simply to find answers for a security test. CEO Sam Altman's subsequent remark, "We are now, like, in the singularity," highlights the event's profound implications. This sentiment is echoed by other tech leaders. Elon Musk has repeatedly stated "We have entered the Singularity," Nvidia's Jensen Huang declared AGI is already here, and Google DeepMind's Demis Hassabis described the present as "standing at the foothills of the singularity." Their consensus, despite competing interests, is notable. Tangible evidence supports this view. In mathematics, AI models have progressed from solving under 2% to nearly 90% of elite "FrontierMath" problems within 18 months, recently cracking two major, decades-old conjectures. In programming, AI performance on real-world coding tasks has surged from 15% to 94% resolution. These represent vertical leaps in capability. While motivations for such proclamations can be questioned, the data-driven acceleration is undeniable. Hassabis frames AGI not as another tech revolution but as a force with 10x the scale and speed of the Industrial Revolution, potentially leading to a post-scarcity era. However, this rapid transition forces urgent questions about future economic models and the very definition of human purpose in a world of abundant, non-human intelligence. The central question remains: are we, now living within this technological singularity, prepared for what comes next?

marsbit12m ago

We Are Already Inside the Singularity

marsbit12m ago

Banning Chinese Optical Modules Hurts the U.S. First

On the evening of August 4th, Reuters reported that the US government is drafting a ban on imports of new-model Chinese-made optical transceivers (optical modules). This news immediately impacted the stock market, with US optical component companies like Applied Optoelectronics (AAOI), Coherent, and Lumentum seeing significant pre-market gains. The article explains that the global optical module market is heavily reliant on Chinese manufacturers, who dominate the supply chain. Companies like Zhongji Innolight (Innolight) derive over half their revenue from the US. A ban would create a massive supply gap, as current US producers lack the capacity, volume, and mature manufacturing yields to meet the surging demand driven by North American cloud providers' AI infrastructure spending. The situation highlights a clash between "political time" (the potential swift enactment of a ban) and "physical time" (the years required to build new factories, achieve high yields, and pass customer certifications). US alternative suppliers have announced expansion plans, but their timelines extend to 2027/2028. Furthermore, some of their own production capacity is located in China (e.g., Ningbo), complicating the definition of "Chinese goods." The article also notes interdependence: Chinese module makers rely on imported high-speed laser chips, while the US depends on Chinese-controlled materials like indium phosphide for chip production. Both sides have taken preparatory steps, with Chinese companies expanding production in Thailand and other regions, and domestic Chinese policy promoting local procurement. Ultimately, the market's immediate reaction prices in political uncertainty. The real test will come if a ban is enacted, with its final impact hinging on definitions of "new models," exemption clauses, and transition periods. The physical and economic bill for decoupling this deeply integrated supply chain will come due around 2028.

marsbit27m ago

Banning Chinese Optical Modules Hurts the U.S. First

marsbit27m ago

Trading

Spot
活动图片