chore: config ai agent

Author: ikkz

.gemini/settings.json

@@ -0,0 +1,10 @@
+{
+  "mcpServers": {
+    "nx-mcp": {
+      "type": "stdio",
+      "command": "npx",
+      "args": ["nx", "mcp"]
+    }
+  },
+  "contextFileName": "AGENTS.md"
+}

AGENTS.md

@@ -3,21 +3,39 @@
 This repo uses Codex-style coding agents. Keep instructions short, concrete, and scoped to this project.
 
 ## Project Layout
+
 - `apps/webhook_router`: Rust backend (Axum + SQLite)
 - `apps/console`: React frontend
 - `docs/`: design notes and specs
 
 ## Backend Conventions
+
 - SQLite only; support `:memory:` for tests.
 - No queues; dispatch synchronously.
 - Webhook endpoints are `POST /ingress/:endpoint_id/:platform`.
 - Use HTTP Basic Auth for `/api`.
 - Adapters live in `apps/webhook_router/src/adapters/`.
 
 ## Testing
+
 - Prefer unit tests near the code (module `#[cfg(test)]`).
 - Run: `cargo test -p webhook_router`.
 
 ## Docs
+
 - Update `docs/tech-plan.md` if architecture changes.
 - Adapter formats live in `docs/adapters/`.
+
+<!-- nx configuration start-->
+<!-- Leave the start & end comments to automatically receive updates. -->
+
+# General Guidelines for working with Nx
+
+- When running tasks (for example build, lint, test, e2e, etc.), always prefer running the task through `nx` (i.e. `nx run`, `nx run-many`, `nx affected`) instead of using the underlying tooling directly
+- You have access to the Nx MCP server and its tools, use them to help the user
+- When answering questions about the repository, use the `nx_workspace` tool first to gain an understanding of the workspace architecture where applicable.
+- When working in individual projects, use the `nx_project_details` mcp tool to analyze and understand the specific project structure and dependencies
+- For questions around nx configuration, best practices or if you're unsure, use the `nx_docs` tool to get relevant, up-to-date docs. Always use this instead of assuming things about nx configuration
+- If the user needs help with an Nx configuration or project graph error, use the `nx_workspace` tool to get any errors
+
+<!-- nx configuration end-->