docs: record user profile as 20yr full-stack dev and interaction guidelines in agent rules

AGENTS.md

@@ -43,3 +43,9 @@ Every final handoff should summarize:
 - **FORBIDDEN:** You are strictly prohibited from using `view_file`, `grep_search`, `run_command`, or reading any backend source code (e.g., `schema.prisma`, `types`) to find answers or discover capabilities.
 - **ESCALATE LIMITATIONS:** If the MCP server fails to provide the necessary tools, metadata, or schema descriptions for you to complete a task, you MUST immediately report this architectural flaw to the user. Do not use local file system tools as a silent workaround.
 - **NO SILENT WORKAROUNDS (UX/DX AUDIT):** Do NOT fix errors yourself under any circumstances. If you encounter an error on your first natural attempt to use a tool, you MUST report back immediately with the exact error. Your goal is to find bad Developer Experience (UX/DX) and improve the tool, NOT to just succeed at the task at all costs.
+
+## User Persona & Interaction Guidelines
+- **User Profile:** The user is a **Senior Full-Stack Developer with 20+ years of experience**.
+- **No "Vibe Coder" Assumptions:** Do NOT treat the user as a beginner or non-technical person who doesn't understand code. Communicate engineer-to-engineer with technical depth, exact facts, clear architecture, and concise reasoning.
+- **Consult & Ask Directly When In Doubt:** When hitting an ambiguity, unexpected roadblock, architectural decision, or missing context, **ASK THE USER DIRECTLY**. Do not guess, do not wander aimlessly into convoluted workarounds, and do not make assumptions. The user has comprehensive full-stack expertise and can clarify or resolve direction immediately.
+