claude-code-templates 1.3.2 → 1.3.4

package/README.md

@@ -176,6 +176,7 @@ The CLI allows you to selectively enable automation hooks that enhance your deve
 - `CLAUDE.md` - Main configuration file for Claude Code
 - `.claude/settings.json` - Language-specific settings with selected automation hooks
 - `.claude/commands/` - Custom commands for common tasks
+- `.mcp.json` - Model Context Protocol server configurations
 
 ### Automation Hooks
 Each language template includes selectable automation hooks for:
@@ -184,6 +185,19 @@ Each language template includes selectable automation hooks for:
 - **Stop**: Final checks before session ends (e.g., linting changed files, bundle analysis)
 - **Notification**: Logging and monitoring of Claude Code activities
 
+### MCP Servers (Model Context Protocol)
+Configure external tools and services to extend Claude's capabilities:
+- **IDE Integration** - VS Code language diagnostics and Jupyter kernel execution
+- **Web Search** - Real-time web search for up-to-date information and documentation
+- **Filesystem Tools** - Advanced file operations, monitoring, and directory management
+- **Database Tools** - Database connections, schema inspection, and query execution
+
+MCP servers are configured in `.mcp.json` and enable Claude to:
+- Execute code in VS Code or Jupyter environments
+- Search the web for current information
+- Perform advanced file system operations
+- Connect to databases and run queries
+
 ### Language-Specific Commands
 Each language template includes optimized commands for:
 - Testing (Jest, pytest, Cargo test, Go test)
@@ -274,22 +288,45 @@ Target directory: /path/to/your/project
    ◉ Stop: Run ESLint on changed files before stopping
    ```
 
-6. **Final Confirmation** 🚀
+6. **MCP Server Selection** 🔧
    ```
-   🚀 Setup Claude Code for javascript-typescript with react (5 commands) (9 hooks)? (Y/n)
+   🔧 Select MCP servers to include (use space to select):
+   ◉ IDE Integration - VS Code language diagnostics and code execution
+   ◉ Web Search - Search the web for up-to-date information
+   ◯ Filesystem Tools - Advanced file operations and monitoring
+   ◯ Database Tools - Database connection and query capabilities
+   ```
+   - Choose Model Context Protocol servers to extend Claude's capabilities
+   - IDE Integration provides VS Code diagnostics and Jupyter kernel execution
+   - Web Search enables real-time web searches within Claude conversations
+   - Additional tools for filesystem operations and database management
+
+7. **Final Confirmation** 🚀
    ```
-   - Review your choices including selected commands and hooks
+   🚀 Setup Claude Code for javascript-typescript with react (5 commands) (9 hooks) (4 MCP)? (Y/n)
+   ```
+   - Review your choices including selected commands, hooks, and MCP servers
+   - Shows total count of each component being installed
    - Type 'n' to cancel, 'y' or Enter to proceed
 
-7. **Installation** 📁
+8. **Installation** 📁
    ```
    📋 Existing CLAUDE.md backed up to CLAUDE.md.backup
    ✓ Copied javascript-typescript/CLAUDE.md → CLAUDE.md
-   ✓ Copied javascript-typescript/.claude → .claude (with selected hooks)
-   ✓ Copied react-specific commands → .claude/commands
-   📋 Installed 5 commands
+   ✓ Copied base configuration and commands javascript-typescript/.claude → .claude
+   ✓ Copied javascript-typescript/.mcp.json → .mcp.json (with selected MCPs)
+   ✓ Copied framework commands javascript-typescript/examples/react-app/.claude/commands → .claude/commands
    🔧 Installed 9 automation hooks
+   🔧 Installed 4 MCP servers
    ✅ Claude Code configuration setup complete!
