feat: improve interactive input

Author: matscode

README.md

@@ -58,8 +58,12 @@ Want just the essentials? Copy these:
 - **Windsurf**: Copy `.windsurf/` folder
 - **Kiro**: Copy `.kiro/` folder
 
-### Activation
-After copying files, **start a new chat** in your editor. The rules activate automatically.
+### Rule Activation
+- Close and reopen project (optional but recommended)
+- Start a new chat
+- Prompt your agent to "Read workspace rules"
+
+**First Time Expectation:** Once rules are read, the user persona creation workflow should be triggered to create your `user-persona.spec.md`
 
 ## 👤 User Persona System
 

rules/interactive-input.rules.md

@@ -144,7 +144,56 @@ echo "Rate: 100%, %d items, %s status. Choice: "
 
 ---
 
-## 🔧 OPERATING SYSTEM DETECTION
+## 🔍 CRITICAL DISTINCTION: DISPLAY TEXT vs INTERACTIVE INPUT
+
+**AGENTS MUST UNDERSTAND THE DIFFERENCE:**
+
+### 📺 DISPLAY-ONLY TEXT
+**Purpose**: Show information, status, or messages WITHOUT expecting user input
+**Format**: Simple `echo` commands
+**Requirements**: 
+- **MANDATORY**: Must end with "Press Enter to continue" or "Type what you'd like to change"
+- **MANDATORY**: Must use `read` to wait for user acknowledgment before proceeding
+- **NO INPUT CAPTURE**: User response is not stored or processed
+
+**EXAMPLE - DISPLAY ONLY** (DO NOT EXECUTE - FOR REFERENCE ONLY):
+```bash
+echo -e "\n\n✅ TASK COMPLETED\n\nI have successfully implemented the requested feature.\n\nPress Enter to continue or type what you'd like to change: "; read acknowledgment
+```
+
+### 🎯 INTERACTIVE INPUT
+**Purpose**: Ask questions and CAPTURE user responses for decision-making
+**Format**: Interactive `echo` with `read` and confirmation
+**Requirements**:
+- **MANDATORY**: Must capture user input with `read answer`
+- **MANDATORY**: Must confirm selection with `echo "You selected: $answer"`
+- **MANDATORY**: Must include 2 leading empty lines
+- **INPUT PROCESSING**: User response is stored and used for logic
+
+**EXAMPLE - INTERACTIVE INPUT** (DO NOT EXECUTE - FOR REFERENCE ONLY):
+```bash
+echo -e "\n\nChoose your option (1/2/3): "; read answer; echo "You selected: $answer"
+```
+
+### 🚨 CRITICAL VIOLATIONS
+- **DISPLAY AS INTERACTIVE**: Using display text format for questions that need answers
+- **INTERACTIVE AS DISPLAY**: Using interactive format for simple information display
+- **MISSING ACKNOWLEDGMENT**: Display text without "Press Enter" or user acknowledgment
+- **MISSING CONFIRMATION**: Interactive input without "You selected" confirmation
+
+### 🔄 KEY BEHAVIORAL DIFFERENCE
+
+**DISPLAY-ONLY TEXT BEHAVIOR:**
+- **Empty Input (Enter/Exit)**: Agent CONTINUES with tasks - this is expected behavior
+- **User Types Something**: Agent PROCESSES that input as feedback/modifications
+- **Purpose**: Allow user to acknowledge completion OR provide feedback
+
+**INTERACTIVE INPUT BEHAVIOR:**
+- **Empty Input**: Agent CAN ask user to provide input again (validation)
+- **User Types Something**: Agent PROCESSES that input as the answer to the question
+- **Purpose**: Capture specific user decisions for logic flow
+
+---
 
 **CRITICAL EXECUTION RULE**: When user input is required, you **MUST EXECUTE** the interactive command using the `run_command` tool, **NEVER** display it as text or code block.
 
@@ -309,8 +358,9 @@ echo -e "\n\nBall color: "; read color; echo -e "\n\nSize (small/medium/large):
 
 1. **Early Clarification** - Ask questions at task start, resolve ambiguities before coding
 2. **Feature Scope Verification** - MUST confirm before adding ANY feature not explicitly requested
-3. **Provide Rationale** - Always explain why questions matter, help weigh trade-offs
-4. **Respect User Decisions** - User choice is final, no exceptions
+3. **Display Text Acknowledgment** - ALL display-only text MUST require user acknowledgment before proceeding
+4. **Provide Rationale** - Always explain why questions matter, help weigh trade-offs
+5. **Respect User Decisions** - User choice is final, no exceptions
 5. **Document Decisions** - Ask before codifying new standards
 6. **File Content Verification** - Re-read all relevant files before making implementation decisions
 7. **Fresh Content Protocol** - Never base interactive questions on stale file content or cached understanding
