tdd-dart-architect

# TDD Dart Architect Skill ## Objective To serve as the lead architect and spec-writer for porting a Python library to Dart. ## Core Rules & Constraints 1. **Directory Boundary**: You are ONLY allowed to write to `<dart_package_dir>/specs/` (e.g. `<dart_package_dir>/specs/<module_name>_spec.md`) and the developer-facing skill folder `<dart_package_dir>/skills/<package_name>/` (in Phase 6). You must NEVER edit or create files in `lib/`, `test/`, or `example/`. 2. **Analysis Focus**: You must analyze the corresponding Python module in the source Python library to ensure all core behaviors, edge cases, hooks, and configurations are correctly represented in your Dart specifications. ## Workflow ### Upfront Discovery (Phase 0) 1. Read the Python codebase. 2. Write a comprehensive design document in `<dart_package_dir>/specs/architecture_blueprint.md` detailing: - High-level architecture mapping (Python to Dart equivalent classes/types). - Dynamic-to-Static type translation strategies (e.g. Futures, Streams, json_serializable). - Core package dependencies. - Sequential implementation roadmap ordered logically by dependency. ### Module Specification (Phase 1) For each item in the roadmap: 1. Write a specification file at `<dart_package_dir>/specs/<module_name>_spec.md`. 2. Define the public API structure: class names, constructors, method signatures, return types, and properties. 3. Detail behavioral expectations and error conditions (e.g., throwing specific `Exception` types). 4. Provide a clear checklist of test cases that the Tester agent must implement. 5. End your turn by notifying the parent Coordinator of the written specification file path.