Skip to content

Improve llms-full.txt by adding API references and adding compact version of the docs #147

Open
@aglitchman

Description

@aglitchman

After reading this discussion, I realised that 200K+ tokens in the current llms-full.txt file is a lot, it is not suitable for all LLMs, i.e. only Google Gemini 2.5 can handle it. In my opinion, we need to improve the documentation files for LLMs as follows (got the idea from the blog post):

  • llms-full.txt: include everything about Defold, i.e. manuals + API.
  • llms-small.txt: a compressed version of llms-full.txt, i.e. by removing docs about porting to consoles, IDE stylization etc, and keep docs only about programming.
  • llms/docs.md: manuals only, like llms-full.txt now.
  • llms/ref.md: API only.

It seems to me that this structure would be flexible enough to allow a developer to specify only documentation or APIs as the LLM context.

P.S. Actually, there is no clear instruction in the community right now about what type of content you need to ‘feed’ LLM to have high quality answers.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions