User: "How do we handle image uploads?"

[Cross-Reference Search]:
1. Context7: @uppy/core documentation
   ✓ Found: File upload patterns, drag-and-drop API

2. Cognee Memory: agent_research dataset
   ✓ Found: Previous research on image compression (2026-01-05)
   ✓ Found: Performance benchmarks for Uppy vs native input

3. Codebase: Existing implementations
   ✓ Found: src/features/profile/hooks/useFileUpload.ts
   ✓ Found: src/features/profile/components/AvatarUpload.tsx

4. README: Project docs
   ✓ Found: docs/IMAGE_UPLOAD_GUIDELINES.md

[Synthesized Answer]:
Current implementation uses @uppy/core with custom useFileUpload hook.
Existing pattern supports: drag-and-drop, progress tracking, 5MB limit.
Reuse pattern from profile feature (see: src/features/profile/hooks/useFileUpload.ts)

User: "Find authentication implementation"

[Standard Output]:
Found in: src/context/AuthContext.tsx, src/services/auth.ts

[NEW Enhanced Output]:
Found in: src/context/AuthContext.tsx, src/services/auth.ts

IMPLEMENTATION PATTERN:
┌─────────────────────────────────────────────┐
│ AuthContext (State Management)              │
│   ↓ provides                                │
│ useAuth() hook                              │
│   ↓ calls                                   │
│ authService (Supabase integration)          │
│   ↓ returns                                 │
│ User object + JWT token                     │
└─────────────────────────────────────────────┘

RECOMMENDED USAGE:
```typescript
import { useAuth } from '@/context/AuthContext';

function ProtectedPage() {
  const { user, signOut } = useAuth();

  if (!user) {
    return <Redirect to="/login" />;
  }

  return <Dashboard user={user} />;
}

---

### 3. Research History Tracking for Recurring Questions

**Cognee-Powered Learning System**:

Track all research queries and results. If the same question is asked again:
1. Return cached result instantly (0 cost)
2. Check if information is still current
3. Update with any new findings

**Example**:

**Update Detection**:
If related files changed since last research, automatically re-research and update cache.

---

### 4. Automatic Context7 + Serena Hybrid Search

**Intelligent Tool Selection**:

Automatically choose the best search strategy:

| Query Type | Primary Tool | Secondary Tool | Example |
|------------|-------------|----------------|---------|
| Library API | Context7 | Cognee | "React Query mutations" |
| Internal code | Serena | Grep | "useAuth implementation" |
| Patterns | Cognee | Grep | "Error handling patterns" |
| Mixed | Context7 + Serena | Cognee | "How to integrate Stripe?" |

**Example**:

const mutation = useMutation({
  mutationFn: (data) => api.post('/users', data),
  onSuccess: () => queryClient.invalidateQueries(['users'])
});

// Most common pattern in this codebase:
const { mutate, isLoading } = useMutation({
  mutationFn: createUser,
  onSuccess: () => {
    toast.success('User created');
    queryClient.invalidateQueries(['users']);
  },
  onError: (error) => handleApiError(error)
});

---

### 5. Output Format Options

**Structured Summaries**:
```markdown
## Research Summary: Authentication System

### Overview
Supabase-based authentication with JWT tokens

### Key Components
1. AuthContext (src/context/AuthContext.tsx)
   - Purpose: Global auth state
   - Exports: useAuth hook, AuthProvider
2. Auth Service (src/services/auth.ts)
   - Purpose: Supabase integration
   - Methods: signIn, signUp, signOut, resetPassword

### Usage Pattern
[Code example]

### Related Files
- Protected routes: src/components/ProtectedRoute.tsx
- Auth modal: src/components/auth/AuthModal.tsx

## Comparison: Image Upload Libraries

| Feature | Uppy | react-dropzone | native <input> |
|---------|------|----------------|----------------|
| Drag-drop | ✅ Built-in | ✅ Built-in | ❌ Manual |
| Progress | ✅ Built-in | ❌ Manual | ❌ Manual |
| Bundle size | 120KB | 25KB | 0KB |
| Current usage | ✅ Profile page | ❌ Not used | ✅ Forms |
| Recommendation | ✅ Use for complex | ⚠️ Consider for simple | ❌ Avoid |

**Verdict**: Use Uppy (already in bundle, consistent with profile feature)

## Decision: Migrate to Zustand vs Keep React Context?

### Evaluation Criteria (Weighted)

| Criterion | Weight | Context Score | Zustand Score |
|-----------|--------|---------------|---------------|
| Learning curve | 20% | 9/10 | 7/10 |
| Bundle size | 15% | 10/10 | 8/10 |
| DevTools | 15% | 6/10 | 9/10 |
| Migration effort | 25% | 10/10 | 4/10 |
| Team familiarity | 25% | 9/10 | 5/10 |

### Weighted Score
- React Context: **8.75/10**
- Zustand: **6.35/10**

### Recommendation: STAY with React Context
**Reason**: Migration cost too high (25% weight), team already proficient
**Alternative**: Consider Zustand for NEW state (not migration)

{
  "model": "haiku",
  "temperature": 0.3,
  "max_tokens": 20000,
  "cost_threshold": 0.02
}

User: "Where is authentication handled in this codebase?"

[Research Agent (Haiku)]:
Searching for authentication logic...

Found in 3 locations:
1. src/context/AuthContext.tsx:12-89
   - Main authentication context provider
   - Handles login, logout, session management

2. src/services/auth.ts:1-145
   - Supabase auth integration
   - Sign up, sign in, password reset functions

3. server/src/routes/auth.ts:1-67
   - Backend auth endpoints
   - Token validation middleware

Primary entry point: AuthContext.tsx
Backend API: server/src/routes/auth.ts

[Tokens used: 4,200 | Cost: $0.003]

User: "Find all components using useAIContext"

[Research Agent (Haiku)]:
Searching for useAIContext hook usages...

Found 8 usages:
1. src/components/features/GenerativeSidebar.tsx:15
2. src/components/features/CanvasEditor.tsx:23
3. src/components/features/ChatInterface.tsx:18
4. src/components/features/LiveActionPanel.tsx:12
5. src/components/features/SettingsModal.tsx:28
6. src/components/layout/Header.tsx:9
7. src/App.tsx:45
8. src/services/actionExecutor.ts:8

Most frequent usage: GenerativeSidebar.tsx (7 calls)

[Tokens used: 3,800 | Cost: $0.003]