Claude context prompt

Paste this in addition to the main prompt any time you ask Claude to build a component, page, or visual. You don't need it for pure logic questions or debugging.

When you have a bug, don't just describe it — drag your .tsx file into the chat. Claude reads the whole file and gives a much more accurate fix than guessing from a description.

One task per session works better than "build the whole booking system." Focused context = better code. When you hit the message limit, start a new chat with the context prompt — pick up exactly where you left off.

If Claude cuts off mid-code, say continue from [last line you saw]. But it's often cleaner to ask for just the missing function rather than continuing a long block.

Add "add a comment above each section explaining what it does and why" to any code request. You'll learn faster and understand what to change when something breaks.

Copy the entire terminal or browser console error — including the stack trace. "It says something about undefined" gives Claude almost nothing to work with. The full error gives everything.