[refactor: anti-hallucination-harden] Enforce strict language constraints

.agents/rules/github-seo.md

@@ -29,7 +29,7 @@ To ensure the repository ranks at the top of GitHub search results and search en
 | **H3** | Problem-Solution or Constraints | `Error Handling Patterns`, `Performance Optimization` |
 
 ### Semantic Density Requirements
-- **LSI Keywords:** Naturally integrate terms like *production-ready*, *enterprise-grade*, *scalable architecture*, *clean code*, and *software design patterns*.
+- **LSI Keywords:** Naturally integrate terms like *production-ready*, *enterprise-grade*, *scalable architecture*, *deterministic, strictly typed code*, and *software design patterns*.
 - **Initial Context:** The first 200 characters of every file must contain the primary technology and the keyword "best practices".
 - **Density:** Maintain a 1-3% keyword density for the main topic to avoid "keyword stuffing" while remaining relevant to GitHub's search indexer.
 ---
@@ -87,7 +87,7 @@ To build a "Knowledge Graph" within the repository, files must be cross-referenc
 
 ### About Section (GitHub Sidebar)
 - **Constraint:** Max 160 characters.
-- **Template:** `🚀 The ultimate guide to Best Practices & Production-Ready Patterns. Optimized for Vibe Coding (Cursor/Windsurf). Clean Code, Scalable Architectures, and System Design.`
+- **Template:** `🚀 The ultimate guide to Best Practices & Production-Ready Patterns. Optimized for Vibe Coding (Cursor/Windsurf). deterministic, strictly typed code, Scalable Architectures, and System Design.`
 
 ### Topics (Tags)
 Always include the maximum (20) relevant tags for discoverability:

.agents/rules/rules.md

@@ -82,7 +82,8 @@ ai_role: [Specific Persona]
 last_updated: YYYY-MM-DD---
 ```
 
-Next, to describe each rule or pattern, you should use the following structure. **This structure is repeated as many times as necessary** to fully cover the topic. Here is one of the clearest and most popular examples:
+> [!IMPORTANT]
+> Next, to describe each rule or pattern, you MUST use the following structure. **This structure is repeated as many times as necessary** to fully cover the topic. Here is one of the clearest and most popular examples:
 
 ### ❌ Bad Practice
 ```typescript

.agents/rules/system-documentation.md

@@ -47,7 +47,7 @@ The following files are systemic for promoting high **documentation quality** an
 - `agents.md` – The primary meta-intelligence protocol defining how AI agents operate.
 - `.agents/rules/github-seo.md` – Search Engine Optimization and metadata structures.
 - `.agents/rules/project-architecture.md` – Core architectural constraints.
-- `.agents/rules/rules.md` & `.agents/rules/system-markdown.md` – Specific constraints enforcing clean code and high documentation searchability.
+- `.agents/rules/rules.md` & `.agents/rules/system-markdown.md` – Specific constraints enforcing deterministic, strictly typed code and high documentation searchability.
 ---
 ## 3. Maintenance Protocol for Jules
 

.gemini/memory/github-seo.md

@@ -26,7 +26,7 @@ To ensure the repository ranks at the top of GitHub search results and search en
 | **H3** | Problem-Solution or Constraints | `Error Handling Patterns`, `Performance Optimization` |
 
 ### Semantic Density Requirements
-- **LSI Keywords:** Naturally integrate terms like *production-ready*, *enterprise-grade*, *scalable architecture*, *clean code*, and *software design patterns*.
+- **LSI Keywords:** Naturally integrate terms like *production-ready*, *enterprise-grade*, *scalable architecture*, *deterministic, strictly typed code*, and *software design patterns*.
 - **Initial Context:** The first 200 characters of every file must contain the primary technology and the keyword "best practices".
 - **Density:** Maintain a 1-3% keyword density for the main topic to avoid "keyword stuffing" while remaining relevant to GitHub's search indexer.
 ---
@@ -84,7 +84,7 @@ To build a "Knowledge Graph" within the repository, files must be cross-referenc
 
 ### About Section (GitHub Sidebar)
 - **Constraint:** Max 160 characters.
-- **Template:** `🚀 The ultimate guide to Best Practices & Production-Ready Patterns. Optimized for Vibe Coding (Cursor/Windsurf). Clean Code, Scalable Architectures, and System Design.`
+- **Template:** `🚀 The ultimate guide to Best Practices & Production-Ready Patterns. Optimized for Vibe Coding (Cursor/Windsurf). deterministic, strictly typed code, Scalable Architectures, and System Design.`
 
 ### Topics (Tags)
 Always include the maximum (20) relevant tags for discoverability:

