docs: add development standards section to README

Author: hallong

README.md

@@ -41,7 +41,7 @@
 
 <!-- ALL-CONTRIBUTORS-BADGE:START - Do not remove or modify this section -->
 [![All Contributors](https://img.shields.io/badge/all_contributors-18-orange.svg?style=flat-square)](#contributors-)
-<!-- ALL-CONTRIBUTORS-BADGE:END --> 
+<!-- ALL-CONTRIBUTORS-BADGE:END -->
 </p>
 
 <p align="center">Python API for Photoshop.</p>
@@ -72,7 +72,7 @@ pip install photoshop_python_api
 ```
 
 
-Since it uses COM (Component Object Model) connect Photoshop, it can be used 
+Since it uses COM (Component Object Model) connect Photoshop, it can be used
 in any DCC software with a python interpreter.
 
 
@@ -183,8 +183,8 @@ Contributions of any kind are welcome!
 how to get Photoshop program ID
 -------------------------------
 ```PS>
-Get-ChildItem "HKLM:\SOFTWARE\Classes" | 
-  ?{ ($_.PSChildName -match "^[a-z]+\.[a-z]+(\.\d+)?$") -and ($_.GetSubKeyNames() -contains "CLSID") } | 
+Get-ChildItem "HKLM:\SOFTWARE\Classes" |
+  ?{ ($_.PSChildName -match "^[a-z]+\.[a-z]+(\.\d+)?$") -and ($_.GetSubKeyNames() -contains "CLSID") } |
   ?{ $_.PSChildName -match "Photoshop.Application" } | ft PSChildName
 ```
 ![get_program_id](https://i.imgur.com/UwPN7qq.png)
@@ -208,3 +208,51 @@ Useful links
 - http://www.tonton-pixel.com/scripts/utility-scripts/get-equivalent-id-code/index.html
 - https://github.com/Adobe-CEP/Samples/tree/master/PhotoshopEvents
 - https://evanmccall.wordpress.com/2015/03/09/how-to-develop-photoshop-tools-in-python
+
+
+Development Standards
+--------------------
+
+This project follows these development standards to maintain code quality and consistency:
+
+### Code Style
+
+- **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`)
+
+- **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
+
+### Git Workflow
+
+- **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`
+
+- **Branching Strategy**:
+  - Feature branches: `feature/<feature-name>`
+  - Bug fixes: `fix/<bug-description>`
+  - Documentation: `docs/<doc-description>`
+
+### 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
+
+### Contributing
+
+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
+