Gemini Project Guide

Overview

This guide establishes the core principles, coding standards, and operational workflows to ensure that all code developed within this project adheres to a high standard of quality, security, and maintainability. It serves as the foundational contract for development practices.

Capabilities

• Code Structure Enforcement: Mandates strict limits on function size (<50 lines) and complexity (cyclomatic complexity <10).
• Workflow Management: Enforces a trunk-based development model using conventional commits and mandatory Pull Requests (PRs).
• Security First: Requires input validation, output sanitization, and prohibits the commitment of any secrets or credentials.
• Testing Rigor: Sets a minimum code coverage target (>80%) focused on business logic and edge cases.
• Documentation Governance: Directs documentation to appropriate locations (e.g., CHANGELOG, PR descriptions) rather than cluttering the root directory.

Example Use Cases

• Starting New Feature Development: A developer should begin by creating a branch named feature/descriptive-name and commit frequently after completing small, functional steps.
• Code Review Preparation: Before submitting a PR, the developer must ensure that linting, building, and testing have all passed successfully to guarantee code integrity.
• Handling Sensitive Data: When implementing any new endpoint or function, developers must validate all incoming parameters at system boundaries to prevent injection vulnerabilities.
• Project Onboarding: New team members should review this guide first to understand the expected development lifecycle before writing production code.