Content pfp
Content
@
https://warpcast.com/~/channel/aichannel
0 reply
0 recast
0 reaction

horsefacts πŸš‚ pfp
horsefacts πŸš‚
@horsefacts.eth
We want to make our docs useful for AI tools like Claude and Cursor. I know there are some emerging standards for this but need to read up. Where should I start?
10 replies
14 recasts
51 reactions

HH pfp
HH
@hamud
A single giant markdown file. You can take a look at what coinbase did with their sdk. Also for some reason the best prompts just look like xml
1 reply
1 recast
11 reactions

keccers pfp
keccers
@keccers.eth
Tbh it seems like the AIs already know a lot. You could add an LLMs dot text https://github.com/AnswerDotAI/llms-txt But also in all honesty i would prefer some basic cleanup on the docs themselves first vs this. There is stuff in the Warpcast docs that is useful when building Frames and it’s not clear you have to go there to find the info. I should be able to go to one place to find everything.
2 replies
1 recast
10 reactions

Tamrat pfp
Tamrat
@tamrat
Zapper has a good example of this that i tried with claude https://protocol.zapper.xyz/docs/api/agents cc @jasper
0 reply
0 recast
4 reactions

silly goose pfp
silly goose
@lovejoy
imo the main point really is to keep them up-to-date with all the latest changes or any details that could be not obvious both to dev and ai. e.g. i have access to all the docs, but additional important life hacks are only in frame devs chat β€” which i wish i could just parse as a whole as it's easy to miss sth useful. ALSO creating starter templates for smaller pieces of functionality would be super helpful, so it's easier to learn what is going on. as i'm learning, i'm trying to figure out the easy way for a non-dev person to create their frame, and i think templates like that could potentially be a life-changer for them. technical things like keeping it in a single file (or certain format) is good in a sense that i can copy it with a single click to paste into claude, but doesn't matter too much difference
0 reply
0 recast
3 reactions

Steve pfp
Steve
@sdv.eth
https://llmstxt.org
0 reply
0 recast
3 reactions

mom pfp
mom
@mom
include practical examples in the md/txt file
0 reply
0 recast
1 reaction

Kasra Rahjerdi pfp
Kasra Rahjerdi
@jc4p
https://llmstxt.firecrawl.dev/ best tool rn
0 reply
0 recast
1 reaction

shazow pfp
shazow
@shazow.eth
Keep in mind that the point of llms.txt is to fit relevant docs/examples into a smaller context window. You can throw in all of the docs in there, but not all models support large context windows, and many are quite expensive on a per-token basis especially if you need the context included in multiple queries. It's just a matter of converting everything you have to markdown.
1 reply
0 recast
1 reaction

mom pfp
mom
@mom
claude is mostly considered a model and cursor a toolβ€” i would be most influenced by piro of all your staff regarding this topic. woj as well.
0 reply
0 recast
0 reaction

πŸ™ DappyKit pfp
πŸ™ DappyKit
@dappykit
πŸ”₯
0 reply
0 recast
0 reaction