# io8 Code Master Agent - Customized for This Project

## Project-Specific Instructions



## Project Breakdown: Password Generator (2025-10-10 05:40:00)

### 1. Project Overview
Create a secure, customizable, and user-friendly web-based password generator. The project will leverage a distinct frontend and backend as per the established directory structure, ensuring a robust and maintainable solution. The cloned base project will serve as the foundation for the frontend application.

### 2. Core Functional Components
*   **Password Generation Logic (Backend):** Implement a highly secure and truly random password generation algorithm. This will handle parameters like length, character sets (uppercase, lowercase, numbers, symbols), and exclusion rules, residing in the `./backend/` directory.
*   **User Interface (Frontend):** Develop an intuitive web interface allowing users to configure password parameters, trigger generation, view the generated password, and copy it to the clipboard. This will build upon the `cloned base project/` and reside primarily in the `./frontend/` directory.
*   **API Integration:** Establish a secure and efficient communication channel between the frontend application (in `frontend/`) and the backend generation service (in `backend/`) for requesting and receiving generated passwords.

### 3. Non-Functional Requirements (Key Focus Areas)
*   **Security:** Paramount importance. Ensure true randomness, prevent password storage, and protect against common web vulnerabilities. Randomness source will be a critical design consideration.
*   **Usability:** Simple and clear user interface, immediate feedback, easy copy functionality for the generated password.
*   **Performance:** Fast password generation and responsive UI, even with complex parameter selections.
*   **Maintainability:** Clear code separation (frontend/backend), adherence to coding standards, and comprehensive documentation.

### 4. Milestones & Deliverables
*   **M1: Requirements & Architecture Defined:** Completion of detailed functional and non-functional requirements, high-level system architecture (including API contract), and technology stack selection. Output documents like `requirements_document.md`, `analysis_document.md`, `architecture_document.md`, and `tech_stack_document.md` will be finalized.
*   **M2: Core Generation Logic Implemented:** A fully functional and tested backend API for password generation, residing within `./backend/`. This includes unit tests for randomness and parameter adherence.
*   **M3: User Interface Developed:** A complete frontend application (within `./frontend/` and built on `cloned base project/`) providing all configuration options, display, and copy functionality.
*   **M4: Integrated & End-to-End Tested System:** The frontend and backend are successfully integrated, and comprehensive end-to-end tests confirm full functionality and security. Output will include `tasks_list.md` updates with test results.
*   **M5: Containerized Deployment Ready:** Finalized `Dockerfile.backend`, `Dockerfile.frontend`, `docker-compose.yml`, `nginx.conf`, and `deployment_config.yml` are created and tested for local and potential cloud deployments.

### 5. Constraints
*   **Security First:** All design and implementation decisions must prioritize security and cryptographic best practices for random password generation.
*   **Append-Only to Base Project Docs:** All documentation and agent outputs related to the specific 'Password Generator' project must be appended to existing documents within `cloned base project/.sureai/`, respecting the existing content and structure.
*   **Modular Design:** Strict separation of concerns between frontend and backend components as outlined in the `.directory_structure.md` to ensure independent development and deployment.
*   **No Password Storage:** The generator will explicitly *not* store generated passwords or user preferences server-side for security reasons.

### 6. Out of Scope (Initial Phase)
*   User authentication or account management.
*   Advanced password history or strength analytics beyond a basic indicator.
*   Multi-language support for the UI.
*   Mobile native applications (focus is on web-based solution for now).



## Implementation Plan: Password Generator (2025-10-10 05:40:00)

### 1. High-Level Project Phases
*   **Phase 1: Discovery & Design (io8Analyst, io8Architect):** This phase focuses on deep diving into requirements for password generation (length, character sets, exclusions), designing the secure generation algorithm, defining the frontend UI/UX, and establishing the API contract between frontend and backend. It will also finalize the specific tech stack within the `backend/` and `frontend/` directories.
    *   *Duration:* ~1 Week
*   **Phase 2: Core Development & Integration (io8Developer - Backend & Frontend):** This phase involves parallel development of the backend password generation service and the frontend user interface. Key activities include implementing the cryptographic random number generator, building the API endpoint, developing UI components, and integrating the frontend with the backend API.
    *   *Duration:* ~2-3 Weeks
*   **Phase 3: Testing, Hardening & DevOps (io8Developer, io8DevOps):** This phase focuses on thorough unit and integration testing of both backend and frontend, security audits, and setting up the deployment infrastructure. It includes writing `Dockerfile.backend`, `Dockerfile.frontend`, `docker-compose.yml`, `nginx.conf` (if needed for reverse proxy/static serve), and `deployment_config.yml`.
    *   *Duration:* ~1 Week

### 2. Agent Engagement Timeline
*   **io8codermaster:** Will maintain continuous oversight, provide guidance, and orchestrate agent transitions throughout all project phases, ensuring adherence to the io8 workflow.
*   **io8Analyst:** Primarily active in **Phase 1** to define `requirements_document.md` and `analysis_document.md`, focusing on password complexity, UI needs, and security constraints.
*   **io8Architect:** Active in **Phase 1** to design the system architecture, API specifications, and select specific technologies for `backend/` and `frontend/`, contributing to `architecture_document.md` and `tech_stack_document.md`.
*   **io8PM:** Will initiate in **Phase 1** to create the overall `project_plan.md` and `prd_document.md`, setting project scope, milestones, and high-level timelines.
*   **io8SM:** Becomes active during **Phase 2** to break down tasks into sprints, manage the backlog, and track progress, updating `tasks_list.md` and `sprint_plan.md`.
*   **io8Developer (Backend & Frontend):** The primary implementers during **Phase 2** and **Phase 3**, responsible for coding, unit testing, and integration.
*   **io8DevOps:** Engaged in **Phase 3** for containerization, environment configuration, and preparing deployment scripts, including `Dockerfile`s, `docker-compose.yml`, `nginx.conf`, and `deployment_config.yml`.

### 3. Key Dependencies
*   A precise `requirements_document.md` from the io8Analyst is critical for accurate design and implementation.
*   A well-defined `architecture_document.md` and `tech_stack_document.md` from the io8Architect are prerequisite for development commencement.
*   The stable password generation logic from the `backend/` is a hard dependency for full `frontend/` integration and end-to-end testing.

### 4. Success Criteria
*   A deployed, containerized web application that securely and accurately generates customizable passwords.
*   The user interface is intuitive, responsive, and fully functional across common web browsers.
*   All agent-specific documentation within `cloned base project/.sureai/` is current, complete, and adheres to naming conventions.
*   The project successfully demonstrates the io8 workflow principles from conception to deployment.

### 5. Resource Allocation Considerations
*   **Development:** Minimum of one full-stack developer or dedicated backend and frontend developers with expertise in the chosen tech stack (e.g., Python/Node.js for backend, Angular/React for frontend, building upon the `cloned base project`).
*   **DevOps:** Expertise in Docker, container orchestration, Nginx configuration, and cloud deployment strategies is essential.
*   **Quality Assurance:** Integrated testing approach, with developers writing unit and integration tests, and a focus on security testing.
*   **Project Management:** Continuous oversight and coordination from the io8PM and io8SM to keep the project on track and manage scope.

## Base Agent Prompt Reference

This agent is based on the standard io8codermaster agent with project-specific customizations above.
Refer to the base io8codermaster agent prompt for general principles and workflow instructions.
