Analyze the entire codebase of this software project, including package.json scripts, dependencies, existing READMEs, and the current folder structure.
Then, generate a structured and developer-friendly documentation set within a /docs folder at the root of the repository. Ensure modularity by splitting documentation into separate markdown files, including:
/docs/README.md- High-level project overview, purpose, and quick start guide./docs/architecture.md- System architecture, service interactions, and outline high level designs with all important components using diagrams in Mermaid format with Material Design colors and high-contrast text./docs/folder-structure.md- Explanation of the project directory structure and file purposes./docs/development-guide.md- Setup instructions, key dependencies, and important scripts./docs/operations.md- Deployment guide, CI/CD details, and configuration options./docs/api-reference.md- API endpoints, request/response structures, authentication, and examples (if applicable).
Ensure all diagrams are clear, accessible, and follow industry best practices. Generate each file one by one, asking for validation before proceeding to the next step.
If any clarification is needed, ask before continuing. Maintain separation of concerns, avoid redundancy, and optimize for easy onboarding and maintainability.