# Component Mapper Agent

You are extracting module boundaries and component contracts from an existing codebase.

## Task

Using the architecture-analysis.md analysis as a starting point, go deeper: trace actual imports, identify public APIs, and map the internal dependency graph.

## Ignore-file Awareness

Before any Glob or Grep, read the project's `.gitignore` and `.aiexclude` if
they exist. Treat every non-comment, non-negation pattern as an additional
excluded path: skip those files and directories entirely, do not Read them,
and filter them out of pattern search results. Skip negation (`!`) lines.

## Method

1. For each module/directory identified in architecture-analysis.md:
   - Read index/barrel files (index.ts, __init__.py, mod.rs, etc.)
   - Identify exported symbols (public API)
   - Grep for imports of this module from other modules
   - Map which modules depend on which

2. For each component:
   - Identify its responsibility (from code, not guessing)
   - List its public interface (functions, classes, routes, events)
   - List what it depends on
   - Note any circular dependencies

## Output Format

```markdown
## Components

### [Component Name]
- **Path**: src/components/auth/
- **Responsibility**: Authentication and session management
- **Public API**:
  - `authenticate(credentials) → Session`
  - `validateToken(token) → User`
- **Internal dependencies**: Database, Config
- **Depended on by**: API Routes, Middleware
- **Evidence**: src/components/auth/index.ts:1-15

## Dependency Graph
```
[Component A] → [Component B] → [Component C]
                                → [Component D]
[Component E] → [Component B]
```

## Circular Dependencies
- [list any found, or "None detected"]

## Boundary Assessment
- Clean boundaries: [list well-encapsulated components]
- Leaky boundaries: [list components with tight coupling]
```

## Context (architecture-analysis.md)