Normalize docs-extractor audience tags; remove admin/stakeholder; strip tool invocations (#8717)

docs(extractor): normalize audience to type="user"; remove admin/stakeholder; strip tool invocation examples

.roo/rules-docs-extractor/1_extraction_workflow.xml

@@ -1,296 +1,99 @@
 <extraction_workflow>
   <mode_overview>
-    The Docs Extractor mode has two primary functions:
-    1. Extract technical and non-technical details about features to provide to documentation teams
-    2. Verify existing documentation for factual accuracy against the codebase
-    
-    This mode does not generate final documentation but provides detailed analysis and verification.
+    The Docs Extractor mode has exactly two workflow paths:
+    1) Verify provided documentation for factual accuracy against the codebase
+    2) Generate source material for user-facing docs about a requested feature or aspect of the codebase
+
+    Outputs are designed to support explanatory documentation (not merely descriptive):
+    - Capture why users need steps and why certain actions are restricted
+    - Surface constraints, limitations, and trade‑offs
+    - Provide troubleshooting playbooks (symptoms → causes → fixes → prevention)
+    - Recommend targeted visuals for complex states (not step‑by‑step screenshots)
+
+    This mode does not generate final user documentation; it produces verification and source-material reports for docs teams.
   </mode_overview>
 
   <initialization_phase>
     <step number="1">
       <title>Parse Request</title>
       <actions>
-        <action>Identify the feature or component in the user's request.</action>
-        <action>Determine if the request is for extraction or verification.</action>
-        <action>For extraction: Note what level of detail is needed (technical vs non-technical).</action>
-        <action>For verification: Identify the documentation to be verified.</action>
+        <action>Identify the feature/aspect in the user's request.</action>
+        <action>Decide path: verification vs. source-material generation.</action>
+        <action>For source-material: capture audience (user or developer) and depth (overview vs task-focused).</action>
+        <action>For verification: identify the documentation to be verified (provided text/links/files).</action>
         <action>Note any specific areas to emphasize or check.</action>
       </actions>
-      <note>The mode branches into extraction or verification based on the request.</note>
     </step>
 
     <step number="2">
       <title>Discover Feature</title>
       <actions>
-        <action>Locate relevant code using appropriate search methods.</action>
-        <action>Identify entry points and components.</action>
-        <action>Map the high-level architecture.</action>
-        <action>Use any combination of tools to understand the feature.</action>
+        <action>Locate relevant code and assets using appropriate discovery methods.</action>
+        <action>Identify entry points and key components that affect user experience.</action>
+        <action>Map the high-level workflow a user follows.</action>
       </actions>
-      <note>Use the most effective discovery method for the situation - file exploration, search, or direct navigation.</note>
     </step>
   </initialization_phase>
 
-  <analysis_phases>
-    <phase name="code_analysis">
-      <title>Code Analysis</title>
-      <steps>
-        <step>
-          <action>Analyze code structure</action>
-          <details>
-            - Identify classes, functions, modules
-            - Extract method signatures, parameters
-            - Document return types, data structures
-            - Map inheritance and composition
-          </details>
-        </step>
-        <step>
-          <action>Extract APIs</action>
-          <details>
-            - REST endpoints
-            - GraphQL schemas
-            - WebSocket events
-            - RPC interfaces
-          </details>
-        </step>
-        <step>
-          <action>Document configuration</action>
-          <details>
-            - Environment variables
-            - Config files and schemas
-            - Feature flags
-            - Runtime parameters
-          </details>
-        </step>
-      </steps>
-    </phase>
-
-    <phase name="ui_ux_analysis">
-      <title>UI/UX and User Experience Analysis</title>
-      <steps>
-        <step>
-          <action>Analyze user interface components</action>
-          <details>
-            - UI components and their interactions
-            - Forms, buttons, navigation elements
-            - Visual feedback and loading states
-            - Responsive design considerations
-            - Accessibility features
-          </details>
-        </step>
-        <step>
-          <action>Map user journeys and interactions</action>
-          <details>
-            - Step-by-step user workflows
-            - Click paths and navigation flows
-            - User decision points
-            - Input validation and error messaging
-            - Success and failure scenarios
-          </details>
-        </step>
-        <step>
-          <action>Document user experience elements</action>
-          <details>
-            - Page layouts and information architecture
-            - Interactive elements and their behaviors
-            - Tooltips, help text, and guidance
-            - Confirmation dialogs and warnings
-            - Progress indicators and status updates
-          </details>
-        </step>
-        <step>
-          <action>Capture visual and behavioral patterns</action>
-          <details>
-            - Color schemes and theming
-            - Animation and transitions
-            - Keyboard shortcuts and accessibility
-            - Mobile vs desktop experiences
-            - Browser-specific considerations
-          </details>
-        </step>
-      </steps>
-    </phase>
-
-    <phase name="business_logic_analysis">
-      <title>Business Logic Extraction</title>
-      <steps>
-        <step>
-          <action>Map workflows from user perspective</action>
-          <details>
-            - User journey through the feature
-            - Decision points and branching
-            - State transitions visible to users
-            - Roles and permissions affecting UI
-          </details>
-        </step>
-        <step>
-          <action>Document business rules</action>
-          <details>
-            - Validation logic and user feedback
-            - Formulas and algorithms
-            - Business process implementations
-            - Compliance requirements
-          </details>
-        </step>
-        <step>
-          <action>Identify use cases</action>
-          <details>
-            - Primary use cases
-            - Edge cases
-            - Error scenarios and user recovery
-            - Performance factors affecting UX
-          </details>
-        </step>
-      </steps>
-    </phase>
-
-    <phase name="integration_analysis">
-      <title>Dependency Analysis</title>
-      <steps>
-        <step>
-          <action>Map dependencies</action>
-          <details>
-            - Third-party libraries
-            - External services and APIs
-            - Database connections
-            - Message queues
-          </details>
-        </step>
-        <step>
-          <action>Document integration points</action>
-          <details>
-            - Incoming webhooks
-            - Outgoing API calls
-            - Event publishers/subscribers
-            - Shared data stores
-          </details>
-        </step>
-        <step>
-          <action>Analyze data flow</action>
-          <details>
-            - Data sources and formats
-            - Data transformations
-            - Output formats and destinations
-            - Data retention policies
-          </details>
-        </step>
-      </steps>
-    </phase>
-
-    <phase name="quality_analysis">
-      <title>Test Analysis</title>
-      <steps>
-        <step>
-          <action>Assess test coverage</action>
-          <details>
-            - Unit test coverage
-            - Integration test scenarios
-            - End-to-end test flows
-            - Performance test results
-          </details>
-        </step>
-        <step>
-          <action>Document error handling</action>
-          <details>
-            - Error types and codes
-            - Exception handling
-            - Fallback mechanisms
-            - Recovery procedures
-          </details>
-        </step>
-        <step>
-          <action>Identify quality metrics</action>
-          <details>
-            - Code complexity
-            - Performance benchmarks
-            - Security vulnerabilities
-            - Maintainability scores
-          </details>
-        </step>
-      </steps>
-    </phase>
-
-    <phase name="security_analysis">
-      <title>Security Analysis</title>
-      <steps>
-        <step>
-          <action>Document security</action>
-          <details>
-            - Auth mechanisms
-            - Access control
-            - Data encryption
-            - Security policies
-          </details>
-        </step>
-        <step>
-          <action>Identify vulnerabilities</action>
-          <details>
-            - Known security issues
-            - Attack vectors
-            - Mitigation
-            - Best practices
-          </details>
-        </step>
-        <step>
-          <action>Check compliance</action>
-          <details>
-            - Regulatory compliance (GDPR, etc.)
-            - Industry standards
-            - Audit trail requirements
-            - Data privacy
-          </details>
-        </step>
-      </steps>
-    </phase>
-  </analysis_phases>
+  <analysis_focus>
+    <area>UI components and their interactions</area>
+    <area>User workflows and decision points</area>
+    <area>Configuration that changes user-visible behavior</area>
+    <area>Error states, messages, and recovery</area>
+    <area>Benefits, limits, prerequisites, and version notes</area>
+    <area>Why this exists: user goals, constraints, and design intent</area>
+    <area>“Cannot do” boundaries: permissions, invariants, and business rules</area>
+    <area>Troubleshooting: symptoms, likely causes, diagnostics, fixes, prevention</area>
+    <area>Common pitfalls and anti‑patterns (what to avoid and why)</area>
+    <area>Decision rationale and trade‑offs that affect user choices</area>
+    <area>Complex UI states that merit visuals (criteria for screenshots/diagrams)</area>
+  </analysis_focus>
 
   <workflow_paths>
-    <path name="extraction">
-      <title>Extract Feature Details</title>
-      <description>Analyze and extract comprehensive details for documentation team</description>
+    <path name="source_material">
+      <title>Generate Source Material for User-Facing Docs</title>
+      <description>Extract concise, user-oriented facts and structure them for documentation teams.</description>
       <steps>
         <step number="1">
-          <title>Compile Technical Details</title>
+          <title>Scope and Audience</title>
           <actions>
-            <action>List all technical components and their relationships</action>
-            <action>Document APIs, data structures, and algorithms</action>
-            <action>Extract configuration options and their impacts</action>
-            <action>Identify error handling and edge cases</action>
-            <action>Note performance characteristics and limitations</action>
+            <action>Confirm the feature/aspect and intended audience.</action>
+            <action>List primary tasks the audience performs with this feature.</action>
           </actions>
         </step>
         <step number="2">
-          <title>Extract Non-Technical Information</title>
+          <title>Extract User-Facing Facts</title>
           <actions>
-            <action>Describe complete user experience and workflows</action>
-            <action>Document UI interactions and visual elements</action>
-            <action>Explain business logic in plain language</action>
-            <action>Identify user benefits and use cases</action>
-            <action>Document common scenarios with UI context</action>
-            <action>Note prerequisites and user-facing dependencies</action>
-            <action>Capture error messages and user guidance</action>
+            <action>Summarize what the feature does and key benefits.</action>
+            <action>Explain why users need this (jobs-to-be-done, outcomes) and when to use it.</action>
+            <action>Document step-by-step user workflows and UI interactions.</action>
+            <action>Capture configuration options that impact user behavior (name, default, effect).</action>
+            <action>Clarify constraints, limits, and “cannot do” cases with rationale.</action>
+            <action>Identify common pitfalls and anti-patterns; include “Do/Don’t” guidance.</action>
+            <action>List common errors with user-facing messages, diagnostics, fixes, and prevention.</action>
+            <action>Record prerequisites, permissions, and compatibility/version notes.</action>
+            <action>Flag complex states that warrant visuals (what to show and why), not every step.</action>
           </actions>
         </step>
         <step number="3">
-          <title>Create Extraction Report</title>
+          <title>Create Source Material Report</title>
           <actions>
-            <action>Organize findings into clear categories</action>
-            <action>Separate technical and non-technical information</action>
-            <action>Include code snippets and examples where helpful</action>
-            <action>Create `EXTRACTION-[feature].md` with findings</action>
-            <action>Highlight areas that need special attention in documentation</action>
+            <action>Organize findings using user-focused structure (benefits, use cases, how it works, configuration, FAQ, troubleshooting).</action>
+            <action>Include short code/UI snippets or paths where relevant.</action>
+            <action>Create `EXTRACTION-[feature].md` with findings.</action>
+            <action>Highlight items that need visuals (screenshots/diagrams).</action>
           </actions>
           <output_format>
-            - Executive summary of the feature
-            - UI/UX analysis and user experience
-            - Technical details section
-            - Non-technical/user-facing details
+            - Executive summary of the feature/aspect
+            - Why it matters (goals, value, when to use)
             - User workflows and interactions
-            - Configuration and setup information
-            - Common use cases with UI context
-            - Error handling and user guidance
-            - Potential documentation considerations
+            - Configuration and setup affecting users (with defaults and impact)
+            - Constraints and limitations (with rationale)
+            - Common scenarios and troubleshooting playbooks (symptoms → causes → fixes → prevention)
+            - Do/Don’t and anti‑patterns
+            - Recommended visuals (what complex states to illustrate and why)
+            - FAQ and tips
+            - Version/compatibility notes
           </output_format>
         </step>
       </steps>
@@ -298,44 +101,43 @@
 
     <path name="verification">
       <title>Verify Documentation Accuracy</title>
-      <description>Check existing documentation against codebase reality</description>
+      <description>Check provided documentation against codebase reality and actual UX.</description>
       <steps>
         <step number="1">
           <title>Analyze Provided Documentation</title>
           <actions>
-            <action>Parse the documentation to identify claims and descriptions</action>
-            <action>Extract technical specifications mentioned</action>
-            <action>Note user-facing features and workflows described</action>
-            <action>Identify configuration options and examples provided</action>
+            <action>Parse the documentation to identify claims and descriptions.</action>
+            <action>Extract technical or user-facing specifics mentioned.</action>
+            <action>Note workflows, configuration, and examples described.</action>
           </actions>
         </step>
         <step number="2">
           <title>Verify Against Codebase</title>
           <actions>
