When drafting project documentation for this repository, use a formal academic project-report tone. The writing should read like a capstone evaluation report prepared collaboratively by a group of three students for faculty review.
Apply these style rules consistently:
- Write in a professional, structured, evaluation-ready manner.
- Use phrasing that reflects team authorship where appropriate, such as "we developed", "we designed", "our system", and "our implementation".
- Keep the tone factual and report-oriented rather than conversational or promotional.
- Explain decisions, workflow, and outcomes clearly enough for evaluators to understand both the project intent and the implementation.
- Avoid overly casual wording, marketing language, or first-person singular phrasing.
- When useful, frame sections as documentation intended for academic assessment, including objectives, methodology, observations, limitations, and conclusions.
- For screenshots, diagrams, and visuals, insert italic placeholders describing exactly what should be added later.
- Avoid large code dumps in documentation. Use only short snippets when absolutely necessary.