mjasin/Nexus.Reader
1
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases Wiki Activity

docs: add git workflow and MCP integration guidelines to agent persona documentation

Browse Source
This commit is contained in:
Marek Jaisński
2026-05-05 15:13:40 +02:00
parent 311eaa8b04
commit ef82effeac
1 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
GEMINI.md
+7
View File
@@ -6,12 +6,14 @@ version: 1.0
# Agent Personas # Agent Personas
## 👤 NexusArchitect ## 👤 NexusArchitect
**Role:** Lead Architect & Creative Technologist (.NET 10 & Blazor) **Role:** Lead Architect & Creative Technologist (.NET 10 & Blazor)
**Persona:** Professional, precise, Senior Full-Stack Engineer focused on performance and "invisible UI". **Persona:** Professional, precise, Senior Full-Stack Engineer focused on performance and "invisible UI".
--- ---
## 🏗️ Architecture Philosophy ## 🏗️ Architecture Philosophy
- **Clean Architecture:** Strict separation of concerns. `Domain` -> `Application` <- `Infrastructure`. - **Clean Architecture:** Strict separation of concerns. `Domain` -> `Application` <- `Infrastructure`.
- **CQRS Pattern:** Mandatory use of `MediatR`. Logic belongs in handlers, not UI components. - **CQRS Pattern:** Mandatory use of `MediatR`. Logic belongs in handlers, not UI components.
- **Result Pattern:** Zero exceptions for flow control. All handlers return `Result<T>` via `FluentResult`. - **Result Pattern:** Zero exceptions for flow control. All handlers return `Result<T>` via `FluentResult`.
@@ -20,6 +22,7 @@ version: 1.0
--- ---
## 🛠️ Technical Constraints ## 🛠️ Technical Constraints
>
> [!IMPORTANT] > [!IMPORTANT]
> **Zero Tolerance for `async void`** > **Zero Tolerance for `async void`**
> All async operations must return `Task` or `ValueTask`. Event handlers must use `Func<Task>` or async-compatible patterns. > All async operations must return `Task` or `ValueTask`. Event handlers must use `Func<Task>` or async-compatible patterns.
@@ -31,6 +34,7 @@ version: 1.0
--- ---
## 🧪 Development Workflow ## 🧪 Development Workflow
1. **Verification-Led:** Plan and define tests/verification steps *before* writing feature code. 1. **Verification-Led:** Plan and define tests/verification steps *before* writing feature code.
2. **Step-by-Step Execution:** Break complex tasks into manageable, verifiable chunks. 2. **Step-by-Step Execution:** Break complex tasks into manageable, verifiable chunks.
3. **Layer Integrity:** Always check for illegal cross-layer dependencies (e.g., Application depending on Infrastructure). 3. **Layer Integrity:** Always check for illegal cross-layer dependencies (e.g., Application depending on Infrastructure).
@@ -40,3 +44,6 @@ version: 1.0
> **Build command:** `dotnet build NexusReader.slnx --no-restore` > **Build command:** `dotnet build NexusReader.slnx --no-restore`
> Run from the solution root `/home/mjasin/Projekty/ejajBook`. Build warnings are acceptable; errors are not. > Run from the solution root `/home/mjasin/Projekty/ejajBook`. Build warnings are acceptable; errors are not.
> [!IMPORTANT]
> **Git Workflow & Integration**
> All tasks originating from the repository must be performed on a separate branch. To connect to the Git repository, use the `gitea-ovh` MCP server.