chore: update contributing

Author: hyochan

CHANGELOG.md

@@ -28,6 +28,7 @@
 ### Migration Guide
 
 If you're upgrading from 6.0.x and were using any deprecated methods:
+
 - Replace `initialize()` with `initConnection()`
 - Replace `acknowledgePurchaseAndroid()` with `finishTransaction()`
 - Use `requestPurchase()` with proper RequestPurchase objects instead of platform-specific methods

CLAUDE.md

@@ -0,0 +1,45 @@
+# Implementation Guidelines
+
+## Flutter-Specific Guidelines
+
+### Pre-Commit Checks
+
+Before committing any changes:
+
+1. Run `dart format .` to ensure consistent code formatting
+2. Run `flutter test` to verify all tests pass
+3. Only commit if both checks succeed
+
+### Platform-Specific Naming Conventions
+
+- **iOS-related code**: Use `IOS` suffix (e.g., `PurchaseIOS`, `SubscriptionOfferIOS`)
+  - When iOS is not the final suffix, use `Ios` (e.g., `IosManager`, `IosHelper`)
+- **Android-related code**: Use `Android` suffix (e.g., `PurchaseAndroid`, `SubscriptionOfferAndroid`)
+- **IAP-related code**: When IAP is not the final suffix, use `Iap` (e.g., `IapPurchase`, not `IAPPurchase`)
+- This applies to both functions and types
+
+### API Method Naming
+
+- Functions that depend on event results should use `request` prefix (e.g., `requestPurchase`, `requestSubscription`)
+- Follow OpenIAP terminology: <https://www.openiap.dev/docs/apis#terminology>
+- Do not use generic prefixes like `get`, `find` - refer to the official terminology
+
+## IAP-Specific Guidelines
+
+### OpenIAP Specification
+
+All implementations must follow the OpenIAP specification:
+
+- **APIs**: <https://www.openiap.dev/docs/apis>
+- **Types**: <https://www.openiap.dev/docs/types>
+- **Events**: <https://www.openiap.dev/docs/events>
+- **Errors**: <https://www.openiap.dev/docs/errors>
+
+### Feature Development Process
+
+For new feature proposals:
+
+1. Before implementing, discuss at: <https://github.com/hyochan/openiap.dev/discussions>
+2. Get community feedback and consensus
+3. Ensure alignment with OpenIAP standards
+4. Implement following the agreed specification

CONTRIBUTING.md

@@ -0,0 +1,134 @@
+# Contributing to Flutter InApp Purchase
+
+Thank you for your interest in contributing! This guide will help you get started with development and submitting your contributions.
+
+## Getting Started
+
+### 1. Clone the Repository
+
+```bash
+git clone https://github.com/hyochan/flutter_inapp_purchase.git
+cd flutter_inapp_purchase
+```
+
+### 2. Install Dependencies
+
+```bash
+flutter pub get
+```
+
+### 3. Run the Example App
+
+Navigate to the example directory and run the app:
+
+```bash
+cd example
+flutter pub get
+
+# For iOS
+flutter run --dart-define=IOS_PRODUCTS="your_product_ids"
+
+# For Android
+flutter run --dart-define=ANDROID_PRODUCTS="your_product_ids"
+```
+
+**Note:** You'll need to configure your app with valid product IDs from your App Store Connect or Google Play Console.
+
+## Making Changes
+
+### 1. Fork the Repository
+
+1. Go to <https://github.com/hyochan/flutter_inapp_purchase>
+2. Click the "Fork" button in the top-right corner
+3. Clone your fork locally:
+
+   ```sh
+   git clone https://github.com/YOUR_USERNAME/flutter_inapp_purchase.git
+   cd flutter_inapp_purchase
+   ```
+
+### 2. Create a Feature Branch
+
+```bash
+git checkout -b feature/your-feature-name
+```
+
+### 3. Make Your Changes
+
+- Write your code following the project conventions
+- Add tests for new functionality
+- Update documentation as needed
+
+### 4. Test Your Changes
+
+```bash
+# Format your code
+dart format .
+
+# Run tests
+flutter test
+
+# Run the example app to verify functionality
+cd example
+flutter run
+```
+
+### 5. Commit Your Changes
+
+```bash
+git add .
+git commit -m "feat: add your feature description"
+```
+
+Follow conventional commit messages:
+
+- `feat:` for new features
+- `fix:` for bug fixes
+- `docs:` for documentation changes
+- `refactor:` for code refactoring
+- `test:` for test additions/changes
+- `chore:` for maintenance tasks
+
+### 6. Push to Your Fork
+
+```bash
+git push origin feature/your-feature-name
+```
+
+### 7. Create a Pull Request
+
+1. Go to your fork on GitHub
+2. Click "Pull request" button
+3. Select your branch and target `main` branch of the original repository
+4. Fill in the PR template with:
+   - Description of changes
+   - Related issue number (if applicable)
+   - Testing performed
+5. Submit the pull request
+
+## Development Guidelines
+
+### Coding Standards
+
+Please refer to [CLAUDE.md](./CLAUDE.md) for:
+
+- Naming conventions
+- Platform-specific guidelines
+- API method naming
+- OpenIAP specification compliance
+
+### Before Submitting
+
+- [ ] Code is formatted with `dart format .`
+- [ ] All tests pass with `flutter test`
+- [ ] Example app runs without errors
+- [ ] Documentation is updated if needed
+- [ ] Commit messages follow conventional format
+
+## Questions or Issues?
+
+- For new feature proposals, start a discussion at: <https://github.com/hyochan/openiap.dev/discussions>
+- For bugs, open an issue with a clear description and reproduction steps
+- For questions, feel free to open a discussion
+
+Thank you for contributing!