feat: add llms.txt to docs

[jokokucing]

This will help when building recipes using copilot, etc..

I found some things you can use like https://scalabledeveloper.com/posts/llms-txt-with-astro/

[xynydev]

On the surface level, I do support making it easier to use libraries with coding agents using llms.txt for giving them context. On the other hand, I don't know if I want to encourage using BlueBuild with LLMs for two reasons:

• The point of this tool is to make the configs human readable and writeable, not full-on code
• At the same time using and an image-based system and building an image yourself requires some understanding of what is possible and what is good practise, which is something you might not learn when just using an agent to do everything for you

Basically, BlueBuild tries to fill the same conceptual space as coding agents do: Allowing you to make something only by knowing what you want to do, without having to learn every implementation detail of how to do it.

https://github.com/projectbluefin/finpilot/ is a kindofa "competing project" that is meant for people wanting AI-help in doing the implementation itself.

Then again, I think documentation that is good for AI is often also good for humans. I think our docs aren't perfett, not for AI-usage and not for humans. Improving the human side shall be my first priority, but adding an llms.txt might be something I consider when I feel that the human documentation is good and straightforward enough for LLMs to use as well.

[xynydev]

Anothe concern is AI-driven contributions to the project, which is a different topic altogether. I should probably draft up a small guideline about that as well.

[jokokucing]

I understand your point. In my use case sometimes I will have a syntax error or something very small I overlook that's causing build failures. I would use the llm to double check and tell me what I did wrong.