claude-code-templates 1.21.12 → 1.21.14

package/cli-tool/components/commands/game-development/unity-project-setup.md

@@ -0,0 +1,190 @@
+---
+allowed-tools: Read, Write, Edit, Bash
+argument-hint: [project-name] | --2d | --3d | --mobile | --vr | --console
+description: Use PROACTIVELY to set up professional Unity game development projects with industry-standard structure, essential packages, and platform-optimized configurations
+model: sonnet
+---
+
+# Unity Project Setup & Development Environment
+
+Initialize professional Unity game development project: $ARGUMENTS
+
+## Current Unity Environment
+
+- Unity version: !`unity-editor --version 2>/dev/null || echo "Unity Editor not found"`
+- Current directory: !`pwd`
+- Available templates: !`find . -name "*.unitypackage" 2>/dev/null | wc -l` Unity packages
+- Git status: !`git status --porcelain 2>/dev/null | wc -l` uncommitted changes
+- System info: !`system_profiler SPSoftwareDataType | grep "System Version" 2>/dev/null || uname -a`
+
+## Task
+
+Set up a complete Unity project with professional development environment and platform-specific optimizations.
+
+## What it creates:
+
+### Project Structure
+```
+Assets/
+├── _Project/
+│   ├── Scripts/
+│   │   ├── Managers/
+│   │   ├── Player/
+│   │   ├── UI/
+│   │   ├── Gameplay/
+│   │   └── Utilities/
+│   ├── Art/
+│   │   ├── Textures/
+│   │   ├── Materials/
+│   │   ├── Models/
+│   │   └── Animations/
+│   ├── Audio/
+│   │   ├── Music/
+│   │   ├── SFX/
+│   │   └── Voice/
+│   ├── Prefabs/
+│   │   ├── Characters/
+│   │   ├── Environment/
+│   │   ├── UI/
+│   │   └── Effects/
+│   ├── Scenes/
+│   │   ├── Development/
+│   │   ├── Production/
+│   │   └── Testing/
+│   ├── Settings/
+│   │   ├── Input/
+│   │   ├── Rendering/
+│   │   └── Audio/
+│   └── Resources/
+├── Plugins/
+├── StreamingAssets/
+└── Editor/
+    ├── Scripts/
+    └── Resources/
+```
+
+### Essential Packages
+- Universal Render Pipeline (URP)
+- Input System
+- Cinemachine
+- ProBuilder
+- Timeline
+- Addressables
+- Unity Analytics
+- Version Control (if available)
+
+### Project Settings
+- Optimized quality settings for target platforms
+- Input system configuration
+- Physics settings
+- Time and rendering configurations
+- Build settings for multiple platforms
+
+### Development Tools
+- Code formatting rules (.editorconfig)
+- Git configuration with Unity-optimized .gitignore
+- Assembly definition files for better compilation
+- Custom editor scripts for workflow improvement
+
+### Version Control Setup
+- Git repository initialization
+- Unity-specific .gitignore
+- LFS configuration for large assets
+- Branching strategy documentation
+
+## Usage:
+
+```bash
+npx claude-code-templates@latest --command unity-project-setup
+```
+
+## Interactive Options:
+
+1. **Project Type Selection**
+   - 2D Game
+   - 3D Game
+   - Mobile Game
+   - VR/AR Game
+   - Hybrid (2D/3D)
+
+2. **Target Platforms**
+   - PC (Windows/Mac/Linux)
+   - Mobile (iOS/Android)
+   - Console (PlayStation/Xbox/Nintendo)
+   - WebGL
+   - VR (Oculus/SteamVR)
+
+3. **Version Control**
+   - Git
+   - Plastic SCM
+   - Perforce
+   - None
+
+4. **Additional Packages**
+   - TextMeshPro
+   - Post Processing
+   - Unity Ads
+   - Unity Analytics
+   - Unity Cloud Build
+   - Custom package selection
+
+## Generated Files:
+
+### Core Scripts
+- `GameManager.cs` - Main game controller
+- `SceneLoader.cs` - Scene management system
+- `AudioManager.cs` - Audio system controller
+- `InputManager.cs` - Input handling system
+- `UIManager.cs` - UI system manager
+- `SaveSystem.cs` - Save/load functionality
+
+### Editor Tools
+- `ProjectSetupWindow.cs` - Custom editor window
+- `SceneQuickStart.cs` - Scene setup automation
+- `AssetValidator.cs` - Asset validation tools
+- `BuildAutomation.cs` - Build pipeline helpers
+
+### Configuration Files
+- `ProjectSettings.asset` - Optimized project settings
+- `QualitySettings.asset` - Multi-platform quality tiers
+- `InputActions.inputactions` - Input system configuration
+- `AssemblyDefinitions` - Modular compilation setup
+
+### Documentation
+- `README.md` - Project overview and setup instructions
+- `CONTRIBUTING.md` - Development guidelines
+- `CHANGELOG.md` - Version history template
+- `API_REFERENCE.md` - Code documentation template
+
+## Post-Setup Checklist:
+
+- [ ] Review and adjust quality settings for target platforms
+- [ ] Configure input actions for your game controls
+- [ ] Set up build configurations for all target platforms
+- [ ] Review folder structure and rename as needed
+- [ ] Configure version control and make initial commit
+- [ ] Set up continuous integration if required
+- [ ] Configure analytics and crash reporting
+- [ ] Review and customize coding standards
+
+## Platform-Specific Configurations:
+
+### Mobile
+- Touch input configuration
+- Performance optimization settings
+- Battery usage optimization
+- App store submission setup
+
+### PC
+- Multi-resolution support
+- Keyboard/mouse input setup
+- Graphics options menu template
+- Windows/Mac/Linux build configs
+
+### Console
+- Platform-specific input mapping
+- Achievement/trophy integration setup
+- Online services configuration
+- Certification requirement templates
+
+This command creates a production-ready Unity project structure that scales from prototype to shipped game, following industry best practices and Unity's recommended patterns.

