Test lib refactor

.cursor/rules/010-docs-memory-knowledge-management.mdc

@@ -138,6 +138,7 @@ When planning documentation updates:
    - No TODOs or placeholders
    - Follow linting rules
    - Make minimal changes for the current task
+   - Assume components or utilities exist and search for them first before creating
 
 3. Documentation First:
    - Update documentation before code changes
@@ -267,33 +268,6 @@ When planning documentation updates:
    cp "docs/templates/task-plan-template.md" "docs/working-memory/open/${feature-name}-$(date +%Y%m%d)/.plan"
    ```
 
-2. Status Updates:
-   ```markdown
-   ## Current Status
-   ### PowerShell: $(Get-Date -Format "yyyy-MM-dd HH:mm")
-   ### Bash: $(date "+%Y-%m-%d %H:%M")
-
-   **Status**: In Progress
-
-   - What's working: {current state}
-   - What's not: {current issues}
-   - Blocking issues: {if any}
-   - Next actions: {immediate next steps}
-   ```
-
-3. Progress Tracking:
-   ```markdown
-   ## Progress History
-   ### PowerShell: $(Get-Date -Format "yyyy-MM-dd HH:mm") - {Brief Title}
-   ### Bash: $(date "+%Y-%m-%d %H:%M") - {Brief Title}
-
-   - ✓ Completed: {work completed}
-   - 🤔 Decisions: {decisions made}
-   - ❌ Issues: {problems encountered}
-   - 📚 Documentation: {documentation updates}
-   - ⏭️ Next: {next steps}
-   ```
-
 ## Validation Requirements
 
 1. Documentation Checks:
@@ -402,56 +376,7 @@ When planning documentation updates:
    - Context: {context/AuthContext}
    ```
 
-## Error Prevention
-
-### Common Documentation Pitfalls
-
-1. Timestamp Issues:
-   ```markdown
-   Common Errors:
-   - Manual timestamp entry
-   - Inconsistent formats
-   - Missing timezone information
-   - Backdated entries
-
-   Prevention:
-   - Always use Get-Date command
-   - Follow standard format
-   - Update in real-time
-   - Never modify timestamps
-   ```
-
-2. Cross-Reference Failures:
-   ```markdown
-   Common Errors:
-   - Broken links
-   - Missing references
-   - Circular dependencies
-   - Outdated references
-
-   Prevention:
-   - Validate links before commit
-   - Use relative paths
-   - Check reference graph
-   - Regular link audits
-   ```
-
-3. Documentation Debt:
-   ```markdown
-   Common Issues:
-   - Incomplete updates
-   - Outdated examples
-   - Missing sections
-   - Inconsistent formatting
-
-   Prevention:
-   - Complete documentation before task completion
-   - Regular documentation reviews
-   - Template compliance checks
-   - Automated formatting
-   ```
-
-### Best Practices for Error Prevention
+## Best Practices for Error Prevention
 
 1. Pre-Commit Checklist:
    ```markdown
@@ -463,22 +388,7 @@ When planning documentation updates:
    - [ ] Cross-references updated
    ```
 
