ibrahim-3d/conductor-orchestrator-superpowers/knowledge-manager

const keywords = extractKeywords(spec);
// Example: ["authentication", "Supabase", "login", "signup", "OAuth"]

## Relevant Patterns Found (top 3 by relevance)
 
### Pattern: Supabase Client Singleton
**Category**: Integration
**Relevance score**: 3/5 keywords matched
**Summary**: Use singleton pattern with server/client separation
**Key Code**:

 
### Pattern: Server Actions with Error Handling
**Category**: API
**Relevance score**: 2/5 keywords matched
**Summary**: Wrap all server actions with try/catch and typed responses

## Known Errors to Watch For
 
### Error: Hydration Mismatch (err-003)
**Pattern**: "Hydration failed because the initial UI does not match"
**Context**: Auth state can differ between server and client
**Prevention**: Wrap auth-dependent UI in useEffect or client component
 
### Error: NEXT_REDIRECT in try/catch (err-004)
**Pattern**: "NEXT_REDIRECT"
**Context**: Server actions with redirect after login
**Prevention**: Re-throw NEXT_REDIRECT errors or move redirect outside try/catch

# Knowledge Brief for [Track ID]
 
## Relevant Patterns (Apply These)
 
1.**Supabase Client Singleton** — Use separate server/client clients
2.**Server Actions with Error Handling** — Typed responses with try/catch
 
## Known Errors (Avoid These)
 
1.**Hydration Mismatch** — Don't render auth-dependent UI on server
2.**NEXT_REDIRECT** — Handle redirect() specially in try/catch
 
## Previous Similar Work
 
-Track `auth-flow_20260115` implemented similar auth flow
-See `conductor/tracks/auth-flow_20260115/plan.md` for reference
 
## Recommendations
 
-Consider using the existing auth patterns from previous track
-Watch for SSR/client hydration issues with auth state

{
  "patterns_found": [
    {
      "name": "Supabase Client Singleton",
      "category": "Integration",
      "relevance": "high",
      "summary": "...",
      "code_snippet": "..."
    }
  ],
  "errors_to_watch": [
    {
      "id": "err-003",
      "pattern": "Hydration mismatch",
      "prevention": "..."
    }
  ],
  "similar_tracks": [
    {
      "track_id": "auth-flow_20260115",
      "relevance": "Implemented OAuth flow"
    }
  ],
  "recommendations": [
    "Reuse auth patterns from previous track",
    "Watch for hydration issues"
  ]
}

// In conductor-orchestrator
async function dispatchPlanner(trackId: string) {
  // 1. Run Knowledge Manager first
  const knowledgeBrief = await Task({
    subagent_type: "general-purpose",
    description: "Load knowledge for track",
    prompt: `You are the knowledge-manager agent.
      Track: ${trackId}
      Spec: ${specContent}
      Search conductor/knowledge/patterns.md and errors.json.
      Return a knowledge brief with relevant patterns and errors.`
  });
  // 2. Dispatch planner WITH knowledge brief
  await Task({
    subagent_type: "general-purpose",
    description: "Create track plan",
    prompt: `You are the loop-planner agent.
      ${knowledgeBrief.output}
      Create plan.md using the patterns above where applicable.
      Avoid the known errors listed.`
  });
}

{
  "patterns_found": [],
  "errors_to_watch": [],
  "similar_tracks": [],
  "recommendations": ["No prior patterns found. Document solutions discovered in this track."]
}