Getting subpar results from Claude Code Try these 3 things to get better results claudecode vibecoding codingagent

You're getting sh**ty code because your clod.md file is bloated. Let me show you how to fix that. clod.md is a context file that tells clod code about your codebase. You can generate one with slash init if you haven't already, or just write one yourself. Long clod.md files can waste tokens, making you reach your usage limits faster or cost you more in the API. Also, every line in your clod.md file competes for attention with your actual task. As a general rule of thumb, your clod.md file shouldn't be longer than 150 lines, but even shorter is better. Here are three things that you can do to fix it. The first is to break apart your clod.md file into smaller nested files. These nested files are automatically loaded whenever clod reads a file in the parent directory. This is great for module-level documentation. The second thing you can do is extract conceptual information into a docs folder. Then you can create markdown files in this docs folder explaining how to do specific things, document specific APIs or components or anything like that. Then you can reference this folder from your clod.md files with instructions to pull context when necessary. The third thing you can do is extract repeatable workflows or processes into clod skills. You can think about skills like clod.md files that clod can choose to load in based on whether it needs a specific ability like writing documentation or things like that. Be sure to save this video for later and follow for more practical clod code tips without the hype.