+   📚 Next steps:
+     1. Review the generated CLAUDE.md file
+     2. Customize the configuration for your project
+     3. Start using Claude Code with: claude
+   💡 Language-specific features for javascript-typescript have been configured
+   🎯 Framework-specific commands for react are available
+   🔧 9 automation hooks have been configured
+   🔧 4 MCP servers have been configured
    ```
 
 ## 🛡️ Safe Installation
@@ -312,34 +349,109 @@ Target directory: /path/to/your/project
 
 ## Development
 
-### Setup
+### Setup for Contributing
 ```bash
-git clone https://github.com/your-username/claude-code-templates.git
+git clone https://github.com/davila7/claude-code-templates.git
 cd claude-code-templates/cli-tool
 npm install
 ```
 
-### Testing
+### Local Development
 ```bash
-# Test locally
-npm start
+# Link the package for local testing
+npm link
+
+# Test locally (will use your local changes)
+claude-code-templates
 
 # Test with specific options
-npm start -- --language python --framework django
+claude-code-templates --language python --framework django
+
+# Run test suite
+npm test
+
+# Unlink when done
+npm unlink -g claude-code-templates
 ```
 
-### Publishing
+### Testing Changes
 ```bash
-npm publish
+# Run the comprehensive test suite
+npm test
+
+# Test specific scenarios manually
+npm start -- --dry-run --language javascript-typescript --framework react
+npm start -- --dry-run --language python --framework django
+```
+
+### Project Structure
+```
+cli-tool/
+├── src/                    # Source code
+│   ├── command-scanner.js  # Scans and loads commands
+│   ├── file-operations.js  # Handles file copying
+│   ├── hook-scanner.js     # Manages automation hooks
+│   ├── index.js           # Main entry point
+│   ├── prompts.js         # Interactive CLI prompts
+│   ├── templates.js       # Template configuration
+│   └── utils.js           # Utility functions
+├── templates/             # Language and framework templates
+│   ├── common/
+│   ├── javascript-typescript/
+│   ├── python/
+│   ├── go/
+│   └── rust/
+└── bin/                   # Executable scripts
 ```
 
 ## Contributing
 
-1. Fork the repository
-2. Create a feature branch
-3. Make your changes
-4. Test thoroughly
-5. Submit a pull request
+We welcome contributions! Here's how to get started:
+
+### 1. Fork & Clone
+```bash
+# Fork the repository on GitHub, then:
+git clone https://github.com/your-username/claude-code-templates.git
+cd claude-code-templates
+```
+
+### 2. Create a Feature Branch
+```bash
+git checkout -b feature/your-feature-name
+# or
+git checkout -b fix/issue-description
+```
+
+### 3. Make Your Changes
+- Add new language templates in `templates/`
+- Add new framework examples in `templates/language/examples/`
+- Update commands, hooks, or core functionality
+- Follow existing code patterns
+
+### 4. Test Thoroughly
+```bash
+cd cli-tool
+npm test                    # Run test suite
+npm start -- --dry-run     # Manual testing
+```
+
+### 5. Submit a Pull Request
+- Commit with clear, descriptive messages
+- Push to your fork
+- Open a PR with description of changes
+- Link any related issues
+
+### Adding New Languages
+1. Create `templates/your-language/` directory
+2. Add `CLAUDE.md`, `.claude/settings.json`, and `.mcp.json`
+3. Create commands in `.claude/commands/`
+4. Add framework examples in `examples/`
+5. Update `src/templates.js` configuration
+
+### Adding New Frameworks
+1. Create `templates/language/examples/framework-name/`
+2. Add framework-specific commands and CLAUDE.md
+3. Update the framework detection logic if needed
 
 ## License
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "claude-code-templates",
-  "version": "1.3.2",
-  "description": "CLI tool to setup Claude Code configurations with framework-specific commands and automation hooks for JavaScript/TypeScript and Python projects",
+  "version": "1.3.4",
+  "description": "CLI tool to setup Claude Code configurations with framework-specific commands, automation hooks and MCP Servers for your projects",
   "main": "src/index.js",
   "bin": {
     "create-claude-config": "bin/create-claude-config.js",
@@ -69,6 +69,7 @@
   "files": [
     "bin/",
     "src/",
+    "templates/",
     "README.md"
   ]
 }

package/src/command-scanner.js

@@ -7,7 +7,7 @@ const path = require('path');
  * @returns {Array} Array of available commands with metadata
  */
 function getAvailableCommands(language) {
-  const templatesDir = path.join(__dirname, '../../');
+  const templatesDir = path.join(__dirname, '../templates');
   const languageDir = path.join(templatesDir, language);
   
   // Check if language directory exists

package/src/file-operations.js

@@ -4,7 +4,7 @@ const chalk = require('chalk');
 const { getHooksForLanguage, filterHooksBySelection, getMCPsForLanguage, filterMCPsBySelection } = require('./hook-scanner');
 
 async function copyTemplateFiles(templateConfig, targetDir) {
-  const templateDir = path.join(__dirname, '../../');
+  const templateDir = path.join(__dirname, '../templates');
   
   // Check if CLAUDE.md already exists
   const claudeFile = path.join(targetDir, 'CLAUDE.md');

package/src/hook-scanner.js

@@ -267,7 +267,7 @@ function getHookDescription(hook, matcher, type) {
  * @returns {Array} Array of available hooks for the language
  */
 function getHooksForLanguage(language) {
-  const templateDir = path.join(__dirname, '../../', language);
+  const templateDir = path.join(__dirname, '../templates', language);
   const settingsPath = path.join(templateDir, '.claude', 'settings.json');
   
   return getHooksFromSettings(settingsPath);
@@ -399,7 +399,7 @@ function getDefaultMCPSelection(serverId) {
  * @returns {Array} Array of available MCPs for the language
  */
 function getMCPsForLanguage(language) {
-  const templateDir = path.join(__dirname, '../../', language);
+  const templateDir = path.join(__dirname, '../templates', language);
   const mcpPath = path.join(templateDir, '.mcp.json');
   
   return getMCPsFromFile(mcpPath);

package/templates/common/.claude/commands/git-workflow.md

@@ -0,0 +1,239 @@
+# Git Workflow Helper
+
+Manage Git workflows with best practices and common operations.
+
+## Purpose
+
+This command helps you perform common Git operations following best practices for collaborative development.
+
+## Usage
+
+```
+/git-workflow
+```
+
+## What this command does
+
+1. **Guides through Git operations** with proper workflow
+2. **Suggests best practices** for commits and branches
+3. **Helps with conflict resolution** and merging
+4. **Provides templates** for commit messages
+5. **Manages branching strategies** (Git Flow, GitHub Flow)
+
+## Common Workflows
+
+### Feature Development
+```bash
+# Create and switch to feature branch
+git checkout -b feature/user-authentication
+
+# Work on your feature
+# ... make changes ...
+
+# Stage and commit changes
+git add .
+git commit -m "feat: add user authentication system
+
+- Implement login/logout functionality
+- Add password validation
+- Create user session management
+- Add authentication middleware"
+
+# Push feature branch
+git push -u origin feature/user-authentication
+
+# Create pull request (via GitHub/GitLab interface)
+```
+
+### Hotfix Workflow
+```bash
+# Create hotfix branch from main
+git checkout main
+git checkout -b hotfix/security-patch
+
+# Fix the issue
+# ... make changes ...
+
+# Commit the fix
+git commit -m "fix: resolve security vulnerability in auth module
+
+- Patch XSS vulnerability in login form
+- Update input validation
+- Add CSRF protection"
+
+# Push and create urgent PR
+git push -u origin hotfix/security-patch
+```
+
+### Sync with Remote
+```bash
+# Update main branch
+git checkout main
+git pull origin main
+
+# Update feature branch with latest main
+git checkout feature/your-feature
+git rebase main
+# OR
+git merge main
+```
+
+## Commit Message Conventions
+
+### Conventional Commits Format
+```
+<type>[optional scope]: <description>
+
+[optional body]
+
+[optional footer(s)]
+```
+
+### Common Types
+- **feat**: New feature
+- **fix**: Bug fix
+- **docs**: Documentation changes
+- **style**: Code style changes (formatting, etc.)
+- **refactor**: Code refactoring
+- **test**: Adding or updating tests
+- **chore**: Maintenance tasks
+
+### Examples
+```bash
+# Feature
+git commit -m "feat(auth): add OAuth2 integration"
+
+# Bug fix
+git commit -m "fix(api): handle null response in user endpoint"
+
+# Documentation
+git commit -m "docs: update API documentation for v2.0"
+
+# Breaking change
+git commit -m "feat!: change API response format
+
+BREAKING CHANGE: API responses now use 'data' wrapper"
+```
+
+## Branch Management
+
+### Git Flow Strategy
+```bash
+# Main branches
+main        # Production-ready code
+develop     # Integration branch
+
+# Supporting branches
+feature/*   # New features
+release/*   # Release preparation
+hotfix/*    # Quick fixes to production
+```
+
+### GitHub Flow (Simplified)
+```bash
+# Only main branch + feature branches
+main        # Production-ready code
+feature/*   # All new work
+```
+
+## Conflict Resolution
+
+### When Conflicts Occur
+```bash
+# Start merge/rebase
+git merge feature-branch
+# OR
+git rebase main
+
+# If conflicts occur, Git will list conflicted files
+# Edit each file to resolve conflicts
+
+# Mark conflicts as resolved
+git add conflicted-file.js
+
+# Continue the merge/rebase
+git merge --continue
+# OR
+git rebase --continue
+```
+
+### Conflict Markers
+```javascript
+<<<<<<< HEAD
+// Your current branch code
+const user = getCurrentUser();
+=======
+// Incoming branch code
+const user = getAuthenticatedUser();
+>>>>>>> feature-branch
+```
+
+## Useful Git Commands
+
+### Status and Information
+```bash
+git status                    # Check working directory status
+git log --oneline            # View commit history
+git branch -a                # List all branches
+git remote -v                # List remote repositories
+```
+
+### Undoing Changes
+```bash
+git checkout -- file.js     # Discard changes to file
+git reset HEAD file.js       # Unstage file
+git reset --soft HEAD~1     # Undo last commit (keep changes)
+git reset --hard HEAD~1     # Undo last commit (discard changes)
+```
+
+### Stashing Work
+```bash
+git stash                    # Save current work
+git stash pop               # Apply and remove latest stash
+git stash list              # List all stashes
+git stash apply stash@{1}   # Apply specific stash
+```
+
+## Best Practices
+
+1. **Commit Often** - Make small, focused commits
+2. **Write Clear Messages** - Use conventional commit format
+3. **Test Before Committing** - Ensure code works
+4. **Pull Before Push** - Keep history clean
+5. **Use Branches** - Don't work directly on main
+6. **Review Code** - Use pull requests for collaboration
+7. **Keep History Clean** - Rebase feature branches when appropriate
+
+## Git Hooks (Optional)
+
+### Pre-commit Hook
+```bash
+#!/bin/sh
+# .git/hooks/pre-commit
+
+# Run linter
+npm run lint
+if [ $? -ne 0 ]; then
+  echo "Linting failed. Please fix errors before committing."
+  exit 1
+fi
+
+# Run tests
+npm test
+if [ $? -ne 0 ]; then
+  echo "Tests failed. Please fix tests before committing."
+  exit 1
+fi
+```
+
+### Commit Message Hook
+```bash
+#!/bin/sh
+# .git/hooks/commit-msg
+
+# Check commit message format
+if ! grep -qE "^(feat|fix|docs|style|refactor|test|chore)(\(.+\))?: .{1,50}" "$1"; then
+  echo "Invalid commit message format. Use conventional commits."
+  exit 1
+fi
+```