-            <action>Check technical claims against actual implementation</action>
-            <action>Verify API endpoints, parameters, and responses</action>
-            <action>Confirm configuration options and defaults</action>
-            <action>Validate code examples and snippets</action>
-            <action>Check if described workflows match implementation</action>
+            <action>Check claims against actual implementation and UX.</action>
+            <action>Verify endpoints/parameters if referenced.</action>
+            <action>Confirm configuration options and defaults.</action>
+            <action>Validate code snippets and examples.</action>
+            <action>Ensure described workflows match implementation.</action>
           </actions>
         </step>
         <step number="3">
           <title>Create Verification Report</title>
           <actions>
-            <action>Categorize findings by severity (Critical, Major, Minor)</action>
-            <action>List all inaccuracies with correct information</action>
-            <action>Identify missing important information</action>
-            <action>Note outdated or deprecated content</action>
-            <action>Provide specific corrections and suggestions</action>
-            <action>Create `VERIFICATION-[feature].md` with findings</action>
+            <action>Categorize findings by severity (Critical, Major, Minor).</action>
+            <action>List inaccuracies with the correct information.</action>
+            <action>Identify missing important information.</action>
+            <action>Provide specific corrections and suggestions.</action>
+            <action>Create `VERIFICATION-[feature].md` with findings.</action>
           </actions>
           <output_format>
             - Verification summary (Accurate/Needs Updates)
             - Critical inaccuracies that could mislead users
-            - Technical corrections needed
-            - Missing information that should be added
+            - Corrections and missing information
+            - Explanatory gaps (missing “why”, constraints, or decision rationale)
+            - Troubleshooting coverage gaps (missing symptoms/diagnostics/fixes/prevention)
+            - Visual recommendations (which complex states warrant screenshots/diagrams)
             - Suggestions for clarity improvements
-            - Overall recommendations
           </output_format>
         </step>
       </steps>
@@ -343,13 +145,13 @@
   </workflow_paths>
 
   <completion_criteria>
-    <for_extraction>
-      <criterion>All code paths analyzed</criterion>
-      <criterion>Technical details comprehensively extracted</criterion>
-      <criterion>Non-technical information clearly explained</criterion>
-      <criterion>Use cases and examples provided</criterion>
+    <for_source_material>
+      <criterion>Audience and scope captured</criterion>
+      <criterion>User workflows and UI interactions documented</criterion>
+      <criterion>User-impacting configuration recorded</criterion>
+      <criterion>Common errors and troubleshooting documented</criterion>
       <criterion>Report organized for documentation team use</criterion>
-    </for_extraction>
+    </for_source_material>
     <for_verification>
       <criterion>All documentation claims verified</criterion>
       <criterion>Inaccuracies identified and corrected</criterion>

.roo/rules-docs-extractor/2_documentation_patterns.xml

@@ -4,7 +4,7 @@
   </overview>
 
   <output_structure>
-    <user_focused_template><![CDATA[
+    <user_focused_template>
 # [Feature Name]
 
 [Description of what the feature does and why a user should care.]
@@ -22,7 +22,7 @@
 - [Pain point 1]
 - [Pain point 2]
 
-**With this feature]**: [Description of the new experience.]
+**With this feature**: [Description of the new experience.]
 
 ## How it Works
 
@@ -58,9 +58,9 @@
 - [Answer.]
 - [Optional tip.]
 
-    ]]></user_focused_template>
+    </user_focused_template>
 
-    <comprehensive_template><![CDATA[
+    <comprehensive_template>
 # [Feature Name] Technical Documentation
 
 ## Table of Contents
@@ -71,28 +71,27 @@
 5. Configuration
 6. User Guide
 7. Developer Guide
-8. Administrator Guide
-9. Security
-10. Performance
-11. Troubleshooting
-12. FAQ
-13. Changelog
-14. References
-
-[This template remains available for generating detailed technical documentation.]
-    ]]></comprehensive_template>
+8. Security
+9. Performance
+10. Troubleshooting
+11. FAQ
+12. Changelog
+13. References
+
+[Use this as an internal source-material outline for technical sections; not for final docs.]
+    </comprehensive_template>
   </output_structure>
 
   <documentation_patterns>
     <before_after>
-      <template><![CDATA[
+      <template>
 **Before**: Multiple, sequential file read requests:
 - "Read `src/app.js`?" → Approve
 - "Read `src/utils.js`?" → Approve
 - "Read `src/config.json`?" → Approve
 
 **Now**: One request to read all related files.
-      ]]></template>
+      </template>
     </before_after>
 
     <visual_separator>
@@ -101,7 +100,7 @@
     </visual_separator>
 
     <faq>
-      <template><![CDATA[
+      <template>
 ## FAQ
 
 **"Why disable this?"**
@@ -113,7 +112,7 @@
 - Roo reads approved files and works with what it has.
 - `.rooignore` files are excluded automatically.
 - Individual files can still be denied in the batch dialog.
-      ]]></template>
+      </template>
     </faq>
 
     <examples>
@@ -123,7 +122,7 @@
     </examples>
 
     <troubleshooting>
-      <template><![CDATA[
+      <template>
 ## Troubleshooting
 
 **"Too many files requested"**
@@ -134,22 +133,22 @@
 - Ensure "Enable concurrent file reads" is on in settings.
 - Verify the file limit is set correctly (default: 100).
 - Some AI models may not support this feature.
-      ]]></template>
+      </template>
     </troubleshooting>
 
     <help>
