AndyL
Elixir has rapidly changing hex packages, both public and private. For people who use AI Coding Tools (Aider, Cursor, Windsurf, etc.), how are you ingesting Project Docs into your LLM Context?
For example: I’d like my Aider session to answer questions and generate code for the latest release of Ash. I haven’t settled on a good approach.
There are emerging tools and standards: LLMS.txt, Model Context Protocol (mcp directory), hex2txt, Claude Projects, Windsurf rules, and more. There is an open PR for ExDoc to auto-generate markdown that can be loaded into a LLM context.
Over the long term maybe MCP will be the widely adopted standard. But for now, the optimum workflow is evolving with heavy doses of trial and error. Various Editors and LLM providers offer different features, and IMO the optimal solution for Elixir is going to be different from languages like JS or Python.
Given the current state of the world, how are you ingesting Elixir Project Docs for LLM-aided development? Any tips/tricks/observations appreciated!
Where Next?
Trending in AI / LLMs
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Practical resources that improve the lives of professional developers.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #elixirconf-eu
- #metaprogramming
- #hex
Our Sponsors
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Producing high quality Elixir screencasts since 2017.
**Building the future of software with AI, trust, and human connection.**
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 1- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
TimButterfield
With ChatGPT, you can create a project and, using the online UI, upload files to that project. This can be useful when you want to have a common set of documentation to use with the individual chats under that project. For the individual chats, you can also attach files for it to refer to on a more temporary basis.
With Claude Code, you have have it reference documentation within your project. In that case, just create a folder to contain the set of docs you want it to use.
I have used both of these approaches. For both, give specific instructions to the AI to refer to those sets of documentation for whatever task you ask it to perform.