chore: add GitHub Actions, issue templates, and contributing guidelines

Author: jkcoderKrones

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,38 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: "[BUG] "
+labels: bug
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Environment (please complete the following information):**
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.
+
+**Concurrency Testing**
+If the bug involves multiple users:
+- [ ] Bug occurs with single user
+- [ ] Bug occurs with multiple users (race condition)
+- [ ] Bug occurs during rapid clicking/interactions

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,26 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: "[FEATURE] "
+labels: enhancement
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.
+
+**Impact on Concurrency**
+- [ ] This feature affects multi-user interactions
+- [ ] This feature requires atomic operations
+- [ ] This feature might introduce race conditions
+- [ ] This feature is single-user only

.github/workflows/ci.yml

@@ -0,0 +1,65 @@
+name: CI/CD Pipeline
+
+on:
+  push:
+    branches: [ main, develop ]
+  pull_request:
+    branches: [ main ]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    
+    strategy:
+      matrix:
+        node-version: [18.x, 20.x]
+    
+    steps:
+    - name: Checkout code
+      uses: actions/checkout@v4
+      
+    - name: Setup Node.js ${{ matrix.node-version }}
+      uses: actions/setup-node@v4
+      with:
+        node-version: ${{ matrix.node-version }}
+        cache: 'npm'
+        
+    - name: Install dependencies
+      run: npm ci
+      
+    - name: Run linter
+      run: npm run lint
+      
+    - name: Build project
+      run: npm run build
+      
+    - name: Run type check
+      run: npx tsc --noEmit
+      
+  build:
+    needs: test
+    runs-on: ubuntu-latest
+    if: github.ref == 'refs/heads/main'
+    
+    steps:
+    - name: Checkout code
+      uses: actions/checkout@v4
+      
+    - name: Setup Node.js
+      uses: actions/setup-node@v4
+      with:
+        node-version: '20.x'
+        cache: 'npm'
+        
+    - name: Install dependencies
+      run: npm ci
+      
+    - name: Build for production
+      run: npm run build
+      
+    - name: Upload build artifacts
+      uses: actions/upload-artifact@v4
+      with:
+        name: production-build
+        path: dist/
+        retention-days: 30

CONTRIBUTING.md

@@ -0,0 +1,105 @@
+# Contributing to Digital Twin Counter
+
+Thank you for your interest in contributing to Digital Twin Counter! This document provides guidelines and instructions for contributing to this project.
+
+## Code of Conduct
+
+Please be respectful and professional in all interactions. We welcome contributions from developers of all experience levels.
+
+## Development Setup
+
+1. **Fork and Clone**
+   ```bash
+   git clone https://github.com/YOUR-USERNAME/digital-twin.git
+   cd digital-twin
+   ```
+
+2. **Install Dependencies**
+   ```bash
+   npm install
+   ```
+
+3. **Set up Convex**
+   ```bash
+   npx convex dev
+   ```
+   Follow the prompts to set up your Convex deployment.
+
+4. **Start Development Server**
+   ```bash
+   npm run dev
+   ```
+
+## Development Guidelines
+
+### Code Style
+- Use TypeScript for all new code
+- Follow the existing code patterns and architecture
+- Use meaningful variable and function names
+- Write clean, self-documenting code
+
+### Testing Concurrency
+When working on features that affect multiple users:
+1. Test with multiple browser tabs/windows
+2. Test rapid clicking/interactions
+3. Verify atomic operations work correctly
+4. Check for race conditions
+
+### Architecture Principles
+- **SOLID Principles**: Follow Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion
+- **DRY**: Don't Repeat Yourself
+- **Component Separation**: Keep components focused and reusable
+- **Type Safety**: Use TypeScript interfaces and types throughout
+
+## Submitting Changes
+
+1. **Create a Branch**
+   ```bash
+   git checkout -b feature/your-feature-name
+   ```
+
+2. **Make Your Changes**
+   - Write clean, well-documented code
+   - Test your changes thoroughly
+   - Ensure the build passes: `npm run build`
+
+3. **Commit Your Changes**
+   ```bash
+   git commit -m "feat: add your feature description"
+   ```
+   Use conventional commit messages:
+   - `feat:` for new features
+   - `fix:` for bug fixes
+   - `docs:` for documentation changes
+   - `refactor:` for code refactoring
+   - `test:` for adding tests
+
+4. **Push and Create Pull Request**
+   ```bash
+   git push origin feature/your-feature-name
+   ```
+   Then create a pull request through GitHub.
+
+## Pull Request Guidelines
+
+- Provide a clear description of the changes
+- Include screenshots for UI changes
+- Reference any related issues
+- Ensure CI/CD pipeline passes
+- Test concurrency scenarios if applicable
+
+## Areas for Contribution
+
+- **UI/UX Improvements**: Better design, animations, accessibility
+- **Performance Optimizations**: Faster load times, reduced bundle size
+- **New Features**: Additional counter operations, user management
+- **Testing**: Unit tests, integration tests, E2E tests
+- **Documentation**: Code comments, tutorials, examples
+- **Accessibility**: Screen reader support, keyboard navigation
+- **Internationalization**: Multi-language support
+
+## Questions?
+
+Feel free to open an issue for questions or discussions about potential contributions.
+
+Thank you for contributing to Digital Twin Counter!