The payload docs are rate limiting claude code from reading the documentation. What's the reason for this?
#Claude code is gettting rate limited when reading the docs.
honest basin
marble burrowBOT
solemn ibex
I think the payload team block it, better to point Claude to https://payloadcms.com/llms.txt and https://payloadcms.com/llms-full.txt
honest basin
Great info @solemn ibex thanks - I couldn't see this specified anywhere in the docs. Would be helpful if there was a callout saying this in the getting started page
quick void
Hey @honest basin are you setting claude loose on the browser?
It's likely much more efficient to clone the payload repo down and just have it look through the MDX files instead (this is what I do)
honest basin
@quick void nice idea. No I’m letting it loose in VSCode
Still relatively new to full-stack js and github operations. How would you go about this if you’re adding payload to an existing project?
quick void
I would start right here -> https://payloadcms.com/docs/getting-started/installation#adding-to-an-existing-app
honest basin
Sorry maybe I wasn't clear @quick void I meant since I already managed to get an instance of payload working and would rather not start from 0. Should I use the repo just as a reference and clone it locally so CC has a point of reference?
quick void
Ohhh! Yes, that's what I was suggesting
because all of our docs are in payload/docs as MDX files, it can rip through those very quickly
honest basin
because all of our docs are in payload/docs as MDX files, it can rip through tho...
yes I noticed that when I opened up the repo. great! thank you.
Would you store the reference clone on the project locally or as a separate folder on your device?
quick void
I'd put it in a separate folder entirely
honest basin
what's the reasoning behind that? Better performance/cleaner project structure?
sorry for the detailed questions - I'm new to this and eager to learn
quick void
If you already have an instance running for the project you're working on that's fine, I was just suggested to clone payload core down to your local machine so claude can more easily and quickly read through the docs that way, does that make sense?
honest basin
Yes, I was debating whether or not to keep the clone within the project folder (so accessible via VS Code and neatly organized in my project) or just have it as a separate folder on my desktop, let's say, so that I can prompt a cloud code to actually access that if we have an issue and also put it in the Cloud.md instructions, etc.
But I think the approach of having it as a separate folder on the desktop makes more sense because then VS Code wouldn't be parsing through double entries, etc.
quick void
yeah I would recommend against that since it is just a resource, just tell claude in your prompt where the docs are e.g. www/payload/docs
it doesn't care where the folder is, but it wouldn't make sense to have the entire payload repo inside your project
honest basin
I appreciate that. Thanks!