𝗖𝗹𝗮𝘂𝗱𝗲 𝗖𝗼𝗱𝗲 𝗔𝘀 𝗔 𝗗𝗮𝗶𝗹𝘆 𝗣𝗮𝗶𝗿 𝗣𝗿𝗼𝗴𝗿𝗮𝗺𝗺𝗲𝗿

𝗖𝗹𝗮𝘂𝗱𝗲 𝗖𝗼𝗱𝗲 𝗔𝘀 𝗔 𝗗𝗮𝗶𝗹𝘆 𝗣𝗮𝗶𝗿 𝗣𝗿𝗼𝗴𝗿𝗮𝗺𝗺𝗲𝗿

I used Claude Code for three weeks. I built a process to save money and time.

Use a per-project CLAUDE.md file. Global files cause confusion. Keep your file short. Include:

• Stack and versions.
• Package manager.
• Things to avoid.
• Specific repo quirks. Short files save money.

Stop the AI from editing too many files. Use these habits:

• Tell it to look at one file only.
• Ask it to list files it will touch first. If the list is too long, stop the request.

Cut your token use in half.

• Paste the error message. Do not paste the whole file.
• Use this flow: read file, propose diff, apply.
• Use /clear for new tasks.

AI tests often test the implementation. They do not test the goal.

• Write one or two test cases first.
• Ask the AI to implement the code to pass those tests. The test is the source of truth.

Use /rewind to fix mistakes. It is faster than git. Avoid "refactor this." Use "rename this function and update callers."

It is not magic. It does not write your whole app. It handles the boring 80% of your work.

Source: https://dev.to/lunar_geng_6536877f18aabb/how-i-set-up-claude-code-as-a-daily-pair-programmer-without-burning-the-budget-2fni Optional learning community: https://t.me/GyaanSetuAi