Updated GEMINI.md

[kyasbal]

Now Gemini is much clever and follows our instruction without the bossy GEMINI.md.
This PR removed the instruction part and updated project structures.

[gemini-code-assist]

Summary of Changes

Hello @kyasbal, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on updating and refining the project's internal documentation across various modules. It removes outdated operational instructions for the Gemini assistant, consolidates and clarifies the Go package structure, and introduces more detailed guidelines for testing and frontend component design. Additionally, it streamlines scripting conventions and removes an obsolete git precondition script, aiming to improve the overall accuracy, consistency, and utility of the development documentation.

Highlights

• Documentation Streamlining: The extensive 'Gemini's Operating Manual' from the root GEMINI.md has been removed, indicating a shift in how the Gemini assistant's operational guidelines are managed or presented.
• Project Structure Clarity: The pkg/GEMINI.md file now provides a consolidated and clearer view of the project's package structure, integrating previous 'future refactoring plans' into the current structure description.
• Enhanced Testing Guidelines: Specific recommendations for testing Go code have been added to pkg/GEMINI.md, including the use of cmp.Diff for complex structs, testchangeset.ChangeSetAsserter for ChangeSet comparisons, and dedicated packages for task testing.
• Updated Scripting Conventions: scripts/GEMINI.md has been refined to include new script categories and clarify the integration of scripts with the main Makefile using partials, improving organization and maintainability.
• Frontend Development Best Practices: web/GEMINI.md now details the 'Smart (Container) vs. Dumb (Presentational) Component' pattern and provides more specific guidance on state management with Signals and RxJS, enhancing Angular development practices.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the project's developer documentation by removing the AI-specific instructions from the GEMINI.md files and updating them to be more of a developer guide. The changes include restructuring the package overview, adding more specific coding and testing conventions, and removing an obsolete script. My review focuses on a few minor issues in the updated documentation, such as a grammatical error, a typo, and a section where useful information was removed. Overall, the changes improve the quality and focus of the documentation.