Lesson 3: AI Pair Programming Patterns

The Problem with Unstructured AI Help

When you ask AI to "add a new feature" without context:

• AI doesn't know your architecture constraints
• AI might suggest changes that break dependencies
• AI doesn't understand your team's conventions

Architecture-Aware AI Interactions

Pattern 1: Before Changing X, Ask About Dependencies

You: "What would break if I change UserService?"

AI (with Sruja context): "Changing UserService would affect:
- LoginComponent (depends on UserService)
- ProfileUI (calls UserService.getProfile())
- NotificationService (receives user events)

You should also update:
- user-auth contract (API boundary)
- test/UserService.test.ts (affected tests)
"

Pattern 2: Use AI to Explore, Then Validate

# AI helps explore
"What does the checkout flow look like?"

# AI shows understanding
"Based on your architecture, checkout involves:
- CartService -> PaymentService -> OrderService

Shall I trace through each step?"

Then validate with Sruja:

# After AI proposes changes
sruja lint
sruja drift -r .

Pattern 3: AI-Assisted Impact Analysis

# Before making a big change
"Use sruja impact to show me blast radius of removing the legacy import service"

# AI calls MCP tool
# Blast radius analysis shown

Pattern 4: Ask for Sruja DSL, Then Validate

You: "Generate Sruja DSL for a new notification service"

AI: [generates Sruja code]

You: "Validate this with sruja lint and check it fits our patterns"

Pattern 5: AI as Architecture Reviewer

You: "Review this code change for architectural compliance"

AI with context: [checks against policies, finds issues]
"1. This change violates your 'no-direct-db-access' policy
2. New dependency creates circular reference with BillingService
3. Missing required 'tech' field in container definition"

Effective Prompts for Architecture Context

Workflow: AI-Assisted Feature Development

1. Define the task

   "I need to add a new payment method to checkout"
   

2. AI explores context

   AI: "Let me check your PaymentContract and checkout flow..."
   

3. AI proposes with constraints

   AI: "Based on your architecture, this requires:
   - Adding endpoint to PaymentContract
   - Updating FraudDetection rules
   - New scenario test for the payment flow"
   

4. Human approves

   "Sounds right, implement it"
   

5. AI implements

6. Human validates with Sruja

   sruja lint
   sruja validate --scenarios
   

Anti-Patterns to Avoid

Module Complete!

You've completed the AI Editor Integration module. You now understand:

• ✅ Setting up Sruja MCP server
• ✅ Building architecture context for AI
• ✅ Using context-driven AI assistance
• ✅ Effective AI pair programming patterns

This module completes the Agentic AI course with practical AI editor integration skills.