I added a repo to feed the docs to context7, for anyone doing mcp would be useful.

[biologicpro]

https://github.com/biologicpro/haxeflixel_doc_for_context7

not sure it worth mention for flixel-docs, just want share with you this thing,
can close me if it is ok :)

[NaxeCode]

Thank you! this has helped me immensely :)

[Geokureli]

I'm not up to date with LLM tools can you elaborate on what exactly this does and how it was made? I'm looking at some files, and some parts match the doc, but other parts don't. If this was created procedurally should flixel-docs add that step to it's deployment?

[NaxeCode]

@Geokureli can't speak for biologicpro , but I’ve found this repo genuinely useful; I use it with a local agent setup through the Context7 MCP tool so models can pull fresher HaxeFlixel docs during codegen, which helps a lot since most of them won’t have the latest info built in. it’s more of an AI facing mirror/export than a replacement for flixel-docs. If it’s generated procedurally, you're right to keep that as a separate export step, instead of it being part of the main deploy

[biologicpro]

Yeah, thanks @NaxeCode for the declaration, now i see back my initial message, thats was very unclear, sorry !

Actually its the generated doc + context7.json
, to
and this repo link is submitted to the context7 site service, so what it does if you developing flixel using certain
ai agent + context7 mcp, then you will get the most updated flixel doc and usage example.

context7 is a doc service , that you can think when ai try to output something with flixel doc api,
then it will try search the flixel doc in context7 rather than use its trained data, which can be outdated, or ai hallucinations.

so to wrap up:
Actually is doc generated repo + context7.json repo, i'd like to share the information of the existence of repo,
so the flixel community could know that the mcp supports the updated flixel.

Feel free to do anything following, i am grateful for any:
1. Thanks the info, close the issue.
2. Include the info in official flixel-doc repo, so the community knows better.
3. due to i am not very active in flixel dev recently, maybe the official flxiel-doc could add context7.json and feed it
to context7 mcp service, so that would make sure the context7 always has the updated doc.

note : 2,3 are just suggestions , there is no why to do it ,adding a 3rd party dependency , add lots of things.

[Geokureli]

I'd be down to add context7.json. Let's discuss what that would take to achieve

[biologicpro]

I checked the doc and actually it becomes very simple now:
you just need paste the doc link (in this case the flixel-doc github)
(the context7.json is a plus, to let context7 parse better )

but if you are doing this officially, as the owner of the library/framework, it gives you
the admin panel access and more operations, once you claim it.

The details you can check here:
https://context7.com/docs/adding-libraries.

And since this is the official doc, the mcp service will always have the updated version for
flixel community !

[Geokureli]

Do I add the context7 to the flixel repo with a link to the doc repo or do i add the context7 to the docs repo?

i.e. this?
https://gist.github.com/Geokureli/ec34b25cb58fe00d6dbeaae469075e94

[biologicpro]

What i have done is add the context7.json to the docs repos, and submit the flxiel doc repo link to here.
But i just notice the flixel-doc only contains the tutorial, example as in md format, the flixel api generated doc
i think is needed for context7 too.