@@ -343,6 +393,11 @@ echo -e "\n\nBall color: "; read color; echo -e "\n\nSize (small/medium/large):
 - [ ] Validated implementation scope matches user request?
 - [ ] Asked if user wants modifications?
 
+**For ALL display-only text:**
+- [ ] Included "Press Enter to continue" or "Type what you'd like to change"?
+- [ ] Used `read` to wait for user acknowledgment?
+- [ ] Avoided proceeding without user acknowledgment?
+
 **REFACTORING-SPECIFIC CHECKLIST:**
 - [ ] Preserved ALL original functionality?
 - [ ] Maintained existing component behavior?

rules/user-persona.rules.md

@@ -4,19 +4,19 @@
 
 This file defines how coding agents should adapt their communication style and interaction approach based on the user's experience level and preferences.
 
-**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).
+**VIOLATION ENFORCEMENT:** All violations of rules in this file are subject to the universal violation enforcement system defined in [`violation-enforcement.rules.md`](./violation-enforcement.rules.md).
 
 ---
 
 ## MANDATORY USER PERSONA SETUP
 
 **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.
+**ENFORCEMENT PRECEDENCE:** This workflow can ONLY be initiated AFTER completing the enforcement requirements defined in [`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` 
+1. **CHECK FOR PERSONA SPEC:** Look for [`specs/user-persona.spec.md`](../specs/user-persona.spec.md) 
 2. **FORCE PERSONA SETUP:** If no spec exists, STOP and initiate persona setup workflow
 3. **LOAD PERSONA:** Read and apply persona settings to all interactions
 4. **NEVER ASSUME:** Do not assume any default persona - always require explicit setup
@@ -26,47 +26,74 @@ This file defines how coding agents should adapt their communication style and i
 ## PERSONA DETECTION WORKFLOW
 
 ### Step 1: Check for Existing Persona
-```
-IF specs/user-persona.spec.md EXISTS:
-  READ persona specifications
-  LOAD into memory for session
-  CONTINUE with adapted approach
-ELSE:
-  INITIATE persona setup workflow (Step 2)
-```
+
+**MANDATORY REQUIREMENT:** Agent MUST check for [`specs/user-persona.spec.md`](../specs/user-persona.spec.md) before ANY coding session.
+
+**IF PERSONA EXISTS:**
+- READ persona specifications immediately
+- LOAD into memory for current session
+- CONTINUE with persona-adapted communication approach (Step 1: PERSONA ASSIMILATION of [`core-principles.rules.md`](./core-principles.rules.md))
+
+**IF PERSONA MISSING:**
+- **CRITICAL STOP:** Agent MUST NOT proceed with coding
+- **MANDATORY ACTION:** Initiate persona setup workflow (Step 2)
+- **VIOLATION:** Proceeding without persona = CRITICAL FAILURE
 
 ### Step 2: Present Persona Options
-```
-READ specs/user-personas/ directory to discover available predefined options
-PRESENT available options:
-1. Predefined personas (list discovered options from directory)
-2. Custom persona option
 
-WAIT for user selection following **USE `run_command` TOOL** for all questions - **MUST FOLLOW** [rules/interactive-input.rules.md](./interactive-input.rules.md) for context on using run_command tool
+**MANDATORY ACTIONS:**
+1. **READ DIRECTORY:** Scan [`specs/user-personas/`](../specs/user-personas/) for available predefined personas
+2. **PRESENT OPTIONS:** Use MANDATORY interactive input format per [`interactive-input.rules.md`](./interactive-input.rules.md)
+3. **CAPTURE SELECTION:** Store user choice for processing
+
+**CRITICAL REQUIREMENT:** MUST use run_command tool with proper interactive format:
+
+**EXAMPLE FORMAT (DO NOT EXECUTE - FOR REFERENCE ONLY):**
+```bash
+echo -e "\n\n🔧 PERSONA SETUP REQUIRED\n\n[persona options]\n\nWhich option best describes you? (Enter 1-6): "; read answer; echo "You selected: $answer"
 ```
 
+**⚠️ IMPORTANT:** This is ONLY an example of the expected format structure. Agents MUST follow the complete interactive input workflow detailed in [`interactive-input.rules.md`](./interactive-input.rules.md) for proper implementation.
+
+**VIOLATION:** Using echo without read capture = CRITICAL FAILURE
+
 ### Step 3: Handle User Selection
-```
-IF user selects predefined persona:
-  COPY selected persona to specs/user-persona.spec.md
-  LOAD persona settings
-  CONTINUE with session
 
-IF user selects custom option:
-  INITIATE interactive persona creation (Step 4)
-```
+**FOR PREDEFINED PERSONA SELECTION:**
+- **COPY PERSONA:** Transfer selected persona file to [`specs/user-persona.spec.md`](../specs/user-persona.spec.md)
+- **LOAD SETTINGS:** Import persona specifications into memory
+- **CONTINUE SESSION:** Proceed with persona-adapted approach (Step 1: PERSONA ASSIMILATION of [`core-principles.rules.md`](./core-principles.rules.md))
+
+**FOR CUSTOM PERSONA REQUEST:**
+- **INITIATE CREATION:** Begin interactive persona creation workflow (Step 4)
+- **FOLLOW TEMPLATE:** Use structured approach for consistency
 
 ### Step 4: Interactive Persona Creation
-```
-READ rules/templates/persona.template.md for required fields and structure
-ASK user questions based on persona template following **USE `run_command` TOOL** for all questions - **MUST FOLLOW** [rules/interactive-input.rules.md](./interactive-input.rules.md) for context on using run_command tool:
+
+**MANDATORY PREPARATION:**
+1. **READ TEMPLATE:** Load [`rules/templates/persona.template.md`](./templates/persona.template.md) for required fields
+2. **STRUCTURE QUESTIONS:** Base all questions on template requirements
+3. **USE INTERACTIVE FORMAT:** Follow [`interactive-input.rules.md`](./interactive-input.rules.md) exactly
+
+**CRITICAL REQUIREMENT:** Each question MUST use run_command tool with proper format:
+
+**EXAMPLE FORMAT** (DO NOT EXECUTE - FOR REFERENCE ONLY):
+echo -e "\n\n[Question]: "; read answer; echo "You selected: $answer"
+
+**⚠️ IMPORTANT:** This is ONLY an example of the expected format structure. Agents MUST follow the complete interactive input workflow detailed in [`interactive-input.rules.md`](./interactive-input.rules.md) for proper implementation, including proper `run_command` tool usage, user input capture with `read`, response confirmation, and all formatting and execution requirements.
+
+**REQUIRED QUESTIONS:**
 1. Role (their primary job function)
 2. Experience Level (none, enthusiast, beginner, intermediate, senior, expert)
 
-CREATE specs/user-persona.spec.md with responses
-LOAD persona settings
-CONTINUE with session
-```
+**VIOLATION:** Using echo without read capture = CRITICAL FAILURE
+**ENFORCEMENT:** Follow [`interactive-input.rules.md`](./interactive-input.rules.md) exactly - NO exceptions
+
+**COMPLETION ACTIONS:**
+1. **GENERATE SPEC:** Create persona specification from user responses
+2. **SAVE FILE:** Write to [`specs/user-persona.spec.md`](../specs/user-persona.spec.md)
+3. **LOAD PERSONA:** Import settings into memory
+4. **CONTINUE SESSION:** Proceed with persona-adapted approach
 
 ---
 

rules/violation-enforcement.rules.md

@@ -51,6 +51,11 @@
 34. **Acting on files before completing mandatory rule reading** → 🚨 EMERGENCY STOP immediately, acknowledge CRITICAL precedence violation, complete rule reading first *(See: [index.rules.md](./index.rules.md) - Enforcement Requirements)*
 35. **Triggering workflows before reading all required rules** → 🚨 EMERGENCY STOP immediately, acknowledge CRITICAL workflow violation, complete rule reading before any workflow *(See: [index.rules.md](./index.rules.md) - Enforcement Requirements)*
 36. **Failing to queue and prioritize multiple workflows after rule reading** → 🚨 EMERGENCY STOP immediately, acknowledge CRITICAL queuing violation, implement systematic workflow processing *(See: [index.rules.md](./index.rules.md) - Enforcement Requirements)*
+37. **Using echo without read capture during persona setup** → 🚨 EMERGENCY STOP immediately, acknowledge CRITICAL interactive input violation, restart with proper format *(See: [user-persona.rules.md](./user-persona.rules.md) - Interactive Input Violations)*
+38. **Displaying persona questions as text instead of executing** → 🚨 EMERGENCY STOP immediately, acknowledge CRITICAL execution failure, use run_command tool *(See: [user-persona.rules.md](./user-persona.rules.md) - Interactive Input Violations)*
+39. **Missing 2 leading empty lines in persona setup commands** → 🚨 EMERGENCY STOP immediately, acknowledge CRITICAL formatting violation, add proper formatting *(See: [user-persona.rules.md](./user-persona.rules.md) - Interactive Input Violations)*
+40. **Using display text without user acknowledgment** → 🚨 EMERGENCY STOP immediately, acknowledge CRITICAL acknowledgment violation, add "Press Enter to continue" *(See: [interactive-input.rules.md](./interactive-input.rules.md) - Display Text vs Interactive Input)*
+41. **Proceeding after display text without waiting for user** → 🚨 EMERGENCY STOP immediately, acknowledge CRITICAL flow violation, wait for user acknowledgment *(See: [interactive-input.rules.md](./interactive-input.rules.md) - Display Text vs Interactive Input)*
 
 ---