-2. Regular Maintenance:
-   ```markdown
-   Weekly Tasks:
-   - Validate all links
-   - Update timestamps
-   - Check templates
-   - Review changes
-
-   Monthly Tasks:
-   - Full documentation audit
-   - Template updates
-   - Archive old content
-   - Update examples
-   ```
-
-3. Quality Assurance:
+2. Quality Assurance:
    ```markdown
    Review Process:
    1. Self-review documentation changes

.cursor/rules/011-docs-plan-management.mdc

@@ -66,52 +66,6 @@ When planning implementations:
    - Cross-reference maintenance
    - Version control practices
 
-## Documentation Standards
-
-### Component Documentation
-```typescript
-/**
- * LoginForm Component
- * @component
- * @description Handles user authentication through form submission
- *
- * @example
- * ```tsx
- * <LoginForm
- *   onSuccess={handleSuccess}
- *   redirectPath="/dashboard"
- * />
- * ```
- */
-interface LoginFormProps {
-  /** Callback fired when login succeeds */
-  onSuccess: (user: User) => void;
-  /** Path to redirect after successful login */
-  redirectPath?: string;
-}
-```
-
-### State Management Documentation
-```typescript
-/**
- * Authentication State
- * @typedef {Object} AuthState
- *
- * @example
- * ```tsx
- * const [authState, dispatch] = useReducer(authReducer, initialState);
- * ```
- */
-interface AuthState {
-  /** Current user object, null if not authenticated */
-  user: User | null;
-  /** Loading state for auth operations */
-  loading: boolean;
-  /** Last error message if any */
-  error?: string;
-}
-```
-
 ### Type Documentation Requirements
 1. Required Documentation:
    - Every exported type must have JSDoc comment
@@ -317,21 +271,6 @@ actions:
                - Created security followup
                </example>
 
-               <example type="invalid">
-               # Bad: Incomplete Milestone Addition
-               1. Added milestone without questions
-               2. Updated only plan.md
-               3. No implementation details
-               4. No security consideration
-               5. Missing dependencies
-
-               ## Missing:
-               - No scope definition
-               - No security review
-               - Incomplete documentation
-               - No dependency check
-               </example>
-
          c) Risk Management:
             - Potential blockers
             - Mitigation strategies
@@ -382,23 +321,6 @@ actions:
               - Link verification process
               - Content accuracy review
 
-         f) Specialized Testing:
-            - For API issues: Follow api_debugging_methodology test patterns
-              ```ruby
-              # Example API test structure from api_debugging_methodology
-              RSpec.describe ApiClient do
-                describe 'configuration' do
-                  it 'loads environment variables' do
-                    # Test env vars
-                  end
-
-                  it 'configures the client properly' do
-                    # Test client setup
-                  end
-                end
-              end
-              ```
-
       4. Documentation Template:
          ```markdown
          ## Task Status Notation
@@ -533,6 +455,7 @@ actions:
             - Must be updated in real-time as work progresses
             - Use [X] for completed items, [ ] for pending items
             - Include timestamps for all updates
+            - ALWAYS run a command to get timestamps, NEVER estimate timestamps in .plan or plan.md files
 
             Structure and Update Flow:
             ```markdown
@@ -566,10 +489,11 @@ actions:
 
             Update Rules:
             1. Current Status:
-               - Update timestamp and status first
+               - ONLY show most recent status
+               - Update timestamp and status
                - Reflect current state of work
-               - List immediate achievements and challenges
-               - NEVER duplicate completed items here
+               - Move previous status updates to Progress History
+               - Consolidate related updates under same timestamp
 
             2. Implementation Steps:
                - Mark items complete with [X] in-place
@@ -579,6 +503,8 @@ actions:
 
             3. Progress History:
                - Add new entries at TOP
+               - Include previous status updates as historical entries
+               - Consolidate related updates under same timestamp
                - Only record MAJOR milestones
                - Keep entries concise
                - Focus on decisions and learnings
@@ -614,30 +540,6 @@ actions:
             - ⏭️ Next: Begin configuration updates
             ```
 
-            Example of Incorrect Updates:
-            ```markdown
-            ## Current Status
-            ### 2025-03-30 21:30
-
-            **Status**: In Progress
-            - What's working:
-              - [X] Document current structure  # DON'T duplicate checklist here
-              - [X] Analyze dependencies
-            - What's not: Import paths
-            - Next actions: Configuration
-
-            ## Implementation Steps
-            1. Preparation Phase  # DON'T remove structure
-               - Document current structure
-               - Analyze dependencies
-
-            ## Progress History
-            ### 2025-03-30 21:30 - Implementation Progress
-            - [X] Document current structure  # DON'T duplicate checklist here
-            - [X] Analyze dependencies
-            - [ ] Update configuration  # DON'T mix pending items
-            ```
-
          b) Main Project Plan (plan.md):
             - Located in /docs/working-memory/plan.md
             - Must be synchronized with individual task plans