docs: update development guide with modern structure and emojis

Author: hallong

README.md

@@ -210,49 +210,87 @@ Useful links
 - https://evanmccall.wordpress.com/2015/03/09/how-to-develop-photoshop-tools-in-python
 
 
-Development Standards
---------------------
+## 🛠️ Development Guide
 
-This project follows these development standards to maintain code quality and consistency:
+Welcome to the development guide for the Photoshop Python API project! This section outlines our development practices and standards to ensure code quality and consistency.
 
-### Code Style
+### 📋 Quick Start for Contributors
 
-- **Python**: We follow the [Google Python Style Guide](https://google.github.io/styleguide/pyguide.html) with some modifications:
-  - Line length: 120 characters (configured in `.flake8` and `pyproject.toml`)
-  - Docstrings: Google style (configured in `.flake8`)
-  - Quotes: Double quotes as default (configured in `.flake8`)
+```bash
+# Clone the repository
+git clone https://github.com/loonghao/photoshop-python-api.git
+cd photoshop-python-api
 
-- **Formatting Tools**:
-  - [Black](https://black.readthedocs.io/): For code formatting
-  - [isort](https://pycqa.github.io/isort/): For import sorting
-  - [flake8](https://flake8.pycqa.org/): For style enforcement
+# Install dependencies with Poetry
+poetry install
 
-### Git Workflow
+# Install pre-commit hooks
+pre-commit install
 
-- **Commit Messages**: We use [Conventional Commits](https://www.conventionalcommits.org/) format
-  - Format: `<type>(<scope>): <description>`
-  - Types: `feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`, `build`, `ci`, `chore`, `revert`
-  - Example: `feat(api): add new layer manipulation method`
+# Run tests
+pytest
+```
+
+### 🎨 Code Style & Quality
+
+We maintain high code quality standards through automated tools and consistent style guidelines:
+
+- **Style Guide**: We follow the [Google Python Style Guide](https://google.github.io/styleguide/pyguide.html) with project-specific adjustments:
+  - Line length: 120 characters max
+  - Docstrings: Google style format
+  - Quotes: Double quotes preferred
+
+- **Quality Tools**:
+  - [Black](https://black.readthedocs.io/) - Code formatting
+  - [isort](https://pycqa.github.io/isort/) - Import organization
+  - [flake8](https://flake8.pycqa.org/) - Style enforcement
+  - [pre-commit](https://pre-commit.com/) - Automated checks before commits
+
+### 🔄 Git Workflow
+
+We use a structured workflow to maintain a clean and organized repository:
+
+- **Commit Messages**: Follow [Conventional Commits](https://www.conventionalcommits.org/) format
+
+  ```text
+  <type>(<scope>): <description>
+
+  [optional body]
+
+  [optional footer(s)]
+  ```
+
+  Common types: `feat`, `fix`, `docs`, `style`, `refactor`, `test`, `chore`
 
 - **Branching Strategy**:
+  - Main branch: `main` - Always stable and deployable
   - Feature branches: `feature/<feature-name>`
   - Bug fixes: `fix/<bug-description>`
   - Documentation: `docs/<doc-description>`
 
-### Development Environment
+### 🧪 Testing
+
+We value thorough testing to ensure reliability:
+
+- **Framework**: We use `pytest` for all tests
+- **Coverage**: Aim for high test coverage on new features
+- **Run Tests**: `pytest` or `poetry run pytest`
+
+### 📦 Development Environment
 
-- **Dependencies**: Managed with [Poetry](https://python-poetry.org/)
-- **Pre-commit Hooks**: Configured in `.pre-commit-config.yaml`
-- **Testing**: Use `pytest` for running tests
+- **Python Versions**: We support Python 3.8+ (see `pyproject.toml` for specifics)
+- **Dependency Management**: [Poetry](https://python-poetry.org/) for consistent environments
+- **Virtual Environment**: Poetry automatically creates and manages virtual environments
 
-### Contributing
+### 🤝 Contributing Process
 
-1. Fork the repository
-2. Create your feature branch
-3. Install development dependencies: `poetry install`
-4. Install pre-commit hooks: `pre-commit install`
-5. Make your changes and ensure tests pass
-6. Commit your changes using conventional commit format
-7. Push to your branch
-8. Create a Pull Request
+1. **Fork & Clone**: Fork the repository and clone your fork
+2. **Branch**: Create a feature branch with a descriptive name
+3. **Develop**: Make your changes following our code style guidelines
+4. **Test**: Ensure all tests pass and add new tests for new features
+5. **Commit**: Use conventional commit format for clear history
+6. **Push & PR**: Push your branch and create a Pull Request
+7. **Review**: Address any feedback from code reviews
+8. **Merge**: Once approved, your PR will be merged
 
+Thank you for contributing to the Photoshop Python API project! 🎉