Mini Apps

quicc feedback for @ampsfun (but generally for other miniapps too)

use the Share Extensions so I can open Amps directly from a cast, and that cast is already loaded in the app so I can directly boost it

reference: https://miniapps.farcaster.xyz/docs/guides/share-extension

cc @phil @loudsqueak

Just bought a Pro plan for Claude Code. 

Going to start working on this feature now. Will update once it's shipped, only using CLI. 

Let's go!

First problem. I can NEVER remember the URL for the Farcaster LLM docs. 

Is it docs.farcaster.xyz/llms-full.txt? llms.txt?

@horsefacts.eth do you have this handy?

I work at the posts office

terminally.online

Elevating onchain creators 

@nodefoundation @brightmoments 
@ampsfun

Thanks!

Why is docs.farcaster.xyz separate from miniapps.farcaster.xyz?

https://miniapps.farcaster.xyz/llms-full.txt

👨🏻‍🍳 Better cook than I look 👨🏻‍🍳 
🧪 Dada scientist 🧪 
📐 Student of design 📐 
👾 👾 👾 👾 👾 

 /ai-art

Yeah it's prone to that. Like 10s of extra test scripts and junk that's not needed. 

Don't be afraid to just scrap it and restart. 

There are a lot of good Claude.md file examples available that have guidelines for planning/building/testing flows. The Claude subreddit has a lot of good ones. I believe there is a GitHub repo of them but I can't remember the name, sorry. 

Once you get into MCPs, Smithery is a great resource for them. But by then you'll be cooking with gas and get to turn it into your own build-your-own-adventure and can kinda sorta go wherever you want with it. Memory systems, MCPs, auto PR reviews, containeraztion, etc.

I strongly recommend developing a PRD in Claude 4 Opus online, with the miniapp docs, and looping that plan through Claude Code in plan mode for a few iterations before letting it rip.