feat: enforce prioritizing reading all the rules before agents gets to work

Author: matscode

rules/core-principles.rules.md

@@ -2,6 +2,8 @@
 
 **MANDATORY: ALL CODING AGENTS MUST FOLLOW THIS WORKFLOW**
 
+**CRITICAL PRECEDENCE:** Before executing ANY step in this workflow, agents MUST complete the enforcement requirements defined in [rules/index.rules.md](./index.rules.md) - Enforcement Requirements. NO exceptions.
+
 This file defines the fundamental workflow and core principles that ALL coding agents must follow during any coding session. These are the foundational rules that govern how agents think, research, decide, and implement.
 
 **VIOLATION ENFORCEMENT:** All violations of rules in this file are subject to the universal violation enforcement system defined in [rules/violation-enforcement.rules.md](./violation-enforcement.rules.md).
@@ -111,9 +113,7 @@ This file defines the fundamental workflow and core principles that ALL coding a
 6. **LEGACY CODE VIOLATIONS** - Modifying existing code without following the mandatory legacy code specification workflow defined in [rules/spec-management.rules.md](./spec-management.rules.md)
 
 **VIOLATION CONSEQUENCES:**
-- **FIRST VIOLATION:** Stop immediately, follow proper workflow, restart implementation
-- **REPEATED VIOLATIONS:** Session termination and restart with proper compliance
-- **CRITICAL VIOLATIONS:** Immediate rollback and specification creation before proceeding
+All violations are subject to the universal violation enforcement system defined in [violation-enforcement.rules.md](./violation-enforcement.rules.md).
 
 ---
 

rules/file-caching.rules.md

@@ -259,7 +259,7 @@ edit_file/update_file [with updated current content understanding]
 
 ### Violation Consequences
 
-**CRITICAL VIOLATION** - Violations result in immediate corrective action and rule reload requirement.
+All violations are subject to the universal violation enforcement system defined in [violation-enforcement.rules.md](./violation-enforcement.rules.md).
 
 ---
 

rules/index.rules.md

@@ -6,6 +6,32 @@
 
 ---
 
+## 🚨 ENFORCEMENT REQUIREMENTS
+
+**CRITICAL:** These 4 enforcement requirements take absolute precedence over all other actions:
+
+1. **Reading all required rules takes precedence over any agent action**
+   - NO exceptions - rules must be read before ANY file operations, code changes, or workflow triggers
+   - Agent MUST halt all activities until rule reading is complete
+
+2. **All required rules must be read before acting on any file**
+   - File modifications, creations, deletions FORBIDDEN until rules are read
+   - Includes viewing, editing, or analyzing any project files
+
+3. **All required rules must be read before triggering any rules workflow**
+   - Persona setup, spec creation, violation enforcement FORBIDDEN until rules are read
+   - No workflow exceptions - rules reading is the prerequisite for ALL workflows
+
+4. **All required rules must be read and understood before proceeding with user requests in every new session**
+   - Agent must complete reading all required rules before handling user requests
+   - Rule reading takes precedence over file operations, code changes, or other agent actions
+   - After rule reading completion, agent proceeds with Core Agent Workflow from core-principles.rules.md
+   - Ensures comprehensive rule compliance before proceeding with user requests
+
+**VIOLATION:** Proceeding without reading rules = CRITICAL VIOLATION requiring immediate session restart
+
+---
+
 ## REQUIRED READING
 
 **MANDATORY:** Read ALL rule files in this exact order before any coding session:

rules/interactive-input.rules.md

@@ -61,7 +61,8 @@ Agent **MUST STOP** and ask questions when encountering:
   - Removing working ContactCard component during "cleanup"
 - **CORRECT APPROACH**: Ask "Should I add features like accept/decline buttons?" or "Should I preserve existing [component] or modify it?"
 
-**Violation Consequences**: Acknowledge missed opportunity → ask retroactively → restart session if repeated → rollback if critical
+**Violation Consequences:**
+All violations are subject to the universal violation enforcement system defined in [violation-enforcement.rules.md](./violation-enforcement.rules.md).
 
 ---
 

rules/spec-management.rules.md

@@ -2,6 +2,8 @@
 
 **MANDATORY: ALL AGENTS MUST FOLLOW THESE SPECIFICATION RULES**
 
+**ENFORCEMENT PRECEDENCE:** All specification workflows can ONLY be initiated AFTER completing the enforcement requirements defined in [rules/index.rules.md](./index.rules.md) - Enforcement Requirements. Rule reading takes absolute precedence over spec creation or management.
+
 **VIOLATION ENFORCEMENT:** All violations of rules in this file are subject to the universal violation enforcement system defined in [rules/violation-enforcement.rules.md](./violation-enforcement.rules.md).
 
 ---
@@ -312,9 +314,7 @@ Before creating any specification file, agents MUST ask these questions to ensur
 - Index file updates are CRITICAL - never skip this step
 
 **VIOLATION CONSEQUENCES:**
-- **FIRST VIOLATION:** Stop immediately, create required specification, restart implementation
-- **REPEATED VIOLATIONS:** Session termination and restart with proper spec compliance
-- **CRITICAL VIOLATIONS:** Immediate rollback and specification creation before proceeding
+All violations are subject to the universal violation enforcement system defined in [violation-enforcement.rules.md](./violation-enforcement.rules.md).
 
 ---
 

rules/user-persona.rules.md

@@ -12,6 +12,8 @@ This file defines how coding agents should adapt their communication style and i
 
 **CRITICAL REQUIREMENT: CODING AGENTS MUST HAVE A USER PERSONA SPEC IN MEMORY**
 
+**ENFORCEMENT PRECEDENCE:** This workflow can ONLY be initiated AFTER completing the enforcement requirements defined in [rules/index.rules.md](./index.rules.md) - Enforcement Requirements. Rule reading takes absolute precedence.
+
 **BEFORE ANY CODING SESSION, AGENTS MUST:**
 
 1. **CHECK FOR PERSONA SPEC:** Look for `specs/user-persona.spec.md` 
@@ -135,7 +137,7 @@ CONTINUE with session
 
 ---
 
-## VIOLATION CONSEQUENCES
+## VIOLATION CONSEQUENCES - SINGLE STRIKE SYSTEM
 
 **FAILURE TO SETUP PERSONA:**
 1. **CRITICAL ERROR:** Session cannot proceed without persona spec