init repo: upload source

Author: mufeedvh

.gitattributes

@@ -0,0 +1,2 @@
+* linguist-vendored
+*.rs linguist-vendored=false

.gitignore

@@ -0,0 +1,17 @@
+# Generated by Cargo
+# will have compiled files and executables
+debug/
+target/
+
+# These are backup files generated by rustfmt
+**/*.rs.bk
+
+# MSVC Windows builds of rustc generate these, which store debugging information
+*.pdb
+
+# RustRover
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/

CONTRIBUTING.md

@@ -0,0 +1,37 @@
+# Welcome Contributors
+
+We welcome contributions to enhance DeepClaude's capabilities and improve its performance. To report bugs, create a [GitHub issue](https://github.com/getasterisk/deepclaude/issues).
+
+> Before contributing, read through the existing issues and pull requests to see if someone else is already working on something similar. That way you can avoid duplicating efforts.
+
+To contribute, please follow these steps:
+
+1. Fork the DeepClaude repository on GitHub.
+2. Create a new branch for your feature or bug fix.
+3. Make your changes and ensure that the code passes all tests.
+4. Submit a pull request describing your changes and their benefits.
+
+### Pull Request Guidelines
+When submitting a pull request, please follow these guidelines:
+
+1. **Title**: please include following prefixes: 
+   - `Feature:` for new features
+   - `Fix:` for bug fixes
+   - `Docs:` for documentation changes
+   - `Refactor:` for code refactoring
+   - `Improve:` for performance improvements
+   - `Other:` for other changes
+
+   for example: 
+      - `Feature: added new feature to the code`
+      - `Fix: fixed the bug in the code`
+
+2. **Description**: Provide a clear and detailed description of your changes in the pull request. Explain the problem you are solving, the approach you took, and any potential side effects or limitations of your changes.
+3. **Documentation**: Update the relevant documentation to reflect your changes. This includes the README file, code comments, and any other relevant documentation.
+4. **Dependencies**: If your changes require new dependencies, ensure that they are properly documented and added to the `Cargo.toml` or `package.json` files.
+5. if the pull request does not meet the above guidelines, it may be closed without merging.
+
+
+**Note**: Please ensure that you have the latest version of the code before creating a pull request. If you have an existing fork, just sync your fork with the latest version of the DeepClaude repository.
+
+Please adhere to the coding conventions, maintain clear documentation, and provide thorough testing for your contributions.