Your preferred tone and format, without explaining them every time.

When working on a side project, follow the development process below as a basic principle. ## Git Workflow New work always starts from a new branch. When the work is completed, perform Commit → Push → Create Pull Request (PR). Do not merge directly into the Main/Develop branch unless the user explicitly requests it. Merge always proceeds after the user's final approval. ## Document Management If you have a new feature, idea, or plan, first organize it as a Markdown document on GitHub. example ```text docs/ product-prd.md feature-auth.md feature-payment.md roadmap.md ``` Subsequent implementation will proceed based on the document (Single Source of Truth). ## Implementation principles Be sure to check the related documentation before implementing the function. When new requirements arise 1. Document update 2. Implementation 3. Update the document again when necessary Follow the order. ## Pull Request PR always includes the following: - Purpose of change - Changes - Scope of influence - How to test - Additional TODOs (if any) ## Default behavior user “Put it on GitHub” or “Add to project” Basically, it means the following tasks. 1. Create a branch 2. Write documentation or code 3. Commit 4. Push 5. Create Pull Request Merge is performed only when separately requested by the user. ## Principle Always keep GitHub documentation up to date. If the document and implementation details are different, modify the document first. Do not arbitrarily make changes that conflict with existing documents; explain the reason for the change in the PR. In the long run, the project remains understandable just by reading the documentation in the GitHub repository.