docs: add readme.md

* add flutter-architecture.md

* add guildlines/conventional-commit.md

* add database-schema.md

* add readme.md

Author: tqha1011

README.md

@@ -1 +1,25 @@
-# TaskManagement
+# Task Management App - Life Organizer
+
+## 1. Introduction
+This repository contains the source code for the **Task Management App (Life Organizer)**, developed as a project for the **SE346** course at the University of Information Technology - VNUHCM (UIT).
+
+Going beyond a traditional to-do list, this application is designed to be a comprehensive personal assistant. It helps users easily organize various life contexts, such as tracking utility bills, managing grocery shopping lists, building daily habits, and handling household chores efficiently.
+
+## 2. Authors
+This project is built and maintained by a dedicated team of 4 members:
+* [Trần Quang Hạ](https://github.com/tqha1011) 
+* [Nguyễn Lê Hoàng Hảo](https://github.com/hoanghaoz) 
+* [Nguyễn Anh Kiệt](https://github.com/anhkietbienhoa-crypto) 
+* [Nguyễn Trí Kiệt](https://github.com/Ender-Via)
+
+## 3. Tech Stack
+The application is built with a focus on performance, security, and clean code principles, strictly following the **Feature-Based MVVM** architecture:
+* **Frontend:** Flutter
+* **Backend & Database:** Supabase (PostgreSQL, Auth, Row Level Security)
+* **Code Quality & CI/CD:** GitHub Actions, SonarCloud
+
+## 4. Documentation
+For a deeper dive into our system design and development workflows, please explore the attached documentation:
+* [Flutter App Architecture](documentation/architecture/flutter-architecture.md)
+* [Database Schema & ERD](documentation/architecture/database-schema.md)
+* [Git & Conventional Commits Guidelines](documentation/guidelines/conventional-commit.md)

documentation/guildelines/conventional-commit.md

@@ -0,0 +1,24 @@
+## 📌 Git Commit Convention
+
+To maintain a clean, readable, and trackable commit history, all team members **MUST** adhere to the following commit guidelines.
+
+### 1. Standard Syntax
+`<type>(<scope>): <short_description>`
+
+### 2. Allowed Types
+
+| Icon | Type | Description | Example |
+| :---: | :--- | :--- | :--- |
+| ✨ | **feat** | Adds a new feature to the application. | `feat(auth): add JWT login API` |
+| 🐛 | **fix** | Patches a bug or resolves an issue. | `fix(cart): resolve incorrect total price calculation` |
+| ♻️ | **refactor**| Restructures code without changing existing logic or adding features. | `refactor(product): clean up IProductService interface` |
+| 📝 | **docs** | Adds or updates documentation (README, diagrams, etc.). | `docs(ci): update SonarCloud workflow` |
+| 🔧 | **chore** | Maintenance tasks, configurations, or dependency updates. | `chore(deps): bump Newtonsoft.Json to 10.0.4` |
+| 🚀 | **perf** | Code changes that improve performance. | `perf(db): add index to Product table for faster queries` |
+
+### 3. Golden Rules
+- The `type` and `scope` MUST strictly be in **lowercase**.
+- The description must be clear, concise, and straight to the point.
+- **NEVER** push code with meaningless commit messages such as: `update`, `fix bug`, `done part A`, `asdfgh`.
+
+Reference: [Conventional Commit](https://www.conventionalcommits.org/en/v1.0.0/)