(no title)
meerab | 6 months ago
Here's what works for me:
- Detailed claude.md containing overall information about the project.
- Anytime Claude chooses a different route that's not my preferred route - ask my preference to be saved in global memory.
- Detailed planning documentation for each feature - Describe high-level functionality.
- As I develop the feature, add documentation with database schema, sample records, sample JSON responses, API endpoints used, test scripts.
- MCP, MCP, MCP! Playwright is a game changer
The more context you give upfront, the less back-and-forth you need. It's been absolutely transformative for my productivity.
Thank you Claude Code team!
f311a|6 months ago
ryukoposting|5 months ago
meerab|6 months ago
Claude code is amazing at producing code for this stack. It does excellent job at outputting ffmpeg, curl commands, linux shell script etc.
I have written detailed project plan and feature plan in MarkDown - and Claude has no trouble understanding the instructions.
I am curious - what is your usecase?
ethanwillis|6 months ago
Really simple workflow!
Zee2|6 months ago
jazzyjackson|6 months ago
EDIT: I see, you're asking Claude to modify claude.md to track your preference there, right?
https://docs.anthropic.com/en/docs/claude-code/memory
meerab|6 months ago
Ask Claude to update the preference and document the moment you realize that claude has deviated away from the path.
bobbylarrybobby|5 months ago
mierz00|5 months ago