MIME-Version: 1.0
References: 
 <CAH_7fT3xTQq=xAyr8Oa+GTEVKrQ+2S8iMgM+xy99wNKW7zXjbg@mail.gmail.com>
 <D03E44EB-66A2-45C8-BB83-870D1209E2C8@yesql.se>
In-Reply-To: <D03E44EB-66A2-45C8-BB83-870D1209E2C8@yesql.se>
From: =?UTF-8?Q?Adri=C3=A1n_Cuadrado_Chavarr=C3=ADa?=
 <adriancuadradochavarria97@gmail.com>
Date: Mon, 3 Nov 2025 20:44:34 +0100
Message-ID: 
 <CAH_7fT2jVAuE8ZZMBpa9cDNw64XmOnR3LHiWaJ6xHLj0KjLLeA@mail.gmail.com>
Subject: Fwd: Feature request: Add a llms.txt file to the docs for AIs to
 learn
To: pgsql-www@lists.postgresql.org
Cc: daniel@yesql.se
Content-Type: multipart/alternative; boundary="00000000000095274a0642b5f2f9"
Archived-At: 
 <https://www.postgresql.org/message-id/CAH_7fT2jVAuE8ZZMBpa9cDNw64XmOnR3LHiWaJ6xHLj0KjLLeA%40mail.gmail.com>
Precedence: bulk

--00000000000095274a0642b5f2f9
Content-Type: text/plain; charset="UTF-8"

> > Some projects like [NextJS](https://nextjs.org/docs/llms-full.txt),
[Stripe](https://docs.stripe.com/llms.txt), [BetterAuth](
https://www.better-auth.com/llms.txt) and [Zod](https://zod.dev/llms.txt)
already provide this.
> >
> > With this file we can make sure that the AI model fetching it is always
using the latest features and versions of postgresql.
> >
> > https://llmstxt.org/
>
> I would recommend posting this to the pgsql-www@ mailinglist instead to
get the
> attention of the website team.
>
> That being said, AFAICT there are no LLM providers who have publicly
stated
> that they are using this proposed standard at all, and the author has not
> submitted it to IETF for a formal review in the RFC process, so it
doesn't seem
> all that promising.

Forwarding to the pgsql-www@lists.postgresql.org mailing list as suggested
by Daniel.

--00000000000095274a0642b5f2f9
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote gmail_quote_container">&gt;=C2=
=A0&gt; Some projects like [NextJS](<a href=3D"https://nextjs.org/docs/llms=
-full.txt" rel=3D"noreferrer" target=3D"_blank">https://nextjs.org/docs/llm=
s-full.txt</a>), [Stripe](<a href=3D"https://docs.stripe.com/llms.txt" rel=
=3D"noreferrer" target=3D"_blank">https://docs.stripe.com/llms.txt</a>), [B=
etterAuth](<a href=3D"https://www.better-auth.com/llms.txt" rel=3D"noreferr=
er" target=3D"_blank">https://www.better-auth.com/llms.txt</a>) and [Zod](<=
a href=3D"https://zod.dev/llms.txt" rel=3D"noreferrer" target=3D"_blank">ht=
tps://zod.dev/llms.txt</a>) already provide this. <br>&gt;=C2=A0&gt; <br>&g=
t;=C2=A0&gt; With this file we can make sure that the AI model fetching it =
is always using the latest features and versions of postgresql.<br>&gt;=C2=
=A0&gt; <br>&gt;=C2=A0&gt; <a href=3D"https://llmstxt.org/" rel=3D"noreferr=
er" target=3D"_blank">https://llmstxt.org/</a><br>
&gt;=C2=A0<br>&gt;=C2=A0I would recommend posting this to the pgsql-www@ ma=
ilinglist instead to get the<br>&gt;=C2=A0attention of the website team.<br=
>
&gt;=C2=A0<br>&gt;=C2=A0That being said, AFAICT there are no LLM providers =
who have publicly stated<br>&gt;=C2=A0that they are using this proposed sta=
ndard at all, and the author has not<br>&gt;=C2=A0submitted it to IETF for =
a formal review in the RFC process, so it doesn&#39;t seem<br>&gt;=C2=A0all=
 that promising.<br><br>Forwarding to the <a href=3D"mailto:pgsql-www@lists=
.postgresql.org">pgsql-www@lists.postgresql.org</a> mailing list as suggest=
ed by Daniel.</div></div>

--00000000000095274a0642b5f2f9--