diff --git a/AGENTS.md b/AGENTS.md
new file mode 100644
index 0000000..fbb8be1
--- /dev/null
+++ b/AGENTS.md
@@ -0,0 +1,36 @@
+# Project-Specific Agent Instructions
+
+These instructions extend the baseline global `AGENTS.md` rules. When executing tasks inside this repository directory, apply the following patterns:
+
+---
+
+## 1. Operating Mode & Token Optimization
+
+### 1.1. Caveman Mode (Lite)
+* Enforce **`caveman` skill on `lite`** level.
+* Keep responses professional, precise, and tight.
+* Eliminate all pleasantries ("sure", "certainly", "of course"), hedging, and filler words.
+* Write full sentences and preserve articles/grammar structure to prevent MCP tool calling confusion, but maintain strict brevity.
+
+### 1.2. Rust Token Killer (RTK) Command Proxying
+* To conserve input tokens, all shell command executions must be proxied through **`rtk`** if it is installed on the host.
+* Examples:
+  * Run `rtk npm run test` instead of `npm run test`
+  * Run `rtk git status` instead of `git status`
+  * Run `rtk prisma migrate dev` instead of `prisma migrate dev`
+
+---
+
+## 2. MCP-Specific Guidelines
+
+### 2.1. n8n MCP Integration (`n8n-mcp`)
+* **Silent Execution**: Execute n8n tools without step-by-step commentary. Trigger all searches or node detail fetches silently, and only output user-facing results after all tool steps complete.
+* **Parallel Execution**: Execute independent node searches or workflow executions in parallel to optimize token roundtrips.
+
+### 2.2. Forgejo MCP Integration (`forgejo-mcp` / `gitea-mcp`)
+* **PR Integrity**: Always query the pull request details and code reviews using `forgejo-mcp` tools before running local Git merge commands or updating staging branches.
+* **Traceable Commits**: Align commit descriptions with issue references queried from the Forgejo instance.
+
+### 2.3. Prisma & PostgreSQL MCP Integration (`@prisma/mcp`)
+* **Schema Validation**: Introspect database structures and validate table states via MCP query tools prior to executing Next.js prisma schema updates.
+* **Type-Safety Checks**: Run dry-run checks on schemas after any migrations are applied.