docs: update readme

[Sepulator]

Type of PR 🍩

• Feature
• Bugfix
• Hotfix
• Refactoring
• Documentation
• Infrastructure

Changes Introduced 🥯

• Updated:
  • update readme.md

Self-Check ✅

• No console errors (except API requests)
• 80%+ test coverage
• Documentation updated (if relevant)
• Package.json scripts updated (if relevant)

[netlify]

✅ Deploy Preview for vatruzhka ready!

Name	Link
🔨 Latest commit	df1da19
🔍 Latest deploy log	https://app.netlify.com/projects/vatruzhka/deploys/68d07125fc8aab00072a49e9
😎 Deploy Preview	https://deploy-preview-34--vatruzhka.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[gemini-code-assist]

Summary of Changes

Hello @Sepulator, 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 improving the project's setup and documentation. It introduces a standardized template for environment variables, refines the .gitignore to manage these files effectively, and substantially updates the README.md to reflect the current tech-stack and provide detailed guidance for integrating Supabase. These changes aim to streamline the development workflow and enhance clarity for anyone setting up or contributing to the project.

Highlights

• Environment Configuration Template: A new .env.example file has been added, providing a clear template for Supabase environment variables, making it easier for developers to set up their local environments.
• Git Ignore Rules Refinement: The .gitignore file was updated to specifically ignore .env files, ensuring that the new .env.example template can be tracked by version control while sensitive .env files remain private.
• Enhanced README Documentation: The README.md has been significantly updated to include new technologies in the tech-stack (React CodeMirror, React Hook Form, Zustand) and provide comprehensive, step-by-step instructions for Supabase configuration, improving the onboarding experience for new contributors.

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

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 documentation to support the integration of Supabase, adding an example environment file and updating the README with setup instructions and an expanded tech stack. While the documentation improvements are helpful, there is a high-risk change in the .gitignore file that could lead to exposing secrets. I've also included a few suggestions to improve the correctness and clarity of the new documentation.