[SIP-173] Proposal for integrate Gemini CLI Documentation via GEMINI.md
Motivation
This SIP proposes the addition of a GEMINI.md file to the Superset project. The purpose of this file is to provide comprehensive documentation and guidelines for integrating and utilizing the Gemini Command Line Interface (CLI) within Superset's development workflow. This will streamline development, facilitate easier interaction with Gemini services, and promote consistent practices across the project.
Proposed Change
Add GEMINI.md to code base.
New or Changed Public Interfaces
No
New dependencies
No
Migration Plan and Compatibility
No
Rejected Alternatives
Maybe CLAUD.md
Comment From: rusackas
Hi... can you give an example of what would be in GEMINI.md?
We also certainly haven't landed on a single proprietary LLM vendor for Superset (on the user or developer side) so we'd love to find a way to support several of them, preferably through some abstracted means.
Comment From: mistercrunch
https://github.com/apache/superset/pull/34194 tackles this as a symlink to LLMS.md
Comment From: rusackas
Curious what @i-love-thinking thinks of the above PR. Shall we move this forward to a DISCUSS phase, or is the itch here already scratched by the above (more generalized) approach?
Comment From: mistercrunch
I think it's pretty much taken care of here, the instructions to LLMs are pretty well curated and should be iterated upon based on our findings. Now it would be great to be able to have CLAUDE-specific or GEMINI-specific instructions (where the symlink approach would break down), but otherwise would require some templating to do this, like a little jinja2 maybe. For now I mostly work with Claude Code personally and haven't found a use case for LLM-specific instructions. I think we can probably close this as GEMINI.md is effectively provided now.