<div dir="ltr"><div class="gmail-gs" style="margin:0px;min-width:0px;padding:0px 0px 20px;width:auto;font-family:"Google Sans",Roboto,RobotoDraft,Helvetica,Arial,sans-serif;font-size:medium"><div class="gmail-"><div id="gmail-:1yo" class="gmail-ii gmail-gt" style="direction:ltr;margin:8px 0px 0px;padding:0px;font-size:0.875rem;overflow-x:hidden"><div id="gmail-:1oz" class="gmail-a3s gmail-aiL" style="direction:ltr;font-variant-numeric:normal;font-variant-east-asian:normal;font-variant-alternates:normal;font-size-adjust:none;font-kerning:auto;font-feature-settings:normal;font-stretch:normal;font-size:small;line-height:1.5;font-family:Arial,Helvetica,sans-serif;overflow:auto hidden"><div id="gmail-avWBGd-243"><div dir="ltr"><p>Hi All,</p><p>We've started a new open-source project at Tiger Data aimed at helping AI agents generate higher-quality Postgres code: <a rel="noopener" href="https://github.com/timescale/pg-aiguide" target="_blank">https://github.com/timescale/pg-aiguide<span aria-hidden="true"></span></a><br>For broader context, here’s the announcement blog describing the approach and motivations:<br><a rel="noopener" href="https://www.tigerdata.com/blog/we-taught-ai-to-write-real-postgres-code-open-sourced-it" target="_blank">https://www.tigerdata.com/blog/we-taught-ai-to-write-real-postgres-code-open-sourced-it<span aria-hidden="true"></span></a></p><p>As part of this work, we're adding guidance modules for major Postgres extensions, and PostGIS is at the top of our list. I’m reaching out to ask whether anyone from the PostGIS community would be interested in collaborating.</p><p>The core idea is to provide “skills” that capture best practices, common pitfalls, and domain-specific patterns so that AI agents can make better decisions. Here is an example skill:<br><a rel="noopener" href="https://github.com/timescale/pg-aiguide/blob/main/skills/design-postgres-tables/SKILL.md" target="_blank">https://github.com/timescale/pg-aiguide/blob/main/skills/design-postgres-tables/SKILL.md<span aria-hidden="true"></span></a></p><p>If there’s interest, we’d be happy to set up a call to walk through the approach and answer questions.</p><p>Beyond skills, the project also includes semantic search over documentation. We currently index Postgres and TimescaleDB docs, and we plan to include the PostGIS manual as well. We can handle the processing, but wanted to check whether there’s anything unusual about the HTML manual that we should be aware of. We’d also appreciate any guidance on which versions of the manual are most important to index.</p><p></p><p>Thanks for your time, and we’d welcome any feedback or involvement from the community.</p></div><div class="gmail-yj6qo"></div><div class="gmail-adL"></div></div></div></div><div class="gmail-WhmR8e" id="gmail-avWBGd-244" style="clear:both"></div></div></div><br class="gmail-Apple-interchange-newline"></div>