-      <template><![CDATA[
+      <template>
 ## Help
 
 - See the [FAQ](#faq) for common issues.
 - Report problems on [GitHub Issues](https://github.com/RooCodeInc/Roo-Code/issues).
 - Include reproduction steps and error messages.
-      ]]></template>
+      </template>
     </help>
   </documentation_patterns>
 
   <audience_sections>
-    <audience type="end_user">
+    <audience type="user">
       <focus>
         <area>Tutorials</area>
         <area>Use cases</area>
@@ -179,60 +178,31 @@
       </style>
     </audience>
 
-    <audience type="administrator">
-      <focus>
-        <area>Deployment</area>
-        <area>Monitoring</area>
-        <area>Security hardening</area>
-        <area>Backup and recovery</area>
-      </focus>
-      <style>
-        <guideline>Operational focus</guideline>
-        <guideline>CLI examples</guideline>
-        <guideline>Automation opportunities</guideline>
-        <guideline>Security and compliance</guideline>
-      </style>
-    </audience>
-
-    <audience type="stakeholder">
-      <focus>
-        <area>Business value</area>
-        <area>Capabilities and limits</area>
-        <area>Competitive advantages</area>
-        <area>Risk assessment</area>
-      </focus>
-      <style>
-        <guideline>Business language</guideline>
-        <guideline>Metrics and KPIs</guideline>
-        <guideline>Strategic benefits</guideline>
-        <guideline>Executive summaries</guideline>
-      </style>
-    </audience>
   </audience_sections>
 
   <metadata_patterns>
     <version_info>
-      <template><![CDATA[
+      <template>
 ### Version Compatibility
 | Component | Min | Recommended | Max | Notes |
 |-----------|-----|-------------|-----|-------|
 | [Component] | [version] | [version] | [version] | [notes] |
-      ]]></template>
+      </template>
     </version_info>
 
     <deprecation_notice>
-      <template><![CDATA[
+      <template>
 > ⚠️ **Deprecated**
 >
 > Deprecated since: [vX.Y.Z] on [date]
 > Removal target: [vA.B.C]
 > Migration: See [migration guide](#migration).
 > Replacement: [new feature/method].
-      ]]></template>
+      </template>
     </deprecation_notice>
 
     <security_warning>
-      <template><![CDATA[
+      <template>
 > 🔒 **Security Warning**
 >
 > [Description of concern]
@@ -240,24 +210,24 @@
 > - **Affected**: [versions]
 > - **Mitigation**: [steps]
 > - **References**: [links]
-      ]]></template>
+      </template>
     </security_warning>
 
     <performance_note>
-      <template><![CDATA[
+      <template>
 > ⚡ **Performance Note**
 >
 > [Description of performance consideration]
 > - **Impact**: [metrics]
 > - **Optimization**: [approach]
 > - **Trade-offs**: [considerations]
-      ]]></template>
+      </template>
     </performance_note>
   </metadata_patterns>
 
   <code_documentation_patterns>
     <api_endpoint>
-      <template><![CDATA[
+      <template>
 ### `[METHOD] /api/[path]`
 
 **Description**: [What this endpoint does]
@@ -299,11 +269,11 @@ curl -X [METHOD] https://api.example.com/[path] \
   -H "Content-Type: application/json" \
   -d '{"field": "value"}'
 ```
-      ]]></template>
+      </template>
     </api_endpoint>
 
     <function_documentation>
-      <template><![CDATA[
+      <template>
 ### `functionName(parameters)`
 
 **Purpose**: [What this function does]
@@ -326,11 +296,11 @@ const result = functionName(value1, value2);
 **Notes**:
 - [Important consideration 1]
 - [Important consideration 2]
-      ]]></template>
+      </template>
     </function_documentation>
 
     <configuration_option>
-      <template><![CDATA[
+      <template>
 ### `CONFIG_NAME`
 
 **Type**: `string | number | boolean`
@@ -352,7 +322,7 @@ config:
 ```
 
 **Impact**: [What changes when this is modified]
-      ]]></template>
+      </template>
     </configuration_option>
   </code_documentation_patterns>
 
@@ -368,20 +338,20 @@ config:
     </external_link>
 
     <related_feature>
-      <template><![CDATA[
+      <template>
 > 📌 **Related Features**
 > - [Feature A](../feature-a/README.md): [How it relates]
 > - [Feature B](../feature-b/README.md): [How it relates]
-      ]]></template>
+      </template>
     </related_feature>
 
     <see_also>
-      <template><![CDATA[
+      <template>
 > 👉 **See Also**
 > - [Related Topic 1](#anchor1)
 > - [Related Topic 2](#anchor2)
 > - [External Resource](https://example.com)
-      ]]></template>
+      </template>
     </see_also>
   </cross_reference_patterns>
 </documentation_patterns>

.roo/rules-docs-extractor/3_analysis_techniques.xml

@@ -1,55 +1,40 @@
 <analysis_techniques>
   <overview>
-    Techniques for analyzing code to extract documentation.
+    Heuristics for analyzing a codebase to extract reliable, user-facing documentation.
+    This file contains technique checklists only—no tool instructions or invocations.
   </overview>
 
   <ui_ux_analysis_techniques>
     <technique name="component_discovery">
-      <description>
-        Find and analyze UI components and their interactions
-      </description>
-      <discovery_methods>
-        <method name="component_search">
-          <description>Search for UI component files</description>
-          <example><![CDATA[
-<!-- Find React/Vue/Angular components -->
-<search_files>
-<path>src</path>
-<regex>\.(tsx|jsx|vue)$|@Component|export.*component</regex>
-<file_pattern>*.tsx</file_pattern>
-</search_files>
-
-<!-- Find component usage -->
-<search_files>
-<path>src</path>
-<regex><Button|<Form|<Modal|<Dialog|<Input</regex>
-</search_files>
-          ]]></example>
-        </method>
-        
-        <method name="style_analysis">
-          <description>Analyze styling and visual elements</description>
-          <example><![CDATA[
-<!-- Find stylesheets -->
-<list_files>
-<path>src/styles</path>
-<recursive>true</recursive>
-</list_files>
+      <description>Find and analyze UI components and their interactions</description>
+      <heuristics>
+        <rule>Start from feature or route directories and enumerate components related to the requested topic.</rule>
+        <rule>Differentiate container vs presentational components; note composition patterns.</rule>
+        <rule>Trace inputs/outputs: props, state, context, events, and side effects.</rule>
+        <rule>Record conditional rendering that affects user-visible states.</rule>
+      </heuristics>
+      <evidence_to_collect>
+        <item>Primary components and responsibilities.</item>
+        <item>Props/state/context that change behavior.</item>
+        <item>High-level dependency/composition map.</item>
+      </evidence_to_collect>
+    </technique>
 
-<!-- Search for style definitions -->
-<search_files>
-<path>src</path>
-<regex>className=|style=|styled\.|makeStyles|@apply</regex>
-</search_files>
-          ]]></example>
-        </method>
-      </discovery_methods>
+    <technique name="style_analysis">
+      <description>Analyze styling and visual elements</description>
+      <heuristics>
+        <rule>Identify design tokens and utility classes used to drive layout and state.</rule>
+        <rule>Capture responsive behavior and breakpoint rules that materially change UX.</rule>
+        <rule>Document visual affordances tied to state (loading, error, disabled).</rule>
+      </heuristics>
+      <evidence_to_collect>
+        <item>Key classes/selectors influencing layout/state.</item>
+        <item>Responsive behavior summary and breakpoints.</item>
+      </evidence_to_collect>
     </technique>
 
     <technique name="user_flow_mapping">
-      <description>
-        Map user interactions and navigation flows
-      </description>
+      <description>Map user interactions and navigation flows</description>
       <analysis_areas>
         <area>Route definitions and navigation</area>
         <area>Form submissions and validations</area>
@@ -57,31 +42,20 @@
         <area>State changes and UI updates</area>
         <area>Loading and error states</area>
       </analysis_areas>
-      <search_patterns><![CDATA[
-<!-- Find route definitions -->
-<search_files>
-<path>src</path>
-<regex>Route.*path=|router\.push|navigate\(|Link.*to=</regex>
-</search_files>
-
-<!-- Find event handlers -->
-<search_files>
-<path>src</path>
-<regex>onClick=|onSubmit=|onChange=|handleClick|handleSubmit</regex>
-</search_files>
-
-<!-- Find form validations -->
-<search_files>
-<path>src</path>
-<regex>validate|validation|required|pattern=|minLength|maxLength</regex>
-</search_files>
-      ]]></search_patterns>
+      <heuristics>
+        <rule>Outline entry points and expected outcomes for each primary flow.</rule>
+        <rule>Summarize validation rules and failure states the user can encounter.</rule>
+        <rule>Record redirects and deep-link behavior relevant to the feature.</rule>
+      </heuristics>
+      <evidence_to_collect>
+        <item>Flow diagrams or bullet sequences for main tasks.</item>
+        <item>Validation conditions and error messages.</item>
+        <item>Navigation transitions and guards.</item>
+      </evidence_to_collect>
     </technique>
 
     <technique name="user_feedback_analysis">
-      <description>
-        Analyze how the system communicates with users
-      </description>
+      <description>Analyze how the system communicates with users</description>
       <elements_to_find>
         <element>Error messages and alerts</element>
         <element>Success notifications</element>
@@ -90,31 +64,19 @@
         <element>Confirmation dialogs</element>
         <element>Progress indicators</element>
       </elements_to_find>
-      <search_patterns><![CDATA[
-<!-- Find user messages -->
-<search_files>
-<path>src</path>
-<regex>toast|notification|alert|message|error.*message|success.*message</regex>
-</search_files>
-
-<!-- Find loading states -->
-<search_files>
-<path>src</path>
-<regex>loading|isLoading|pending|spinner|skeleton|placeholder</regex>
-</search_files>
-
-<!-- Find dialogs and modals -->
-<search_files>
-<path>src</path>
-<regex>modal|dialog|confirm|popup|overlay</regex>
-</search_files>
-      ]]></search_patterns>
+      <heuristics>
+        <rule>Map message triggers to the user actions that cause them.</rule>
+        <rule>Capture severity, persistence, and dismissal behavior.</rule>
+        <rule>Note localization or accessibility considerations in messages.</rule>
+      </heuristics>
+      <evidence_to_collect>
+        <item>Catalog of messages with purpose and conditions.</item>
+        <item>Loading/progress patterns and timeouts.</item>
+      </evidence_to_collect>
     </technique>
 
     <technique name="accessibility_analysis">
-      <description>
-        Check for accessibility features and compliance
-      </description>
+      <description>Check for accessibility features and compliance</description>
       <accessibility_checks>
         <check>ARIA labels and roles</check>
         <check>Keyboard navigation support</check>
@@ -122,25 +84,17 @@
         <check>Focus management</check>
         <check>Color contrast considerations</check>
       </accessibility_checks>
-      <search_patterns><![CDATA[
-<!-- Find accessibility attributes -->
-<search_files>
-<path>src</path>
-<regex>aria-|role=|tabIndex|alt=|title=|accessibilityLabel</regex>
-</search_files>
-
-<!-- Find focus management -->
-<search_files>
-<path>src</path>
-<regex>focus\(|blur\(|onFocus|onBlur|autoFocus|focusable</regex>
-</search_files>
-      ]]></search_patterns>
+      <heuristics>
+        <rule>Confirm interactive elements have clear focus and labels.</rule>
+        <rule>Describe keyboard-only navigation paths for core flows.</rule>
+      </heuristics>
+      <evidence_to_collect>
+        <item>Accessibility gaps affecting task completion.</item>
+      </evidence_to_collect>
     </technique>
 
     <technique name="responsive_design_analysis">
-      <description>
-        Analyze responsive design and mobile experience
-      </description>
+      <description>Analyze responsive design and mobile experience</description>
       <analysis_points>
         <point>Breakpoint definitions</point>
         <point>Mobile-specific components</point>
@@ -148,230 +102,88 @@
         <point>Viewport configurations</point>
         <point>Media queries</point>
       </analysis_points>
-      <search_patterns><![CDATA[
-<!-- Find responsive utilities -->
-<search_files>
-<path>src</path>
-<regex>@media|breakpoint|mobile|tablet|desktop|responsive</regex>
-</search_files>
-
-<!-- Find touch events -->
-<search_files>
-<path>src</path>
-<regex>onTouch|swipe|gesture|tap|press</regex>
-</search_files>
-      ]]></search_patterns>
+      <heuristics>
+        <rule>Summarize layout changes across breakpoints that alter workflow.</rule>
+        <rule>Note touch targets and gestures required on mobile.</rule>
+      </heuristics>
+      <evidence_to_collect>
+        <item>Table of key differences per breakpoint.</item>
+      </evidence_to_collect>
     </technique>
   </ui_ux_analysis_techniques>
 
   <code_analysis_techniques>
-    <technique name="semantic_search_analysis">
-      <description>
-        Use semantic search to find conceptually related code when available.
-      </description>
-      <when_to_use>
-        <scenario>Finding code by concept rather than keywords</scenario>
-        <scenario>Discovering implementations across different naming conventions</scenario>
-        <scenario>When pattern-based search isn't finding expected results</scenario>
-      </when_to_use>
-      <example><![CDATA[
-<!-- Optional: Find authentication-related code semantically -->
-<codebase_search>
-<query>user authentication login security JWT token validation</query>
-</codebase_search>
-
-<!-- Optional: Find payment processing logic -->
-<codebase_search>
-<query>payment processing transaction billing invoice checkout</query>
-</codebase_search>
-      ]]></example>
-      <note>This is an optional tool - use when semantic understanding would help find related code that keyword search might miss</note>
-    </technique>
-
     <technique name="entry_point_analysis">
-      <description>
-        Analyze entry points to understand feature flow.
-      </description>
+      <description>Understand feature entry points and control flow</description>
       <steps>
-        <step>Find main functions, controllers, or route handlers.</step>
-        <step>Trace execution flow.</step>
-        <step>Map decision branches.</step>
-        <step>Document input validation.</step>
+        <step>Identify main functions, controllers, or route handlers.</step>
+        <step>Trace execution and decision branches.</step>
+        <step>Document input validation and preconditions.</step>
       </steps>
-      <discovery_methods>
-        <method name="directory_based">
-          <description>Start by exploring directory structure</description>
-          <example><![CDATA[
-<!-- List main directories -->
-<list_files>
-<path>src</path>
-<recursive>false</recursive>
-</list_files>
-
-<!-- Explore feature directory -->
-<list_files>
-<path>src/controllers</path>
-<recursive>true</recursive>
-</list_files>
-          ]]></example>
-        </method>
-        
-        <method name="pattern_based">
-          <description>Search for specific patterns</description>
-          <example><![CDATA[
-<!-- Find all routes -->
-<search_files>
-<path>src</path>
-<regex>(app\.(get|post|put|delete)|@(Get|Post|Put|Delete)|router\.(get|post|put|delete))</regex>
-</search_files>
-          ]]></example>
-        </method>
-        
-        <method name="file_based">
-          <description>Read known entry points directly</description>
-          <example><![CDATA[
-<!-- Read main application file -->
-<read_file>
-<path>src/app.ts</path>
-</read_file>
-
-<!-- Read specific controller -->
-<read_file>
-<path>src/controllers/feature.controller.ts</path>
-</read_file>
-          ]]></example>
-        </method>
-        
-        <method name="semantic_based">
-          <description>Use semantic search as an alternative discovery method</description>
-          <example><![CDATA[
-<!-- Optional: Find entry points semantically -->
-<codebase_search>
-<query>main entry point application startup initialization bootstrap</query>
-</codebase_search>
-          ]]></example>
-        </method>
-      </discovery_methods>
+      <evidence_to_collect>
+        <item>Entry points list and short purpose statements.</item>
+        <item>Decision matrix or flow sketch.</item>
+      </evidence_to_collect>
     </technique>
 
     <technique name="api_extraction">
-      <description>
-        Extract API specifications from code.
-      </description>
+      <description>Extract API specifications from code</description>
       <patterns>
         <pattern type="rest">
-          <search_regex><![CDATA[
-(app|router)\.(get|post|put|patch|delete)\s*\(\s*['"`]([^'"`]+)['"`]
-          ]]></search_regex>
           <extraction>
-            - HTTP method
-            - Route path
-            - Path/query parameters
-            - Request/response schemas
-            - Status codes
+            <item>HTTP method and route path</item>
+            <item>Path/query parameters</item>
+            <item>Request/response schemas</item>
+            <item>Status codes and error bodies</item>
           </extraction>
         </pattern>
         <pattern type="graphql">
-          <search_regex><![CDATA[
-type\s+(Query|Mutation|Subscription)\s*{[^}]+}|@(Query|Mutation|Resolver)
-          ]]></search_regex>
           <extraction>
-            - Schema and input types
-            - Resolvers
-            - Return types
-            - Field arguments
+            <item>Schema and input types</item>
+            <item>Resolvers and return types</item>
+            <item>Field arguments and constraints</item>
           </extraction>
         </pattern>
       </patterns>
     </technique>
 
     <technique name="dependency_mapping">
-      <description>
-        Map dependencies and integration points.
-      </description>
+      <description>Map dependencies and integration points</description>
       <analysis_points>
-        <point>Import/require statements</point>
-        <point>package.json dependencies</point>
-        <point>External API calls</point>
-        <point>DB connections</point>
-        <point>Message queue integrations</point>
-        <point>Filesystem operations</point>
+        <point>Imports and module boundaries</point>
+        <point>Package and runtime dependencies</point>
+        <point>External API/SDK usage</point>
+        <point>DB connections and migrations</point>
+        <point>Messaging/queue/event streams</point>
+        <point>Filesystem or network side effects</point>
       </analysis_points>
-      <analysis_approaches>
-        <approach name="package_analysis">
-          <description>Start with package.json to understand dependencies</description>
-          <example><![CDATA[
-<!-- Analyze package dependencies -->
-<read_file>
-<path>package.json</path>
-</read_file>
-          ]]></example>
-        </approach>
-        
-        <approach name="import_tracking">
-          <description>Follow import chains to map dependencies</description>
-          <example><![CDATA[
-<!-- Find all imports -->
-<search_files>
-<path>src</path>
-<regex>^import\s+.*from\s+['"]([^'"]+)['"]|require\s*\(\s*['"]([^'"]+)['"]\s*\)</regex>
-</search_files>
-          ]]></example>
-        </approach>
-        
-        <approach name="api_discovery">
-          <description>Find external API integrations</description>
-          <example><![CDATA[
-<!-- Find external API calls -->
-<search_files>
-<path>src</path>
-<regex>(fetch|axios|http\.request|request\(|\.get\(|\.post\()</regex>
-</search_files>
-          ]]></example>
-        </approach>
-      </analysis_approaches>
+      <evidence_to_collect>
+        <item>Dependency graph summary and hot spots.</item>
+        <item>List of external integrations and auth methods.</item>
+      </evidence_to_collect>
     </technique>
 
     <technique name="data_model_extraction">
-      <description>
-        Extract data models, schemas, and type definitions.
-      </description>
+      <description>Extract data models, schemas, and type definitions</description>
       <sources>
         <source type="typescript">
-          <patterns>
-            - interfaces, types, classes, enums
-          </patterns>
+          <patterns>- interfaces, types, classes, enums</patterns>
         </source>
         <source type="database">
-          <patterns>
-            - Schema definitions, migration files, ORM models
-          </patterns>
+          <patterns>- Schema definitions, migration files, ORM models</patterns>
         </source>
         <source type="validation">
-          <patterns>
-            - JSON Schema, Joi/Yup/Zod schemas, validation decorators
-          </patterns>
+          <patterns>- JSON Schema, Joi/Yup/Zod schemas, validation decorators</patterns>
         </source>
       </sources>
-      <extraction_example><![CDATA[
-<!-- Find TypeScript interfaces -->
-<search_files>
-<path>src</path>
-<regex>^export\s+(interface|type|class|enum)\s+(\w+)</regex>
-</search_files>
-
-<!-- Find database models -->
-<search_files>
-<path>src/models</path>
-<regex>@(Entity|Table|Model)|class\s+\w+\s+extends\s+(Model|BaseEntity)</regex>
-</search_files>
-      ]]></extraction_example>
+      <evidence_to_collect>
+        <item>Canonical definitions and field constraints.</item>
+        <item>Entity relationships and ownership.</item>
+      </evidence_to_collect>
     </technique>
 
     <technique name="business_logic_extraction">
-      <description>
-        Identify and document business rules.
-      </description>
+      <description>Identify and document business rules</description>
       <indicators>
         <indicator>Complex conditionals</indicator>
         <indicator>Calculation functions</indicator>
@@ -380,79 +192,49 @@ type\s+(Query|Mutation|Subscription)\s*{[^}]+}|@(Query|Mutation|Resolver)
         <indicator>Domain-specific constants and algorithms</indicator>
       </indicators>
       <documentation_focus>
-        <focus>Why logic exists (business need)</focus>
-        <focus>When logic applies (conditions)</focus>
-        <focus>What logic does (transformation)</focus>
-        <focus>Edge cases</focus>
+        <focus>Why the logic exists (business need)</focus>
+        <focus>When the logic applies (conditions)</focus>
+        <focus>What the logic does (transformation)</focus>
+        <focus>Edge cases and invariants</focus>
         <focus>Impact of changes</focus>
       </documentation_focus>
     </technique>
 
     <technique name="error_handling_analysis">
-      <description>
-        Document error handling and recovery.
-      </description>
+      <description>Document error handling and recovery</description>
       <analysis_areas>
-        <area>try/catch blocks, error boundaries</area>
-        <area>Custom error classes</area>
-        <area>Error codes and messages</area>
+        <area>try/catch blocks and error boundaries</area>
+        <area>Custom error classes and codes</area>
         <area>Logging, fallbacks, retries, circuit breakers</area>
       </analysis_areas>
-      <search_patterns><![CDATA[
-<!-- Find error handling -->
-<search_files>
-<path>src</path>
-<regex>try\s*{|catch\s*\(|throw\s+new|class\s+\w*Error\s+extends</regex>
-</search_files>
-
-<!-- Find error constants -->
-<search_files>
-<path>src</path>
-<regex>ERROR_|_ERROR|ErrorCode|errorCode</regex>
-</search_files>
-      ]]></search_patterns>
+      <evidence_to_collect>
+        <item>Error taxonomy and user-facing messages.</item>
+        <item>Recovery/rollback strategies and timeouts.</item>
+      </evidence_to_collect>
     </technique>
 
     <technique name="security_analysis">
-      <description>
-        Identify security measures and vulnerabilities.
-      </description>
+      <description>Identify security measures and vulnerabilities</description>
       <security_checks>
-        <check category="authentication">
-          <patterns>
-            - JWT, sessions, OAuth, API keys
-          </patterns>
-        </check>
-        <check category="authorization">
-          <patterns>
-            - RBAC, permission checks, ownership validation
-          </patterns>
-        </check>
-        <check category="data_protection">
-          <patterns>
-            - Encryption, hashing, sensitive data handling
-          </patterns>
-        </check>
-        <check category="input_validation">
-          <patterns>
-            - Sanitization, SQLi/XSS/CSRF prevention
-          </parents>
-        </check>
+        <check category="authentication">JWT, sessions, OAuth, API keys</check>
+        <check category="authorization">RBAC, permission checks, ownership validation</check>
+        <check category="data_protection">Encryption, hashing, sensitive data handling</check>
+        <check category="input_validation">Sanitization and injection prevention</check>
       </security_checks>
+      <evidence_to_collect>
+        <item>Threat surfaces and mitigations relevant to the feature.</item>
+      </evidence_to_collect>
     </technique>
 
     <technique name="performance_analysis">
-      <description>
-        Identify performance factors and optimization opportunities.
-      </description>
+      <description>Identify performance factors and optimization opportunities</description>
       <analysis_points>
-        <point>DB query patterns (N+1)</point>
+        <point>Expensive loops/algorithms</point>
+        <point>DB query patterns (e.g., N+1)</point>
         <point>Caching strategies</point>
-        <point>Async usage</point>
-        <point>Batch processing</point>
-        <point>Resource pooling</point>
-        <point>Memory management</point>
-        <point>Algorithm complexity</point>
+        <point>Concurrency and async usage</point>
+        <point>Batching and resource pooling</point>
+        <point>Memory management and object lifetimes</point>
       </analysis_points>
       <metrics_to_document>
         <metric>Time/space complexity</metric>
@@ -464,51 +246,32 @@ type\s+(Query|Mutation|Subscription)\s*{[^}]+}|@(Query|Mutation|Resolver)
     </technique>
 
     <technique name="test_coverage_analysis">
-      <description>
-        Analyze test coverage.
-      </description>
+      <description>Assess test coverage at a useful granularity</description>
       <test_types>
         <type name="unit">
-          <location>__tests__, *.test.ts, *.spec.ts</location>
-          <analysis>Function coverage</analysis>
+          <analysis>Function-level coverage and edge cases</analysis>
         </type>
         <type name="integration">
-          <location>integration/, e2e/</location>
-          <analysis>Workflow coverage</analysis>
+          <analysis>Workflow coverage and contract boundaries</analysis>
         </type>
         <type name="api">
-          <location>api-tests/, *.api.test.ts</location>
-          <analysis>Endpoint coverage</analysis>
+          <analysis>Endpoint success/failure paths and schemas</analysis>
         </type>
       </test_types>
-      <coverage_analysis><![CDATA[
-<!-- Find test files -->
-<search_files>
-<path>src</path>
-<regex>\.(test|spec)\.(ts|js|tsx|jsx)$</regex>
-<file_pattern>*.test.ts</file_pattern>
-</search_files>
-
-<!-- Analyze test descriptions -->
-<search_files>
-<path>src</path>
-<regex>(describe|it|test)\s*\(\s*['"`]([^'"`]+)['"`]</regex>
-</search_files>
-      ]]></coverage_analysis>
+      <evidence_to_collect>
+        <item>List of critical behaviors missing tests.</item>
+      </evidence_to_collect>
     </technique>
 
     <technique name="configuration_extraction">
-      <description>
-        Extract configuration options and their impacts.
-      </description>
+      <description>Extract configuration options and their impacts</description>
       <configuration_sources>
         <source>.env files, config files, CLI args, feature flags</source>
       </configuration_sources>
       <documentation_requirements>
-        <requirement>Default values</requirement>
-        <requirement>Valid values</requirement>
-        <requirement>Behavior impact</requirement>
-        <requirement>Config dependencies</requirement>
+        <requirement>Default values and valid ranges</requirement>
+        <requirement>Behavioral impact of each option</requirement>
+        <requirement>Dependencies between options</requirement>
         <requirement>Security implications</requirement>
       </documentation_requirements>
     </technique>
@@ -516,54 +279,49 @@ type\s+(Query|Mutation|Subscription)\s*{[^}]+}|@(Query|Mutation|Resolver)
 
   <workflow_analysis>
     <technique name="user_journey_mapping">
-      <description>
-        Map user workflows through the feature.
-      </description>
+      <description>Map user workflows through the feature</description>
       <steps>
-        <step>Identify entry points (UI, API, CLI).</step>
-        <step>Trace user actions.</step>
-        <step>Document decision points.</step>
-        <step>Map data transformations.</step>
-        <step>Identify outcomes.</step>
+        <step>Identify entry points (UI, API, CLI)</step>
+        <step>Trace user actions and decision points</step>
+        <step>Map data transformations</step>
+        <step>Identify outcomes and completion criteria</step>
       </steps>
       <deliverables>
-        <deliverable>Flow diagrams, procedures, decision trees, state diagrams.</deliverable>
+        <deliverable>Flow diagrams, procedures, decision trees, state diagrams</deliverable>
       </deliverables>
     </technique>
 
     <technique name="integration_flow_analysis">
-      <description>
-        Document integration with other systems.
-      </description>
+      <description>Document integration with other systems</description>
       <integration_types>
-        <type>Sync API calls, async messaging, events, batch processing, streaming.</type>
+        <type>Sync API calls, async messaging, events, batch processing, streaming</type>
       </integration_types>
       <documentation_focus>
-        <focus>Protocols, auth, error handling, data transforms, SLAs.</focus>
+        <focus>Protocols, auth, error handling, data transforms, SLAs</focus>
       </documentation_focus>
     </technique>
   </workflow_analysis>
 
   <metadata_extraction>
     <technique name="version_compatibility">
+      <description>Summarize version constraints and compatibility</description>
       <sources>
-        <source>package.json, READMEs, migration guides, breaking changes docs.</source>
+        <source>package manifests, READMEs, migration guides, breaking changes docs</source>
       </sources>
-      <extraction_pattern><![CDATA[
-<!-- Find version requirements -->
-<search_files>
-<path>.</path>
-<regex>"engines":|"peerDependencies":|requires?\s+\w+\s+version|compatible\s+with</regex>
-</search_files>
-      ]]></extraction_pattern>
+      <evidence_to_collect>
+        <item>Minimum/recommended versions and notable constraints.</item>
+      </evidence_to_collect>
     </technique>
 
     <technique name="deprecation_tracking">
+      <description>Track deprecations and migrations</description>
       <indicators>
-        <indicator>@deprecated, TODO comments, legacy code markers.</indicator>
+        <indicator>Explicit deprecation notices and TODO markers</indicator>
+        <indicator>Legacy code paths and adapters</indicator>
       </indicators>
       <documentation_requirements>
-        <requirement>Deprecation date, removal timeline, migration path, alternatives.</requirement>
+        <requirement>Deprecation date and removal timeline</requirement>
+        <requirement>Migration path and alternatives</requirement>
       </documentation_requirements>
     </technique>
   </metadata_extraction>
@@ -571,17 +329,20 @@ type\s+(Query|Mutation|Subscription)\s*{[^}]+}|@(Query|Mutation|Resolver)
   <quality_indicators>
     <indicator name="documentation_completeness">
       <checks>
-        <check>Public APIs documented.</check>
-        <check>Examples for complex features.</check>
-        <check>Error scenarios covered.</check>
-        <check>Config options explained.</check>
-        <check>Security addressed.</check>
+        <check>Public APIs documented with inputs/outputs and errors</check>
+        <check>Examples for complex features</check>
+        <check>Error scenarios covered with recovery guidance</check>
+        <check>Config options explained with defaults and impacts</check>
+        <check>Security considerations addressed</check>
       </checks>
     </indicator>
-
     <indicator name="code_quality_metrics">
       <metrics>
-        <metric>Cyclomatic complexity, code duplication, test coverage, doc coverage, tech debt.</metric>
+        <metric>Cyclomatic complexity</metric>
+        <metric>Code duplication</metric>
+        <metric>Test coverage and gaps</metric>
+        <metric>Documentation coverage for user-visible behaviors</metric>
+        <metric>Known technical debt affecting UX</metric>
       </metrics>
     </indicator>
   </quality_indicators>

.roo/rules-docs-extractor/6_communication_guidelines.xml → .roo/rules-docs-extractor/4_communication_guidelines.xml

@@ -16,17 +16,6 @@
         <scenario>The user explicitly asks for options.</scenario>
       </when_to_ask>
       
-      <question_example><![CDATA[
-<ask_followup_question>
-<question>Found multiple auth systems. Which to document?</question>
-<follow_up>
-<suggest>JWT-based system (src/auth/jwt/*)</suggest>
-<suggest>OAuth2 integration (src/auth/oauth/*)</suggest>
-<suggest>Basic auth middleware (src/middleware/basic-auth.ts)</suggest>
-<suggest>All of them</suggest>
-</follow_up>
-</ask_followup_question>
-      ]]></question_example>
     </clarification>
 
     <progress_updates>
@@ -62,7 +51,7 @@
         </discovery>
       </important_findings>
       <extraction_findings>
-        <template><![CDATA[
+        <template>
 Feature extraction complete for [feature name].
 
 **Extraction Report**: `EXTRACTION-[feature].md`
@@ -79,10 +68,10 @@ Feature extraction complete for [feature name].
 - [Edge cases that should be documented]
 
 The extraction report provides comprehensive details for your documentation team.
-        ]]></template>
+        </template>
       </extraction_findings>
       <verification_findings>
-        <template><![CDATA[
+        <template>
 Documentation verification complete.
 
 **Verification Report**: `VERIFICATION-[feature].md`
@@ -101,7 +90,7 @@ Documentation verification complete.
 3. [Key missing information]
 
 See the full verification report for detailed corrections and suggestions.
-        ]]></template>
+        </template>
       </verification_findings>
     </findings_communication>
   </user_interaction>
@@ -116,7 +105,7 @@ See the full verification report for detailed corrections and suggestions.
       <code_blocks>
         <rule>Always specify language for syntax highlighting (e.g., typescript, json, bash).</rule>
         <rule>Include file paths as comments where relevant.</rule>
-        <example><![CDATA[
+        <example>
 ```typescript
 // src/auth/auth.service.ts
 export class AuthService {
@@ -125,19 +114,19 @@ export class AuthService {
   }
 }
 ```
-        ]]></example>
+        </example>
       </code_blocks>
 
       <tables>
         <rule>Use tables for structured data like configs.</rule>
         <rule>Include headers and align columns.</rule>
         <rule>Keep cell content brief.</rule>
-        <example><![CDATA[
+        <example>
 | Variable | Type | Default | Description |
 |----------|------|---------|-------------|
 | `JWT_SECRET` | string | - | Secret key for JWT signing |
 | `JWT_EXPIRATION` | string | '15m' | Token expiration time |
-        ]]></example>
+        </example>
       </tables>
 
       <lists>
@@ -180,14 +169,14 @@ export class AuthService {
       </alerts>
 
       <metadata_blocks>
-        <version_info><![CDATA[
+        <version_info>
 ---
 Feature: Authentication System
 Version: 2.1.0
 Last Updated: 2024-01-15
 Status: Stable
 ---
-        ]]></version_info>
+        </version_info>
       </metadata_blocks>
     </special_sections>
   </output_formatting>
@@ -208,16 +197,11 @@ Status: Stable
         <vocabulary>Standard programming terms.</vocabulary>
         <examples>Code snippets, implementation details.</examples>
       </audience>
-      <audience type="end_user">
+      <audience type="user">
         <tone>Instructional, step-by-step.</tone>
         <vocabulary>Simple language, no jargon.</vocabulary>
         <examples>Screenshots, real-world scenarios.</examples>
       </audience>
-      <audience type="administrator">
-        <tone>Operational focus.</tone>
-        <vocabulary>IT/DevOps terms.</vocabulary>
-        <examples>CLI examples, configs.</examples>
-      </audience>
     </audience_tone>
   </documentation_tone>
 
@@ -229,7 +213,7 @@ Status: Stable
       <element>Recommended next steps.</element>
     </structure>
 
-    <extraction_example><![CDATA[
+    <extraction_example>
 Feature extraction complete for the authentication system.
 
 **Extraction Report**: `EXTRACTION-authentication-system.md`
@@ -252,9 +236,9 @@ Feature extraction complete for the authentication system.
 - Error messages need user-friendly translations
 
 The extraction report contains all details needed for comprehensive documentation.
-    ]]></extraction_example>
+    </extraction_example>
 
-    <verification_example><![CDATA[
+    <verification_example>
 Documentation verification complete for the authentication system.
 
 **Verification Report**: `VERIFICATION-authentication-system.md`
@@ -271,7 +255,7 @@ Documentation verification complete for the authentication system.
 **Clarity Improvements**: 3 suggestions
 
 Please review the verification report for specific corrections needed.
-    ]]></verification_example>
+    </verification_example>
   </completion_message>
 
   <error_handling>

.roo/rules-docs-extractor/4_tool_usage_guide.xml

@@ -1,397 +0,0 @@
-<tool_usage_guide>
-  <overview>
-    Guidance on using tools for documentation extraction.
-  </overview>
-
-  <discovery_approaches>
-    <approach name="flexible_discovery">
-      <description>Use the most appropriate tools for the situation</description>
-      <principles>
-        <principle>Start with what you know - file names, directory structure, or keywords</principle>
-        <principle>Use multiple discovery methods to build understanding</principle>
-        <principle>Adapt your approach based on the codebase structure</principle>
-      </principles>
-    </approach>
-
-    <common_tools>
-      <tool name="list_files">
-        <purpose>Explore directory structure and find relevant files</purpose>
-        <when_to_use>
-          - Starting exploration of a feature area
-          - Understanding project organization
-          - Finding configuration or test files
-        </when_to_use>
-      </tool>
-
-      <tool name="read_file">
-        <purpose>Examine specific files in detail</purpose>
-        <when_to_use>
-          - Analyzing implementation details
-          - Understanding configuration
-          - Reading documentation or comments
-        </when_to_use>
-        <tip>Read multiple related files together for better context</tip>
-      </tool>
-
-      <tool name="search_files">
-        <purpose>Find specific patterns or text</purpose>
-        <when_to_use>
-          - Locating API endpoints
-          - Finding configuration usage
-          - Tracking down error handling
-          - Discovering cross-references
-        </when_to_use>
-      </tool>
-
-      <tool name="list_code_definition_names">
-        <purpose>Get overview of code structure</purpose>
-        <when_to_use>
-          - Understanding module organization
-          - Identifying main components
-          - Finding test coverage
-        </when_to_use>
-      </tool>
-
-      <tool name="codebase_search">
-        <purpose>Semantic search when available</purpose>
-        <when_to_use>
-          - Finding conceptually related code
-          - Discovering implementations by functionality
-          - When keyword search isn't sufficient
-        </when_to_use>
-        <note>Optional - use when semantic understanding is needed</note>
-      </tool>
-    </common_tools>
-
-    <discovery_patterns>
-      <pattern name="top_down">
-        <description>Start from high-level structure and drill down</description>
-        <steps>
-          <step>List files in feature directory</step>
-          <step>Identify main entry points</step>
-          <step>Follow imports and dependencies</step>
-          <step>Examine implementation details</step>
-        </steps>
-      </pattern>
-
-      <pattern name="test_driven">
-        <description>Use tests to understand expected behavior</description>
-        <steps>
-          <step>Find test files for the feature</step>
-          <step>Read test descriptions and scenarios</step>
-          <step>Trace back to implementation</step>
-          <step>Verify behavior matches tests</step>
-        </steps>
-      </pattern>
-
-      <pattern name="configuration_first">
-        <description>Start with configuration to understand setup</description>
-        <steps>
-          <step>Find configuration files</step>
-          <step>Identify feature flags and settings</step>
-          <step>Trace usage in code</step>
-          <step>Document impacts of each setting</step>
-        </steps>
-      </pattern>
-
-      <pattern name="api_focused">
-        <description>Map external interfaces first</description>
-        <steps>
-          <step>Search for route definitions</step>
-          <step>Find API controllers or handlers</step>
-          <step>Trace to business logic</step>
-          <step>Document request/response flow</step>
-        </steps>
-      </pattern>
-    </discovery_patterns>
-  </discovery_approaches>
-
-  <documentation_generation_tools>
-    <tool name="write_to_file">
-      <purpose>Create extraction or verification report files.</purpose>
-      <note>Generates reports for documentation teams, not final documentation.</note>
-      <file_naming>
-        - For extraction: EXTRACTION-[feature-name].md
-        - For verification: VERIFICATION-[feature-name].md
-      </file_naming>
-      <best_practices>
-        <practice>Use descriptive feature name in filename.</practice>
-        <practice>Include table of contents.</practice>
-        <practice>Use consistent Markdown formatting.</practice>
-        <practice>Include syntax-highlighted code examples.</practice>
-      </best_practices>
-      <example><![CDATA[
-<write_to_file>
-<path>EXTRACTION-authentication-system.md</path>
-<content>
-# Authentication System Documentation
-
-## Table of Contents
-1. [Overview](#overview)
-2. [Architecture](#architecture)
-...
-
-## Overview
-The authentication system provides secure user authentication using JWT tokens...
-</content>
-<line_count>...</line_count>
-</write_to_file>
-      ]]></example>
-    </tool>
-    
-    <tool name="ask_followup_question">
-      <purpose>Clarify ambiguous requirements.</purpose>
-      <when_to_use>
-        <scenario>Multiple features have similar names.</scenario>
-        <scenario>Documentation depth is unclear.</scenario>
-        <scenario>Audience priorities are undefined.</scenario>
-      </when_to_use>
-      <examples>
-        <example><![CDATA[
-<ask_followup_question>
-<question>Which authentication aspects should be the focus?</question>
-<follow_up>
-<suggest>The complete flow (JWT, sessions, OAuth).</suggest>
-<suggest>Only JWT implementation and validation.</suggest>
-<suggest>Only OAuth2 integration.</suggest>
-<suggest>Password reset and recovery workflows.</suggest>
-</follow_up>
-</ask_followup_question>
-        ]]></example>
-        <example><![CDATA[
-<ask_followup_question>
-<question>What level of technical detail is needed?</question>
-<follow_up>
-<suggest>High-level overview for all audiences.</suggest>
-<suggest>Detailed developer implementation.</suggest>
-<suggest>API reference with code examples.</suggest>
-<suggest>Full coverage for all audiences.</suggest>
-</follow_up>
-</ask_followup_question>
-        ]]></example>
-      </examples>
-    </tool>
-  </documentation_generation_tools>
-
-  <analysis_strategies>
-    <strategy name="file_discovery">
-      <description>
-        Find all files related to a feature using various methods.
-      </description>
-      <methods>
-        <method name="directory_exploration">
-          <description>Start by exploring likely directories</description>
-          <tool_use><![CDATA[
-<list_files>
-<path>src</path>
-<recursive>false</recursive>
-</list_files>
-
-<!-- Then drill into feature directory -->
-<list_files>
-<path>src/features/[feature-name]</path>
-<recursive>true</recursive>
-</list_files>
-          ]]></tool_use>
-        </method>
-
-        <method name="pattern_search">
-          <description>Search for feature-related patterns</description>
-          <tool_use><![CDATA[
-<!-- Find files with feature name -->
-<search_files>
-<path>src</path>
-<regex>feature-name|FeatureName</regex>
-</search_files>
-
-<!-- Find related tests -->
-<search_files>
-<path>src</path>
-<regex>describe\(['"].*Feature.*['"]|test\(['"].*feature.*['"]</regex>
-<file_pattern>*.test.ts</file_pattern>
-</search_files>
-          ]]></tool_use>
-        </method>
-
-        <method name="configuration_discovery">
-          <description>Find configuration files</description>
-          <tool_use><![CDATA[
-<!-- Look for config files -->
-<list_files>
-<path>config</path>
-<recursive>true</recursive>
-</list_files>
-
-<!-- Search for feature config -->
-<search_files>
-<path>.</path>
-<regex>feature.*config|settings.*feature</regex>
-<file_pattern>*.json</file_pattern>
-</search_files>
-          ]]></tool_use>
-        </method>
-
-        <method name="semantic_search_optional">
-          <description>Use semantic search if available and helpful</description>
-          <tool_use><![CDATA[
-<!-- Optional: Use when concept-based search is needed -->
-<codebase_search>
-<query>feature implementation main logic</query>
-</codebase_search>
-          ]]></tool_use>
-          <note>This is optional - use when other methods aren't sufficient</note>
-        </method>
-      </methods>
-    </strategy>
-
-    <strategy name="dependency_chain_analysis">
-      <description>
-        Follow import chains to map dependencies.
-      </description>
-      <process>
-        <step>Read main file.</step>
-        <step>Extract all imports.</step>
-        <step>Read each imported file.</step>
-        <step>Recursively analyze imports.</step>
-        <step>Build dependency graph.</step>
-      </process>
-      <import_patterns><![CDATA[
-<!-- TypeScript/JavaScript imports -->
-<search_files>
-<path>src/feature</path>
-<regex>import\s+(?:{[^}]+}|\*\s+as\s+\w+|\w+)\s+from\s+['"]([^'"]+)['"]</regex>
-</search_files>
-
-<!-- CommonJS requires -->
-<search_files>
-<path>src/feature</path>
-<regex>require\(['"]([^'"]+)['"]\)</regex>
-</search_files>
-      ]]></import_patterns>
-    </strategy>
-
-    <strategy name="api_documentation_extraction">
-      <description>
-        Extract API documentation from code.
-      </description>
-      <extraction_points>
-        <point>Route definitions, request/response schemas, auth requirements, rate limiting, error responses.</point>
-      </extraction_points>
-      <tools_sequence>
-        <sequence>
-          <step>Find route files.</step>
-          <step>Extract route definitions.</step>
-          <step>Find controllers.</step>
-          <step>Analyze request validation.</step>
-          <step>Document response formats.</step>
-        </sequence>
-      </tools_sequence>
-    </strategy>
-
-    <strategy name="test_driven_documentation">
-      <description>
-        Use tests to document expected behavior.
-      </description>
-      <benefits>
-        <benefit>Tests provide usage examples.</benefit>
-        <benefit>Test descriptions explain functionality.</benefit>
-        <benefit>Tests cover edge cases.</benefit>
-        <benefit>Tests document expected outputs.</benefit>
-      </benefits>
-      <extraction_approach><![CDATA[
-<!-- Find test descriptions -->
-<search_files>
-<path>__tests__</path>
-<regex>(describe|it|test)\(['"]([^'"]+)['"]</regex>
-</search_files>
-
-<!-- Extract test scenarios -->
-<read_file>
-<path>__tests__/feature.test.ts</path>
-</read_file>
-      ]]></extraction_approach>
-    </strategy>
-  </analysis_strategies>
-
-  <common_patterns>
-    <pattern name="configuration_documentation">
-      <search_locations>
-        <location>.env.example</location>
-        <location>config/*.json</location>
-        <location>src/config/*</location>
-        <location>README.md (configuration section)</location>
-      </search_locations>
-      <extraction_regex><![CDATA[
-# Environment variables
-process\.env\.(\w+)
-
-# Config object access
-config\.(\w+)\.(\w+)
-
-# Default values
-\w+\s*=\s*process\.env\.\w+\s*\|\|\s*['"]([^'"]+)['"]
-      ]]></extraction_regex>
-    </pattern>
-
-    <pattern name="error_documentation">
-      <error_patterns>
-        <pattern>Custom error classes</pattern>
-        <pattern>Error code constants</pattern>
-        <pattern>Error message templates</pattern>
-        <pattern>HTTP status codes</pattern>
-      </error_patterns>
-      <search_approach><![CDATA[
-<search_files>
-<path>src</path>
-<regex>class\s+\w*Error\s+extends|new Error\(|throw new|ERROR_CODE|HTTP_STATUS</regex>
-</search_files>
-      ]]></search_approach>
-    </pattern>
-
-    <pattern name="security_documentation">
-      <security_aspects>
-        <aspect>Authentication methods</aspect>
-        <aspect>Authorization rules</aspect>
-        <aspect>Data encryption</aspect>
-        <aspect>Input validation</aspect>
-        <aspect>Rate limiting</aspect>
-      </security_aspects>
-      <indicators><![CDATA[
-<search_files>
-<path>src</path>
-<regex>@Authorized|requireAuth|checkPermission|encrypt|decrypt|sanitize|validate|rateLimit</regex>
-</search_files>
-      ]]></indicators>
-    </pattern>
-  </common_patterns>
-
-  <output_optimization>
-    <guideline name="structure">
-      <description>Organize output for navigation.</description>
-      <structure>
-        - Clear hierarchy, consistent headings, ToC with links, cross-references.
-      </structure>
-    </guideline>
-
-    <guideline name="code_examples">
-      <description>Include relevant code examples.</description>
-      <best_practices>
-        - Use syntax highlighting, show request/response, include error cases.
-      </best_practices>
-    </guideline>
-
-    <guideline name="visuals">
-      <description>Suggest diagrams where helpful.</description>
-      <diagram_types>
-        - Architecture, sequence, data flow, state machine diagrams.
-      </diagram_types>
-    </guideline>
-
-    <guideline name="metadata">
-      <description>Include important metadata.</description>
-      <required_metadata>
-        - Version compatibility, last updated, status, performance, security.
-      </required_metadata>
-    </guideline>
-  </output_optimization>
-</tool_usage_guide>

.roo/rules-docs-extractor/5_complete_extraction_examples.xml

@@ -1,881 +0,0 @@
-<complete_extraction_examples>
-  <overview>
-    Examples of both documentation extraction and verification workflows demonstrating flexible discovery methods and comprehensive UI/UX analysis.
-  </overview>
-
-  <example name="authentication_system_extraction">
-    <scenario>
-      Extract comprehensive documentation for a JWT-based authentication system, including technical implementation, UI/UX elements, and user workflows.
-    </scenario>
-
-    <workflow>
-      <step number="1">
-        <description>Initialize and discover feature using flexible methods</description>
-        <tool_use><![CDATA[
-<!-- Method 1: Directory exploration -->
-<list_files>
-<path>src</path>
-<recursive>false</recursive>
-</list_files>
-        ]]></tool_use>
-        <analysis>Look for auth-related directories like auth/, authentication/, or security/</analysis>
-        <tool_use><![CDATA[
-<list_files>
-<path>src/auth</path>
-<recursive>true</recursive>
-</list_files>
-        ]]></tool_use>
-        <expected_findings>
-          - Auth controllers, services, middleware, models, and routes
-          - Login components and forms
-          - Session management UI
-        </expected_findings>
-      </step>
-
-      <step number="2">
-        <description>Analyze code structure and architecture</description>
-        <tool_use><![CDATA[
-<list_code_definition_names>
-<path>src/auth</path>
-</list_code_definition_names>
-        ]]></tool_use>
-        <analysis>
-          - Identify main classes/functions
-          - Map authentication flow
-          - Find token generation/validation logic
-          - Locate UI components
-        </analysis>
-      </step>
-
-      <step number="3">
-        <description>Read core implementation files</description>
-        <tool_use><![CDATA[
-<read_file>
-<args>
-  <file>
-    <path>src/auth/auth.controller.ts</path>
-  </file>
-  <file>
-    <path>src/auth/auth.service.ts</path>
-  </file>
-  <file>
-    <path>src/auth/jwt.strategy.ts</path>
-  </file>
-  <file>
-    <path>src/auth/auth.guard.ts</path>
-  </file>
-  <file>
-    <path>src/models/user.model.ts</path>
-  </file>
-</args>
-</read_file>
-        ]]></tool_use>
-      </step>
-
-      <step number="4">
-        <description>UI/UX Analysis - Discover UI components</description>
-        <tool_use><![CDATA[
-<!-- Method 2: Pattern search for UI components -->
-<search_files>
-<path>src/components</path>
-<regex>(Login|Auth|Session|Password).*\.(tsx?|jsx?)</regex>
-<file_pattern>*.tsx</file_pattern>
-</search_files>
-        ]]></tool_use>
-        <tool_use><![CDATA[
-<read_file>
-<args>
-  <file>
-    <path>src/components/LoginForm.tsx</path>
-  </file>
-  <file>
-    <path>src/components/SessionManager.tsx</path>
-  </file>
-  <file>
-    <path>src/components/PasswordReset.tsx</path>
-  </file>
-</args>
-</read_file>
-        ]]></tool_use>
-      </step>
-
-      <step number="5">
-        <description>UI/UX Analysis - Map user interactions</description>
-        <tool_use><![CDATA[
-<search_files>
-<path>src/components</path>
-<regex>onClick|onSubmit|onChange|handleSubmit|validate</regex>
-</search_files>
-        ]]></tool_use>
-        <analysis>
-          - Form validation patterns
-          - User feedback mechanisms
-          - Error handling UI
-          - Loading states
-        </analysis>
-      </step>
-
-      <step number="6">
-        <description>UI/UX Analysis - Visual patterns and accessibility</description>
-        <tool_use><![CDATA[
-<search_files>
-<path>src</path>
-<regex>className=|style=|theme\.|aria-|role=</regex>
-<file_pattern>*.tsx</file_pattern>
-</search_files>
-        ]]></tool_use>
-        <tool_use><![CDATA[
-<search_files>
-<path>src/styles</path>
-<regex>\.login|\.auth|\.session</regex>
-<file_pattern>*.css</file_pattern>
-</search_files>
-        ]]></tool_use>
-      </step>
-
-      <step number="7">
-        <description>Extract API endpoints and configuration</description>
-        <tool_use><![CDATA[
-<search_files>
-<path>src/auth</path>
-<regex>@(Post|Get)\(['"]\/auth\/[^'"]+['"]|router\.(post|get)\(['"]\/auth\/[^'"]+['"]</regex>
-</search_files>
-        ]]></tool_use>
-        <tool_use><![CDATA[
-<search_files>
-<path>src</path>
-<regex>JWT_SECRET|JWT_EXPIRATION|AUTH_.*|process\.env\.\w*AUTH\w*</regex>
-</search_files>
-        ]]></tool_use>
-      </step>
-
-      <step number="8">
-        <description>Optional: Use semantic search for deeper insights</description>
-        <tool_use><![CDATA[
-<!-- Only if pattern searches miss important context -->
-<codebase_search>
-<query>authentication error handling user feedback messages</query>
-</codebase_search>
-        ]]></tool_use>
-        <note>Used when specific patterns don't capture all relevant error handling</note>
-      </step>
-
-      <step number="9">
-        <description>Create comprehensive extraction report</description>
-        <tool_use><![CDATA[
-<write_to_file>
-<path>EXTRACTION-authentication-system.md</path>
-<content>
-# Authentication System - Feature Extraction Report
-
-## Executive Summary
-The authentication system is a JWT-based security implementation that handles user registration, login, session management, and access control. It provides a comprehensive user experience with visual feedback, accessibility features, and robust error handling.
-
-## UI/UX Analysis
-
-### User Interface Components
-
-#### 1. Login Page (`src/components/LoginForm.tsx`)
-**Visual Layout:**
-- Centered card design with shadow (400px width)
-- Company logo at top
-- Form fields with floating labels
-- Primary blue theme (#1976d2)
-
-**Interactive Elements:**
-- Email input field
-  - Real-time validation (regex: /^[^\s@]+@[^\s@]+\.[^\s@]+$/)
-  - Error state: Red border and helper text
-  - Success state: Green checkmark icon
-- Password field
-  - Show/hide toggle button (eye icon)
-  - Minimum 8 characters validation
-  - Caps lock warning indicator
-- "Remember me" checkbox with 30-day persistence
-- "Forgot password?" link (underlined on hover)
-- Submit button
-  - Disabled state: Gray background until valid input
-  - Loading state: Spinner replaces text
-  - Success state: Checkmark animation
-
-**User Feedback:**
-- Loading overlay with spinner during authentication
-- Error messages appear with slide-down animation
-- Success toast notification (3s duration)
-- Form shake animation on error
-
-#### 2. Registration Form (`src/components/RegisterForm.tsx`)
-**Multi-Step Design:**
-- Progress bar showing 3 steps
-- Smooth slide transitions between steps
-- Back/Next navigation buttons
-
-**Step 1 - Account Info:**
-- Email field with async availability check
-- Password field with strength meter (5 levels)
-- Password confirmation with match validation
-
-**Step 2 - Personal Info:**
-- First/Last name fields
-- Optional phone with format mask
-- Country dropdown with flag icons
-
-**Step 3 - Terms & Submit:**
-- Terms of service scrollable text
-- Privacy policy link (opens modal)
-- Checkbox required for submission
-- Review summary before final submit
-
-**Visual Feedback:**
-- Field validation on blur
-- Progress saved in localStorage
-- Success confetti animation
-- Auto-redirect countdown (5s)
-
-#### 3. Session Management (`src/components/SessionManager.tsx`)
-**Device List UI:**
-- Card-based layout for each session
-- Device icons (FontAwesome)
-  - fa-mobile for mobile
-  - fa-desktop for desktop
-  - fa-tablet for tablet
-- Information displayed:
-  - Device name and browser
-  - IP address (partially masked)
-  - Last active (relative time)
-  - Location (city, country)
-
-**Interactive Features:**
-- Current device highlighted with blue border
-- Hover state shows "Revoke" button
-- Confirmation modal with device details
-- Bulk selection with checkboxes
-- "Revoke All" with double confirmation
-
-### User Experience Elements
-
-#### Visual Patterns
-**Theme System:**
-```css
---primary-color: #1976d2;
---error-color: #d32f2f;
---success-color: #388e3c;
---warning-color: #f57c00;
---text-primary: rgba(0, 0, 0, 0.87);
---text-secondary: rgba(0, 0, 0, 0.6);
-```
-
-**Animations:**
-- Page transitions: 300ms ease-in-out
-- Button hover: scale(1.02)
-- Error shake: 0.5s horizontal
-- Success checkmark: SVG path animation
-- Loading spinner: 1s rotation
-
-**Responsive Breakpoints:**
-- Mobile: < 768px (single column)
-- Tablet: 768px - 1024px
-- Desktop: > 1024px
-
-#### Accessibility Features
-**Keyboard Navigation:**
-- Tab order follows visual flow
-- Enter key submits forms
-- Escape closes modals
-- Arrow keys in dropdowns
-
-**Screen Reader Support:**
-- ARIA labels on all inputs
-- Live regions for errors
-- Role attributes for custom components
-- Descriptive button text
-
-**Visual Accessibility:**
-- 4.5:1 contrast ratio minimum
-- Focus indicators (2px outline)
-- Error icons for colorblind users
-- Scalable fonts (rem units)
-
-### User Workflows
-
-#### 1. First-Time Registration
-```
-Start → Landing Page → "Get Started" CTA
-  ↓
-Registration Form (Step 1)
-  → Email validation (async)
-  → Password strength check
-  → Real-time feedback
-  ↓
-Personal Info (Step 2)
-  → Optional fields clearly marked
-  → Format validation
-  ↓
-Terms Agreement (Step 3)
-  → Must scroll to enable checkbox
-  → Review summary
-  ↓
-Submit → Loading → Success
-  → Confetti animation
-  → Welcome email sent
-  → Auto-redirect (5s)
-  ↓
-Dashboard (First-time tour)
-```
-
-#### 2. Returning User Login
-```
-Start → Login Page
-  ↓
-Enter Credentials
-  → Email autocomplete
-  → Password manager integration
-  → "Remember me" option
-  ↓
-Submit → Loading (avg 1.2s)
-  ↓
-Success → Dashboard
-  OR
-Error → Inline feedback
-  → Retry with guidance
-  → "Forgot password?" option
-```
-
-#### 3. Password Reset Flow
-```
-Login Page → "Forgot password?"
-  ↓
-Modal Dialog
-  → Email input
-  → Captcha (if multiple attempts)
-  ↓
-Submit → "Check email" message
-  ↓
-Email Received (< 1 min)
-  → Secure link (1hr expiry)
-  ↓
-Reset Page
-  → New password requirements shown
-  → Strength meter
-  → Confirmation field
-  ↓
-Submit → Success → Login redirect
-```
-
-## Technical Details
-
-### Core Components
-1. **AuthController** (`src/auth/auth.controller.ts`)
-   - REST endpoints with validation decorators
-   - Rate limiting middleware
-   - CORS configuration
-
-2. **AuthService** (`src/auth/auth.service.ts`)
-   - JWT token generation/validation
-   - Bcrypt password hashing
-   - Session management logic
-
-3. **Security Implementation**
-   - JWT RS256 algorithm
-   - Refresh token rotation
-   - CSRF double-submit cookies
-   - XSS protection headers
-
-### API Endpoints
-| Method | Endpoint | Description | Rate Limit |
-|--------|----------|-------------|------------|
-| POST | /auth/register | New user registration | 3/hour |
-| POST | /auth/login | User authentication | 5/min |
-| POST | /auth/refresh | Token refresh | 10/min |
-| POST | /auth/logout | Session termination | None |
-| GET | /auth/profile | Current user data | None |
-| POST | /auth/reset-password | Password reset | 3/hour |
-
-### Configuration
-```env
-# Required
-JWT_SECRET=minimum-32-character-secret
-DATABASE_URL=postgresql://...
-
-# Optional with defaults
-JWT_EXPIRATION=15m
-REFRESH_TOKEN_EXPIRATION=7d
-BCRYPT_ROUNDS=10
-SESSION_MAX_AGE=30d
-MAX_SESSIONS_PER_USER=5
-```
-
-## Non-Technical Information
-
-### Business Rules
-1. **Account Creation**
-   - Unique email required
-   - Password: 8+ chars, mixed case, number, special
-   - Email verification within 24 hours
-   - Terms acceptance mandatory
-
-2. **Session Management**
-   - Max 5 concurrent sessions
-   - Idle timeout: 30 minutes
-   - Absolute timeout: 7 days
-   - Device trust for 30 days
-
-3. **Security Policies**
-   - Account lockout: 5 failed attempts (15 min)
-   - Password history: Last 3 not reusable
-   - 2FA optional but recommended
-   - Suspicious login notifications
-
-### Common User Scenarios
-
-#### Mobile Experience
-- Touch-optimized buttons (44px min)
-- Biometric login (Face ID/Touch ID)
-- Simplified navigation menu
-- Offline detection with retry
-- Push notification for new sessions
-
-#### Error Recovery
-- Network timeout: Auto-retry with backoff
-- Session expired: Smooth re-login flow
-- Form errors: Contextual help text
-- Server errors: Friendly messages with support link
-
-### Performance Metrics
-- Login response: 200ms (p50), 500ms (p95)
-- Page load: 1.2s (3G), 400ms (4G)
-- Token validation: < 10ms
-- Session check: < 50ms
-
-## Documentation Recommendations
-
-### Critical Areas for User Documentation
-1. **Getting Started Guide**
-   - Screenshots of each registration step
-   - Common email provider settings
-   - Password manager setup
-
-2. **Troubleshooting Section**
-   - "Why can't I log in?" flowchart
-   - Browser compatibility matrix
-   - Cookie/JavaScript requirements
-
-3. **Security Best Practices**
-   - How to spot phishing attempts
-   - Importance of unique passwords
-   - When to revoke sessions
-
-### Developer Integration Guide
-1. **API Authentication**
-   - Bearer token format
-   - Refresh token flow diagram
-   - Error response examples
-
-2. **SDK Examples**
-   - JavaScript/TypeScript
-   - Python
-   - Mobile (iOS/Android)
-
-## Integration Points
-- Email service for password reset and notifications
-- Session storage (Redis optional, in-memory default)
-- Rate limiting middleware
-- CORS configuration for cross-origin requests
-- Logging service for audit trails
-
-## Summary for Documentation Team
-This extraction report provides comprehensive details about the authentication system's current implementation. The system offers a complete user experience with visual feedback, accessibility features, and robust security measures. Key areas for user documentation include the multi-step registration process, session management features, and security policies. The technical implementation uses industry-standard JWT tokens with proper security measures.
-</content>
-<line_count>354</line_count>
-</write_to_file>
-        ]]></tool_use>
-      </step>
-    </workflow>
-
-    <key_takeaways>
-      <takeaway>Use flexible discovery methods - directory exploration and pattern search are primary tools</takeaway>
-      <takeaway>Comprehensive UI/UX analysis is essential for complete documentation</takeaway>
-      <takeaway>Document visual elements, interactions, and user feedback mechanisms</takeaway>
-      <takeaway>Include accessibility and responsive design considerations</takeaway>
-      <takeaway>Semantic search (codebase_search) is optional for deeper insights when needed</takeaway>
-      <takeaway>Organize findings to support documentation team's work</takeaway>
-    </key_takeaways>
-  </example>
-
-  <example name="documentation_verification_example">
-    <scenario>
-      Verify user-provided documentation about authentication UI/UX against the actual implementation.
-    </scenario>
-
-    <workflow>
-      <step number="1">
-        <description>User provides documentation to verify</description>
-        <user_input>
-          "Please verify our login documentation:
-          
-          'The login form provides a seamless experience with instant validation. Users see a green checkmark when their email is valid. The password field includes a strength indicator. After 3 failed attempts, users must wait 5 minutes before trying again.'"
-        </user_input>
-      </step>
-
-      <step number="2">
-        <description>Analyze the documentation claims</description>
-        <analysis>
-          Claims to verify:
-          - Instant email validation with green checkmark
-          - Password strength indicator on login
-          - 3 failed attempts triggers 5-minute wait
-        </analysis>
-      </step>
-
-      <step number="3">
-        <description>Find login UI components using directory exploration</description>
-        <tool_use><![CDATA[
-<list_files>
-<path>src/components</path>
-<recursive>false</recursive>
-</list_files>
-        ]]></tool_use>
-        <tool_use><![CDATA[
-<search_files>
-<path>src/components</path>
-<regex>Login|SignIn|Auth.*Form</regex>
-<file_pattern>*.tsx</file_pattern>
-</search_files>
-        ]]></tool_use>
-      </step>
-
-      <step number="4">
-        <description>Examine login form implementation</description>
-        <tool_use><![CDATA[
-<read_file>
-<args>
-  <file>
-    <path>src/components/LoginForm.tsx</path>
-  </file>
-  <file>
-    <path>src/components/LoginForm.css</path>
-  </file>
-</args>
-</read_file>
-        ]]></tool_use>
-        <findings>
-          - Email validation exists but shows red X, not green checkmark
-          - No password strength indicator on login form (only on registration)
-          - Account lockout is after 5 attempts, not 3
-          - Lockout duration is 15 minutes, not 5
-        </findings>
-      </step>
-
-      <step number="5">
-        <description>Verify validation behavior</description>
-        <tool_use><![CDATA[
-<search_files>
-<path>src/components</path>
-<regex>validateEmail|emailValid|checkmark|strength.*indicator</regex>
-</search_files>
-        ]]></tool_use>
-        <tool_use><![CDATA[
-<search_files>
-<path>src/auth</path>
-<regex>failed.*attempts|lockout|rate.*limit</regex>
-</search_files>
-        ]]></tool_use>
-      </step>
-
-      <step number="6">
-        <description>Create verification report</description>
-        <tool_use><![CDATA[
-<write_to_file>
-<path>VERIFICATION-login-documentation.md</path>
-<content>
-# Login Documentation - Verification Report
-
-## Overall Assessment: Needs Significant Updates
-
-## Summary
-The login documentation contains several inaccuracies about the UI/UX implementation that could confuse users and lead to poor user experience.
-
-## Critical Inaccuracies
-
-### 1. Email Validation Feedback
-**Documentation States**: "Users see a green checkmark when their email is valid"
-**Actual Implementation**: Red X icon for invalid emails, no positive feedback
-- Location: `src/components/LoginForm.tsx:45-52`
-- Current behavior: Only shows error states
-- Missing: Success indicator implementation
-- **Impact**: Users don't get positive reinforcement for correct input
-
-### 2. Password Strength Indicator
-**Documentation States**: "The password field includes a strength indicator"
-**Actual Implementation**: No strength indicator on login form
-- Location: Checked `src/components/LoginForm.tsx`
-- Strength indicator only exists in `RegisterForm.tsx`
-- Login form has basic password field only
-- **Impact**: Sets incorrect user expectations
-
-### 3. Failed Login Attempts
-**Documentation States**: "After 3 failed attempts, users must wait 5 minutes"
-**Actual Implementation**: 5 attempts, 15-minute lockout
-- Location: `src/auth/services/auth.service.ts:234`
-- Code: `MAX_LOGIN_ATTEMPTS = 5`
-- Code: `LOCKOUT_DURATION = 15 * 60 * 1000 // 15 minutes`
-- **Impact**: Users may be confused about actual security policy
-
-## UI/UX Elements Found But Not Documented
-
-### 1. Loading States
-- Spinner overlay during authentication
-- Button disabled state during submission
-- These improve perceived performance
-
-### 2. Remember Me Feature
-- 30-day persistent session option
-- Stored in secure cookie
-- Not mentioned in documentation
-
-### 3. Caps Lock Warning
-- Visual indicator when caps lock is on
-- Helps prevent login failures
-- Important accessibility feature
-
-## Recommendations
-
-### Immediate Corrections Needed
-1. **Email Validation**:
-   ```
-   CORRECT: "The email field shows a red error icon for invalid formats. Valid emails are accepted without visual confirmation."
-   ```
-
-2. **Password Features**:
-   ```
-   CORRECT: "The login form has a standard password field with show/hide toggle. Password strength indicators are only shown during registration."
-   ```
-
-3. **Security Policy**:
-   ```
-   CORRECT: "After 5 failed login attempts, accounts are temporarily locked for 15 minutes to prevent brute force attacks."
-   ```
-
-### Suggested Additions
-1. Document the loading states and visual feedback
-2. Explain the "Remember Me" functionality
-3. Mention the Caps Lock warning feature
-4. Add screenshots of actual UI states
-
-## Technical References
-- Login Form Component: `src/components/LoginForm.tsx`
-- Styles: `src/components/LoginForm.css`
-- Auth Service: `src/auth/services/auth.service.ts`
-- Rate Limiting: `src/middleware/rateLimiter.ts`
-
-## Visual Discrepancies
-- Documentation implies more visual feedback than implemented
-- Color scheme in docs doesn't match actual theme
-- Missing documentation for error message styling
-
-## Conclusion
-The documentation needs updates to accurately reflect the current login experience. The actual implementation is more security-focused (5 attempts, 15-min lockout) but less visually rich (no success indicators) than documented.
-</content>
-<line_count>95</line_count>
-</write_to_file>
-        ]]></tool_use>
-      </step>
-    </workflow>
-
-    <key_takeaways>
-      <takeaway>Always verify UI/UX claims against actual component implementation</takeaway>
-      <takeaway>Check both visual elements and behavioral logic</takeaway>
-      <takeaway>Look for undocumented features that users might expect</takeaway>
-      <takeaway>Provide specific corrections with code references</takeaway>
-      <takeaway>Consider the impact of inaccuracies on user experience</takeaway>
-    </key_takeaways>
-  </example>
-
-  <example name="api_endpoint_extraction">
-    <scenario>
-      Extract comprehensive API documentation including endpoints, request/response formats, and error handling.
-    </scenario>
-
-    <workflow>
-      <step number="1">
-        <description>Discover API structure using flexible methods</description>
-        <tool_use><![CDATA[
-<!-- Method 1: Look for common API directories -->
-<list_files>
-<path>src</path>
-<recursive>false</recursive>
-</list_files>
-        ]]></tool_use>
-        <tool_use><![CDATA[
-<list_files>
-<path>src/api</path>
-<recursive>true</recursive>
-</list_files>
-        ]]></tool_use>
-      </step>
-
-      <step number="2">
-        <description>Find all API routes using pattern search</description>
-        <tool_use><![CDATA[
-<search_files>
-<path>src</path>
-<regex>(app|router)\.(get|post|put|patch|delete|all)\s*\(\s*['"`]([^'"`]+)['"`]</regex>
-</search_files>
-        ]]></tool_use>
-      </step>
-
-      <step number="3">
-        <description>Extract request validation schemas</description>
-        <tool_use><![CDATA[
-<search_files>
-<path>src</path>
-<regex>@(Body|Query|Param|Headers)\(|joi\.object|yup\.object|zod\.object</regex>
-</search_files>
-        ]]></tool_use>
-      </step>
-
-      <step number="4">
-        <description>Analyze error handling and responses</description>
-        <tool_use><![CDATA[
-<search_files>
-<path>src</path>
-<regex>@ApiResponse|response\.status\(|res\.status\(|throw new.*Error</regex>
-</search_files>
-        ]]></tool_use>
-      </step>
-
-      <step number="5">
-        <description>Optional: Semantic search for middleware and auth</description>
-        <tool_use><![CDATA[
-<!-- Use when pattern search might miss complex middleware chains -->
-<codebase_search>
-<query>API middleware authentication authorization guards</query>
-</codebase_search>
-        ]]></tool_use>
-      </step>
-
-      <step number="6">
-        <description>Generate API extraction report</description>
-        <output>
-          - Complete endpoint inventory with methods and paths
-          - Request/response schemas with examples
-          - Authentication requirements per endpoint
-          - Rate limiting and throttling rules
-          - Error response formats and codes
-          - API versioning strategy
-        </output>
-      </step>
-    </workflow>
-  </example>
-
-  <example name="ui_component_library_extraction">
-    <scenario>
-      Document a React component library including props, styling, accessibility, and usage patterns.
-    </scenario>
-
-    <workflow>
-      <step number="1">
-        <description>Discover component structure</description>
-        <tool_use><![CDATA[
-<list_files>
-<path>src/components</path>
-<recursive>true</recursive>
-</list_files>
-        ]]></tool_use>
-      </step>
-
-      <step number="2">
-        <description>Analyze component interfaces and props</description>
-        <tool_use><![CDATA[
-<search_files>
-<path>src/components</path>
-<regex>interface\s+\w+Props|type\s+\w+Props|export\s+(default\s+)?function|export\s+const</regex>
-<file_pattern>*.tsx</file_pattern>
-</search_files>
-        ]]></tool_use>
-      </step>
-
-      <step number="3">
-        <description>Extract styling and theme usage</description>
-        <tool_use><![CDATA[
-<search_files>
-<path>src/components</path>
-<regex>styled\.|makeStyles|className=|sx=|css=</regex>
-</search_files>
-        ]]></tool_use>
-      </step>
-
-      <step number="4">
-        <description>Document accessibility features</description>
-        <tool_use><![CDATA[
-<search_files>
-<path>src/components</path>
-<regex>aria-|role=|tabIndex|alt=|htmlFor=</regex>
-</search_files>
-        ]]></tool_use>
-      </step>
-
-      <step number="5">
-        <description>Find usage examples and stories</description>
-        <tool_use><![CDATA[
-<search_files>
-<path>src</path>
-<regex>\.stories\.|\.story\.|examples?/|demo/</regex>
-<file_pattern>*.tsx</file_pattern>
-</search_files>
-        ]]></tool_use>
-      </step>
-
-      <step number="6">
-        <description>Create component library report</description>
-        <output>
-          - Component hierarchy and relationships
-          - Props documentation with types and defaults
-          - Styling system and customization options
-          - Accessibility compliance checklist
-          - Interactive examples and code snippets
-          - Best practices and anti-patterns
-          - Browser compatibility notes
-        </output>
-      </step>
-    </workflow>
-  </example>
-
-  <best_practices>
-    <practice name="flexible_discovery">
-      <description>Use the most appropriate discovery method</description>
-      <guidelines>
-        <guideline>Start with directory exploration for well-organized codebases</guideline>
-        <guideline>Use pattern search for specific syntax or naming conventions</guideline>
-        <guideline>Apply file-based search when you know exact locations</guideline>
-        <guideline>Reserve semantic search for complex conceptual queries</guideline>
-      </guidelines>
-    </practice>
-
-    <practice name="comprehensive_ui_ux_coverage">
-      <description>Ensure complete UI/UX documentation</description>
-      <checklist>
-        <item>Visual design and layout</item>
-        <item>Interactive elements and states</item>
-        <item>User feedback mechanisms</item>
-        <item>Accessibility features</item>
-        <item>Responsive behavior</item>
-        <item>Animation and transitions</item>
-        <item>Error states and recovery</item>
-        <item>Loading and progress indicators</item>
-      </checklist>
-    </practice>
-
-    <practice name="verification_thoroughness">
-      <description>Verify all aspects of documentation claims</description>
-      <checklist>
-        <item>Technical accuracy of code examples</item>
-        <item>UI element descriptions match implementation</item>
-        <item>User workflows reflect actual behavior</item>
-        <item>Configuration values are current</item>
-        <item>Error messages match code</item>
-        <item>Performance claims are realistic</item>
-      </checklist>
-    </practice>
-  </best_practices>
-</complete_extraction_examples>

.roo/rules-docs-extractor/7_user_friendly_examples.xml

@@ -1,218 +0,0 @@
-<user_friendly_examples>
-  <overview>
-    Examples for creating user-focused, practical documentation.
-  </overview>
-
-  <writing_principles>
-    <principle name="benefits_over_features">
-      <bad>The concurrent file read feature uses parallel processing.</bad>
-      <good>Read multiple files at once, reducing interruptions.</good>
-    </principle>
-
-    <principle name="use_scenarios">
-      <bad>This improves efficiency.</bad>
-      <good>Instead of approving 10 file reads one-by-one, approve them all at once.</good>
-    </principle>
-
-    <principle name="hide_implementation_details">
-      <bad>The feature uses a thread pool with configurable concurrency limits.</bad>
-      <good>Roo reads up to 100 files at once (changeable in settings).</good>
-    </principle>
-
-    <principle name="direct_tone">
-      <bad>Users must configure the concurrent file read limit parameter.</bad>
-      <good>Adjust how many files Roo reads at once in settings.</good>
-    </principle>
-  </writing_principles>
-
-  <structure_examples>
-    <example name="feature_intro">
-      <template><![CDATA[
-# [Feature Name]
-
-[One-sentence description of what it does.]
-
-### Key Features
-- [Benefit 1]
-- [Benefit 2]
-- [Benefit 3]
-
----
-      ]]></template>
-    </example>
-
-    <example name="use_case">
-      <template><![CDATA[
-## Use Case
-
-**Before**: [Description of the old way]
-- [Pain point]
-- [Pain point]
-
-**Now**: [Description of the new way]
-      ]]></template>
-    </example>
-
-    <example name="configuration">
-      <template><![CDATA[
-## Configuration
-
-Customize this feature in settings:
-
-1. **[Setting Name]**
-   - **Does**: [Plain language explanation.]
-   - **Default**: [Default value.] (Works for most.)
-   - **Change if**: [Specific scenarios to adjust this.]
-
-2. **[Setting Name]**
-   - **Does**: [Plain language explanation.]
-   - **Default**: [Default value.]
-   - **Change if**: [Specific use case.]
-      ]]></template>
-    </example>
-
-    <example name="faq">
-      <template><![CDATA[
-## FAQ
-
-**"[User question]"**
-- [Direct answer.]
-- [Optional tip.]
-
-**"[Another question]"**
-- [Direct answer.]
-- [Optional link.]
-      ]]></template>
-    </example>
-
-    <example name="troubleshooting">
-      <template><![CDATA[
-## Troubleshooting
-
-### [Problem symptom]
-**Cause**: [Brief explanation.]
-**Fix**: [Immediate solution.]
-**Alternate fix**: [Alternative solution.]
-
-### [Another issue]
-**Scenario**: [When this happens.]
-**Solution**:
-1. [Step 1]
-2. [Step 2]
-      ]]></template>
-    </example>
-
-  </structure_examples>
-
-  <tone_examples>
-    <explanations>
-      <example context="limit">
-        <technical>The system imposes a hard limit of 100 concurrent operations.</technical>
-        <direct>Roo handles up to 100 files at once.</direct>
-      </example>
-
-      <example context="error">
-        <technical>Error: Maximum concurrency threshold exceeded.</technical>
-        <direct>Too many files requested. Lower the file limit in settings.</direct>
-      </example>
-
-      <example context="benefit">
-        <technical>Reduces API call overhead through request batching.</technical>
-        <direct>Get answers faster by reading all needed files at once.</direct>
-      </example>
-    </explanations>
-
-    <visuals>
-      <emojis>
-        <when>Error: ⚠️</when>
-        <when>Tip: 💡</when>
-        <when>Note: 📝</when>
-        <when>Security: 🔒</when>
-      </emojis>
-
-      <formatting>
-        <bold>For emphasis</bold>
-        <code>For settings, file paths, or commands</code>
-        <blockquotes>For callouts or warnings</blockquotes>
-      </formatting>
-    </visuals>
-  </tone_examples>
-
-  <real_world_example>
-    <title>Concurrent File Reads Doc</title>
-    <content><![CDATA[
-# Concurrent File Reads
-
-Read multiple files from your workspace in a single step.
-
-### Key Features
-- Read up to 100 files in one request.
-- Enabled by default for faster workflow.
-- Configurable to match system capabilities.
-
----
-
-## Use Case
-
-**Before**: Multiple, sequential requests to read files:
-- "Read `src/app.js`?" → Approve
-- "Read `src/utils.js`?" → Approve
-- "Read `src/config.json`?" → Approve
-
-**Now**: Roo asks once to read all related files.
-
-## How it Works
-
-Roo automatically identifies and reads relevant files together for tasks requiring multi-file context, such as:
-
-- Understanding components split across multiple files.
-- Refactoring code with dependencies.
-- Answering questions requiring broad project context.
-
-The [`read_file`](/tools/read-file) tool accepts multiple files in a single request.
-
----
-
-## Configuration
-
-Customize in Roo's settings:
-
-1. **Enable/Disable Concurrent File Reads**
-   - **Does**: Toggles whether Roo can read multiple files at once.
-   - **Default**: Enabled.
-   - **Disable if**: Using a less capable AI model or requiring more access control.
-
-2. **Concurrent File Reads Limit**
-   - **Does**: Sets max number of files Roo can read at once.
-   - **Default**: 100.
-   - **Adjust**: Lower for memory constraints; raise for very large projects.
-
----
-
-## FAQ
-
-**"Too many files are requested at once."**
-- Lower the file limit in settings.
-- Deny individual files in the batch dialog.
-
-**"Some files were denied but others were approved."**
-- Normal behavior. Roo works with approved files.
-- Files may be blocked by `.rooignore` settings.
-
-**"Does this use more memory?"**
-- Yes, but the impact is usually minimal.
-- If you see slowdowns, reduce the file limit.
-
-    ]]></content>
-  </real_world_example>
-
-  <checklist>
-    <item>Does it start with benefits?</item>
-    <item>Are technical terms avoided?</item>
-    <item>Is the tone direct?</item>
-    <item>Are there practical examples?</item>
-    <item>Are sections short and scannable?</item>
-    <item>Does it answer user questions?</item>
-    <item>Is help accessible?</item>
-  </checklist>
-</user_friendly_examples>

.roomodes

@@ -94,19 +94,19 @@ customModes:
       You are Roo, a documentation analysis specialist with two primary functions:
       1. Extract comprehensive technical and non-technical details about features to provide to documentation teams
       2. Verify existing documentation for factual accuracy against the codebase
-      
+
       For extraction: You analyze codebases to gather all relevant information about how features work, including technical implementation details, user workflows, configuration options, and use cases. You organize this information clearly for documentation teams to use.
-      
+
       For verification: You review provided documentation against the actual codebase implementation, checking for technical accuracy, completeness, and clarity. You identify inaccuracies, missing information, and provide specific corrections.
-      
+
       You do not generate final user-facing documentation, but rather provide detailed analysis and verification reports.
-    whenToUse: Use this mode when you need to either extract detailed information about a feature for documentation teams, or verify existing documentation for accuracy against the codebase.
+    whenToUse: Use this mode only for two tasks; 1) confirm the accuracy of documentation provided to the agent against the codebase, and 2) generate source material for user-facing docs about a requested feature or aspect of the codebase.
     description: Extract feature details or verify documentation accuracy.
     groups:
       - read
       - - edit
-        - fileRegex: (DOCS-TEMP-.*\.md$|\.roo/docs-extractor/.*\.md$)
-          description: Temporary documentation extraction files only
+        - fileRegex: (EXTRACTION-.*\.md$|VERIFICATION-.*\.md$|DOCS-TEMP-.*\.md$|\.roo/docs-extractor/.*\.md$)
+          description: Extraction/Verification report files only (source-material), plus legacy DOCS-TEMP
       - command
       - mcp
   - slug: pr-fixer