package/cli-tool/components/commands/git/feature.md

@@ -0,0 +1,196 @@
+---
+allowed-tools: Bash(git:*)
+argument-hint: <feature-name>
+description: Create a new Git Flow feature branch from develop with proper naming and tracking
+model: sonnet
+---
+
+# Git Flow Feature Branch
+
+Create new feature branch: **$ARGUMENTS**
+
+## Current Repository State
+
+- Current branch: !`git branch --show-current`
+- Git status: !`git status --porcelain`
+- Develop branch status: !`git log develop..origin/develop --oneline 2>/dev/null | head -5 || echo "No remote tracking for develop"`
+
+## Task
+
+Create a Git Flow feature branch following these steps:
+
+### 1. Pre-Flight Validation
+
+- **Check git repository**: Verify we're in a valid git repository
+- **Validate feature name**: Ensure `$ARGUMENTS` is provided and follows naming conventions:
+  - ✅ Valid: `user-authentication`, `payment-integration`, `dashboard-redesign`
+  - ❌ Invalid: `feat1`, `My_Feature`, empty name
+- **Check for uncommitted changes**:
+  - If changes exist, warn user and ask to commit/stash first
+  - OR offer to stash changes automatically
+- **Verify develop branch exists**: Ensure `develop` branch is present
+
+### 2. Create Feature Branch
+
+Execute the following workflow:
+
+```bash
+# Switch to develop branch
+git checkout develop
+
+# Pull latest changes from remote
+git pull origin develop
+
+# Create feature branch with Git Flow naming convention
+git checkout -b feature/$ARGUMENTS
+
+# Set up remote tracking
+git push -u origin feature/$ARGUMENTS
+```
+
+### 3. Provide Status Report
+
+After successful creation, display:
+
+```
+✓ Switched to develop branch
+✓ Pulled latest changes from origin/develop
+✓ Created branch: feature/$ARGUMENTS
+✓ Set up remote tracking: origin/feature/$ARGUMENTS
+✓ Pushed branch to remote
+
+🌿 Feature Branch Ready
+
+Branch: feature/$ARGUMENTS
+Base: develop
+Status: Clean working directory
+
+🎯 Next Steps:
+1. Start implementing your feature
+2. Make commits using conventional format:
+   git commit -m "feat: your changes"
+3. Push changes regularly: git push
+4. When complete, use /finish to merge back to develop
+
+💡 Git Flow Tips:
+- Keep commits atomic and well-described
+- Push frequently to avoid conflicts
+- Use conventional commit format (feat:, fix:, etc.)
+- Test thoroughly before finishing
+```
+
+### 4. Error Handling
+
+Handle these scenarios gracefully:
+
+**Uncommitted Changes:**
+```
+⚠️  You have uncommitted changes:
+M  src/file1.js
+M  src/file2.js
+
+Options:
+1. Commit changes first
+2. Stash changes: git stash
+3. Discard changes: git checkout .
+
+What would you like to do? [1/2/3]
+```
+
+**Feature Name Not Provided:**
+```
+❌ Feature name is required
+
+Usage: /feature <feature-name>
+
+Examples:
+  /feature user-profile-page
+  /feature api-v2-integration
+  /feature payment-gateway
+
+Feature names should:
+- Be descriptive and concise
+- Use kebab-case (lowercase-with-hyphens)
+- Describe what the feature does
+```
+
+**Branch Already Exists:**
+```
+❌ Branch feature/$ARGUMENTS already exists
+
+Existing feature branches:
+  feature/user-authentication
+  feature/payment-gateway
+  feature/$ARGUMENTS ← This one
+
+Options:
+1. Switch to existing branch: git checkout feature/$ARGUMENTS
+2. Use a different feature name
+3. Delete existing and recreate (destructive!)
+```
+
+**Develop Behind Remote:**
+```
+⚠️  Local develop is behind origin/develop by 5 commits
+
+✓ Pulling latest changes...
+✓ Develop is now up to date
+✓ Ready to create feature branch
+```
+
+**No Develop Branch:**
+```
+❌ Develop branch not found
+
+Git Flow requires a 'develop' branch. Create it with:
+  git checkout -b develop
+  git push -u origin develop
+
+Or initialize Git Flow:
+  git flow init
+```
+
+## Git Flow Context
+
+This command is part of the Git Flow branching strategy:
+
+- **main**: Production-ready code (protected)
+- **develop**: Integration branch for features (protected)
+- **feature/***: New features (you are here)
+- **release/***: Release preparation
+- **hotfix/***: Emergency production fixes
+
+Feature branches:
+- Branch from: `develop`
+- Merge back to: `develop`
+- Naming convention: `feature/<descriptive-name>`
+- Lifecycle: Short to medium term
+
+## Environment Variables
+
+This command respects:
+- `GIT_FLOW_DEVELOP_BRANCH`: Develop branch name (default: "develop")
+- `GIT_FLOW_PREFIX_FEATURE`: Feature prefix (default: "feature/")
+
+## Related Commands
+
+- `/finish` - Complete and merge feature branch to develop
+- `/flow-status` - Check current Git Flow status
+- `/release <version>` - Create release branch from develop
+- `/hotfix <name>` - Create hotfix branch from main
+
+## Best Practices
+
+**DO:**
+- ✅ Use descriptive feature names
+- ✅ Keep feature scope focused and small
+- ✅ Push to remote regularly
+- ✅ Test your changes before finishing
+- ✅ Use conventional commit messages
+
+**DON'T:**
+- ❌ Create features directly from main
+- ❌ Use generic names like "feature1"
+- ❌ Let feature branches live too long
+- ❌ Mix multiple unrelated features
+- ❌ Skip testing before merging