I spent way too many late nights trying to get Claude Code to stop hallucinating hook dependencies on a CRM dashboard project I just finished. Honestly, you might want to consider how it handles state management before diving too deep. I found two main paths to take here.

• Custom System Instructions: I used these for React 18 Hooks API patterns. Great for keeping logic consistent, but be careful because it sometimes ignores local context if the prompt gets too bloated.
• The Tailwind CSS v3.4 Framework MCP: Basically a lifesaver for layouts. It gives you solid boilerplate fast, tho it might add extra utility classes you dont actually need. I would suggest starting with the hooks instructions first. Make sure to double check your useEffect cleanup functions tho... Claude likes to skip those when it is in a rush and you dont want memory leaks on a local shop dashboard.

To add to the point above: I'd actually be careful about going too deep into custom system instructions right away, especially since you're on a tight deadline and probably want to keep your API costs down. Complex prompts can eat through tokens faster than you think, and that adds up when you're testing. Honestly, I've found that just pointing Claude Code to a specific documentation file or a simple rules file in your root works way better for keeping React structure consistent. If you want to save some money and time, prioritize these things instead:

• Create a small text file with your preferred hook patterns so it doesnt get too creative.
• Stick to shadcn/ui UI Library for the dashboard pieces because Claude already knows the syntax perfectly and wont hallucinate the props.
• Use Lucide React Icons for all your dashboard indicators to keep the bundle light and the code simple. Just watch out for running indexing commands on your whole project if you have a massive node_modules folder... it can lag the session and waste money for no reason.

Saved for later, ty!

Just saw this and ugh, honestly it reminds me of when I tried using these newer agent tools for a big dashboard update last month. I was so hyped but it turned out to be super disappointing because I kept hitting these weird reliability issues. My brother actually had a similar ordeal when he was trying to build a simple inventory tracker for his garage.

• he spent all night looking at the official react dev docs
• then he got lost in some deep architectural blog posts on dev to
• eventually he just gave up and used a basic template It was such a mess... he thought the tool would just handle the component nesting for him but it kept getting confused. Reminds me of the time we tried to set up a smart home system and it ended up locking us out of the kitchen for three hours because of a firmware glitch. Just a total nightmare when you expect tech to be smart and it just isnt.