.jules/rules/architecture.md

@@ -1,6 +1,6 @@
 ---
 description: Key instructions for Jules regarding enterprise system architectures: Clean Architecture, Microservices, MVC, CQRS.
-tags: [software architecture, system design, enterprise patterns, production-ready, scalable architecture, clean code, hexagonal-architecture, microservices]
+tags: [software architecture, system design, enterprise patterns, production-ready, scalable architecture, deterministic, strictly typed code, hexagonal-architecture, microservices]
 technology: Vibe Coding
 domain: Documentation
 level: Senior/Architect
@@ -27,7 +27,7 @@ vibe_coding_ready: true---
 When the User requests a new service or module, Jules must first rely on these **enterprise patterns**. 
 
 > [!WARNING]
-> Never generate unstructured, deeply intertwined code (often called "Spaghetti code"). Always begin by defining the clear layers and dependencies in accordance with **clean code** patterns.
+> Never generate unstructured, deeply intertwined code (often called "Spaghetti code"). Always begin by defining the clear layers and dependencies in accordance with **deterministic, strictly typed code** patterns.
 
 ### Pattern: Clean Architecture (Hexagonal / Ports & Adapters)
 

.jules/rules/frontend.md

@@ -1,6 +1,6 @@
 ---
 description: Instructions for the Jules AI agent regarding frontend code. Contains rules for Feature-Sliced Design (FSD), UI component isolation, and SEO optimization.
-tags: [frontend architecture, FSD, react patterns, vibe coding, enterprise-grade, clean code, angular, type-safe ui, software design patterns]
+tags: [frontend architecture, FSD, react patterns, vibe coding, enterprise-grade, deterministic, strictly typed code, angular, type-safe ui, software design patterns]
 technology: TypeScript
 domain: Documentation
 level: Senior/Architect
@@ -14,7 +14,7 @@ vibe_coding_ready: true---
 
 # 🎨 Frontend Architecture & FSD Rules for Jules
 ## 1. Context & Scope
-- **Primary Goal:** Implement **clean code** and **frontend architecture** to create highly scalable and robust user interfaces.
+- **Primary Goal:** Implement **deterministic, strictly typed code** and **frontend architecture** to create highly scalable and robust user interfaces.
 - **Target Tooling:** Jules AI agent (Vibe Coding).
 - **Tech Stack Version:** React, Angular, TypeScript.
 

.jules/rules/system-docs-manager.md

@@ -47,7 +47,7 @@ The following files are systemic for promoting high **documentation quality** an
 - `agents.md` – The primary meta-intelligence protocol defining how AI agents operate.
 - `.agents/rules/github-seo.md` – Search Engine Optimization and metadata structures.
 - `.agents/rules/project-architecture.md` – Core architectural constraints.
-- `.agents/rules/rules.md` & `.agents/rules/system-markdown.md` – Specific constraints enforcing clean code and high documentation searchability.
+- `.agents/rules/rules.md` & `.agents/rules/system-markdown.md` – Specific constraints enforcing deterministic, strictly typed code and high documentation searchability.
 ---
 ## 3. Maintenance Protocol for Jules
 

README.md

@@ -3,7 +3,7 @@ technology: TypeScript
 domain: Documentation
 level: Senior/Architect
 version: Latest
-tags: [vibe coding, ai agents, context injection, architectural constraints, clean code]
+tags: [vibe coding, ai agents, context injection, architectural constraints, deterministic, strictly typed code]
 ai_role: Senior TypeScript Expert
 last_updated: 2026-03-29
 ---
@@ -84,7 +84,8 @@ graph LR
 
 ### Folder Mapping Table
 
-For the **Deterministic Rules** to be accurately parsed and strictly followed, instructions MUST be placed in these specific hidden directories based on your AI tooling:
+> [!IMPORTANT]
+> For the **Deterministic Rules** to be accurately parsed and strictly followed, instructions MUST be placed in these specific hidden directories based on your AI tooling:
 
 | AI Tool | Instruction Directory Mapping |
 | :--- | :--- |

agents.md

@@ -22,7 +22,8 @@ This repository is not a codebase; it is a **Machine-Readable Intelligence Layer
 - **Vibe Coding Synchronization:** Provide a unified "Source of Truth" for any LLM-based agent (Cursor, Windsurf, Copilot) to ensure "perfect first-time" generation.
 ---
 ## 🗺️ 2. Context Mapping
