workflows

Workflow Patterns for Development Scenarios

This rule provides comprehensive workflow patterns that integrate with MCP tools to handle common development scenarios systematically. Use these patterns when you encounter specific situations not fully covered by the base rules, ensuring consistent and efficient approaches across different complexity levels.

1. Code Investigation & Debugging Workflows

1.1 TypeScript Compilation Errors Pattern

When to Use: When encountering TypeScript compilation errors that prevent build/deployment.

Workflow Sequence:

graph TD
    A[TS Compilation Error] --> B{analyze_file - health check}
    B --> C{Health status?}
    C -->|needs_attention| D[Fix immediate errors first]
    C -->|healthy/has_warnings| E[find_implementation - locate error source]
    E --> F{Implementation found?}
    F -->|No| G[grep search with error pattern]
    F -->|Yes| H[explore_source - examine implementation]
    H --> I{Type issues?}
    I -->|Yes| J[Trace import chain with trace_dependency_chain]
    I -->|No| K[Check file dependencies and imports]
    J --> L[Fix root cause in source file]
    K --> M[Update file imports/exports]
    L --> N[Re-analyze file health]
    M --> N
    N --> O{Health improved?}
    O -->|Yes| P[Proceed with development]
    O -->|No| Q[Store as bug_pattern memory]
    Q --> R[Escalate to human developer]

Tool Chain:

• analyze_file (MANDATORY - first step)
• find_implementation → explore_source → trace_dependency_chain
• grep (for complex pattern searches)
• store_memory (document solutions as bug_pattern)

Success Criteria:

• File health status changes from needs_attention to healthy
• No TypeScript compilation errors
• Solution documented for future reference

1.2 Runtime Error Resolution Pattern

When to Use: When application crashes or behaves unexpectedly during execution.

Workflow Sequence:

graph TD
    A[Runtime Error Occurs] --> B[analyze_file - current state]
    B --> C{Error logs available?}
    C -->|Yes| D[grep for error messages]
    C -->|No| E[start dev server with debug logging]
    D --> F[search_github_issues for similar errors]
    E --> F
    F --> G{Solutions found?}
    G -->|Yes| H[Apply community solutions]
    G -->|No| I[find_implementation of problematic function]
    I --> J[explore_source of implementation]
    J --> K{Logic error found?}
    K -->|Yes| L[Fix logic and retest]
    K -->|No| M[make_api_request to test specific endpoints]
    L --> N[Run comprehensive tests]
    M --> O{API working?}
    O -->|Yes| P[Error is in UI layer]
    O -->|No| Q[Check database connections]
    P --> R[Update client-side error handling]
    Q --> S[Fix database issues]
    N --> T{Tests pass?}
    R --> T
    S --> T
    T -->|Yes| U[store_memory as bug_pattern]
    T -->|No| V[Escalate with detailed context]