Codebase Exploration

Performs thorough codebase exploration to build deep understanding before coding work begins.

Exploration Approach

Use the Task tool with subagent_type: Explore to investigate the codebase. Focus on understanding:

1. •Project purpose and structure - README, documentation, directory layout
2. •Architecture - Main components, how they interact, communication patterns
3. •Core code - Key classes, data models, utilities
4. •Configuration - How the project is configured and customized
5. •Dependencies - External libraries and integrations
6. •Patterns and conventions - Coding style, naming conventions, design patterns

Adapt exploration depth based on project size and complexity. For small projects, a quick overview suffices. For large projects, explore systematically.

Guiding Questions

Answer these questions during exploration:

Architecture

• •What is the main entry point or controller?
• •How do components communicate (IPC, APIs, events)?
• •What external systems does this integrate with?

Patterns

• •What naming conventions are used?
• •What design patterns appear (factories, dataclasses, protocols)?
• •How is configuration managed?

Structure

• •Where is the core business logic?
• •Where are tests located?
• •What build/tooling configuration exists?

Output Format

Provide a structured summary including:

• •Project purpose (1-2 sentences)
• •Key components table
• •Important files list with paths
• •Notable patterns or conventions
• •Any areas of complexity or concern

Example Output

## Project Purpose

Provides foundational utilities for message handling, error management, and common operations across all Sun Lab
Python projects.

## Key Components

| Component          | Location                                  | Purpose                                         |
|--------------------|-------------------------------------------|-------------------------------------------------|
| Console            | src/ataraxis_base_utilities/console/      | Unified message/error handling framework        |
| Standalone Methods | src/ataraxis_base_utilities/standalone/   | Common data manipulation utilities              |
| Public API         | src/ataraxis_base_utilities/__init__.py   | Library entry point and public exports          |

## Important Files

- `src/ataraxis_base_utilities/console/console_class.py` - Main Console implementation
- `src/ataraxis_base_utilities/standalone_methods/standalone_methods.py` - Utility functions
- `pyproject.toml` - Project configuration and dependencies

## Notable Patterns

- Global singleton Console instance for consistent configuration
- Loguru-based logging with three-tier file output (debug, message, error)
- MyPy strict mode with full type annotations
- Google-style docstrings

## Areas of Concern

- Intentional conflict with other loguru-using libraries
- Global state via console instance requires initialization from application entry point

Usage

Invoke at session start to ensure full context before making changes. Prevents blind modifications and ensures understanding of existing patterns.