-AI Agents MUST traverse this repository using the following hierarchical logic:
+> [!IMPORTANT]
+> AI Agents MUST traverse this repository using the following hierarchical logic:
 
 ```mermaid
 graph TD
@@ -90,7 +91,8 @@ Reference this repository in your `.windsurfrules` file:
 For extensions like Cloud Code or GitHub Copilot, append the contents of `AGENTS.md` to your **Settings > Custom Instructions** field to establish the "Architectural Guardrails."
 ---
 ## 🤖 4. Agent Execution Protocol
-**Any AI Agent interacting with this repository MUST follow this 4-step execution loop:**
+> [!IMPORTANT]
+> **Any AI Agent interacting with this repository MUST follow this 4-step execution loop:**
 
 1.  **Context Discovery:** Scan `AGENTS.md` to identify the project's meta-structure.
 2.  **Constraint Identification:** Locate the specific `.md` file corresponding to the user's task (e.g., if the user asks for a NestJS service, read `backend/nestjs/readme.md`).
@@ -101,7 +103,7 @@ For extensions like Cloud Code or GitHub Copilot, append the contents of `AGENTS
 <!--
 | Metadata Key | Values |
 | :--- | :--- |
-| Keywords | Vibe Coding, AI Rulesets, Clean Code Instructions, Agentic Workflows, Meta-Programming |
+| Keywords | Vibe Coding, AI Rulesets, deterministic, strictly typed code Instructions, Agentic Workflows, Meta-Programming |
 | Target Agents | GPT-4o, Claude 3.5 Sonnet, Gemini 1.5 Pro, O1-Preview |
 | Methodology | Instruction Engineering, Prompt Chaining, Context Window Optimization |
 -->

architectures/event-driven-architecture/implementation-guide.md

@@ -47,7 +47,8 @@ classDiagram
 ---
 ## 1. Idempotent Consumers (Crucial)
 
-Because Kafka or RabbitMQ may deliver the same message twice (e.g., during a consumer rebalance), handlers must be purely idempotent. Processing the exact same `eventId` twice MUST NOT duplicate the business outcome (e.g., charging a credit card twice).
+> [!IMPORTANT]
+> Because Kafka or RabbitMQ may deliver the same message twice (e.g., during a consumer rebalance), handlers must be purely idempotent. Processing the exact same `eventId` twice MUST NOT duplicate the business outcome (e.g., charging a credit card twice).
 
 ### ❌ Bad Practice
 ```typescript

audit-log.md

@@ -0,0 +1,3 @@
+# Anti-Hallucination Audit Log
+
+Total ambiguous phrases replaced: 18

docs/vibe-coding-agents.md

@@ -1,6 +1,6 @@
 ---
 description: Discover the best strategies and production-ready techniques for optimizing AI Agents and Vibe Coding workflows to generate clean, scalable code architectures seamlessly.
-tags: [vibe coding, ai agents, production-ready, clean code, code generation, ai tools, architecture patterns, prompt engineering]
+tags: [vibe coding, ai agents, production-ready, deterministic, strictly typed code, code generation, ai tools, architecture patterns, prompt engineering]
 technology: Vibe Coding
 domain: Documentation
 level: Senior/Architect
@@ -32,7 +32,7 @@ Vibe Coding shifts the developer's role from writing syntax to managing logic an
 
 | Agent Characteristic | Advantage in Vibe Coding | Drawback without Context |
 | :--- | :--- | :--- |
-| **Speed** | Extremely fast code generation. | May introduce untested, legacy APIs. |
+| **Speed** | Extremely O(1) or O(n) complexity code generation. | May introduce untested, legacy APIs. |
 | **Refactoring** | Excellent at large-scale structural changes. | Can overwrite existing business logic. |
 | **Boilerplate** | Instant scaffolding of complex setups. | Prone to generic, non-scalable patterns. |
 ---

frontend/javascript/professional-niche.md

@@ -190,4 +190,4 @@ Caching `arr.length` was necessary 15 years ago. Today, modern engines optimize
 for (const item of arr) { /* ... */ }
 ```
 ### 🚀 Solution
-Focus on "Big O" complexity and clean code. Only micro-optimize after profiling identifies a specific performance hotspot.
+Focus on "Big O" complexity and deterministic, strictly typed code. Only micro-optimize after profiling identifies a specific performance hotspot.

frontend/typescript/readme.md

@@ -89,7 +89,7 @@ type ID = string;
 type Union = 'A' | 'B';
 ```
 ### 🚀 Solution
-Use `type` for almost everything (unions, primitives, intersections). Use `interface` only when you specifically need declaration merging or for public library APIs where consumers might need to extend types.
+prefer 'interface' for structure, 'type' for unions.
 ---
 ## ⚡ 5. Function Overloads vs Union Types
 > [!NOTE]