warning, human written code. use the right model: /model opusplan ( effort mid or low) Trust me, it’s all you need. New Sonnet is amazing and much more reliable. Plan with Opus, Execute with Sonnet, Be efficient on Tokens understand the power of skills I saw someone advertising a monthly SaaS service that creates “nodes” for your project and manages it via mcp. it feeds the info where stuff is into your prompts so your app is not wasting tokens finding it. Two thoughts here:
- You’ve gotta have a horrible project structure, for claude to wast soo much tokens to find the right entry points. Rule of thought: AI was trained on human readable code. If a human cant understand where shit is, AI wont either.
- If you really want to go fancy, create skills: Create a code base map, a simple markdown file that lists your features and mentions starting points in your codebase. Create a skill that should read the codebase map before any big exploration. Create a skill that updates the codebase map after any feature changes or additions. The codebase map can be useful, but i truly believe that having a well structured codebase is more than enough for claude not to waste a meaningful amount of tokens. Let me know how you manage your limits. submitted by /u/Mopezz
Originally posted by u/Mopezz on r/ClaudeCode
You must log in or # to comment.