Here's what the Founder of Claude Code does before he starts ANY project: 1. Plans first, codes never, he goes back and forth with Claude on the plan until it's perfect. No code gets written yet 2. Creates a CLAUDE.md file (a simple doc that Claude reads every session... so it knows your project, your rules, your style) 3. Gives Claude a way to verify its own work - For backend: write and run tests - For UI: take screenshots, check in browser Claude should never finish a task without proving it works 4. Sets up project-level permission rules in settings.json instead of skipping permissions entirely. Shared with the whole team 5. Five more preparation steps in VIDEO BELOW 6. Only then switches to auto-accept mode and lets Claude build The part most people miss: he doesn't treat Claude as a magic box that gets things right first try he treats it like a junior dev that needs clear instructions, feedback loops, and guardrails at scale he runs multiple sessions in parallel, uses Opus with thinking enabled because it makes fewer mistakes even though it's slower and relies on background agents that push code for later review his setup is surprisingly simple. no crazy custom tools. just slash commands, subagents, and a clean CLAUDE.md the difference isn't the tool. it's how you set it up before you start ❤️ P.S. for sure 99.5% of readers will scroll down this tweet, but I send it to 0.5% who loves to learn how to improve your workflow daily and control 99.5% in 2 years Hard skills literally mean nothing in our world The most important skills which you can have are: building architectures and orchestrations If you master it and use a creative approach, CONGRATSshow more

Ronin

109,197 subscribers

分享 下载