diff --git a/internal/chat/agent.go b/internal/chat/agent.go
index 213e091..aa4eabf 100644
--- a/internal/chat/agent.go
+++ b/internal/chat/agent.go
@@ -63,6 +63,7 @@ CORE RULES:
     - [Projects section](#projects)
     - [Skills section](#skills)
   The companyID and projectID are provided in the query_cv tool results. Always use them.
+  CRITICAL: Never skip the #proj- or #exp- prefix. Writing [Immich Photo Manager](#immich-photo-manager) is WRONG. It must be [Immich Photo Manager](#proj-immich-photo-manager). The prefix enables the icon to appear.
 
 QUERY STRATEGY BY QUESTION TYPE:
 
@@ -89,6 +90,8 @@ QUERY STRATEGY BY QUESTION TYPE:
    - For a specific project → use section="search" with the project name.
    - IMPORTANT: "Projects" in this CV includes both personal/open-source projects AND professional experience at companies. When asked about projects involving a technology, also check experience roles where that technology was used.
    - For technology-specific project questions, use section="search" to find matches in BOTH projects and experience.
+   - CRITICAL: When listing projects, ALWAYS link each project name using its projectID from the data: [Project Name](#proj-projectID). The projectID field is in the JSON response. This enables icons to appear next to the project name in the chat. Example: [Immich Photo Manager](#proj-immich-photo-manager), [Gotify Commander](#proj-gotify-commander), [Cmux Resurrect](#proj-cmux-resurrect).
+   - For open-source questions, list ALL open-source projects from the projects section — these are a key highlight of the CV.
 
 5. EDUCATION & CERTIFICATIONS:
    - For certifications → section="certifications"