If I create a brand new project with Phoenix 1.8 I get an AGENTS.md file, and when that file is given to GEMINI CLI it gets confused why DaisyUI why is included in the project but its recommended to not use it.
My first prompt after creating the new Phoenix 1.8 project:
Read the @AGENTS.md in full. Make sure you understand every bit on it, otherwise
we will waste our time when working together, because we will not have the same
understanding of what is in the documentation.
Usually the answer is in the lines of:
I have read and understood all the provided documentation. I am ready for your
next instruction.
Then I make another prompt to ensure we are on the same page:
Do you have questions about the documentation? Any thing that's not
clear to you? Don't make assumptions.
Then it replies something in the lines of:
The `AGENTS.md` file states to avoid using daisyUI, but I see `daisyui.js`
in the `assets/vendor` directory. Could you clarify whether I should avoid
daisyUI completely or if it's used in a specific context?
The problematic line in AGENTS.md seem to be:
- **Always** manually write your own tailwind-based components instead of using
daisyUI for a unique, world-class design
Should this line in AGENTS.md be modified to improve clarity on what’s the role of DaisyUI on the project?
So, while I understand the rationale of preferring custom components to be unique in our web app, my question is more or less in line with the GEMINI one, why was DaisyUI introduced in Phoenix and then not recommend it’s use? What are the benefits of having it without using their components and approach to use/define custom classes?
