claude-autopm 3.1.2 → 3.2.1

package/packages/plugin-pm/commands/pm:prd-new.md

@@ -23,9 +23,14 @@ Create new product requirement document - interactively or from existing content
 : PRD content for non-interactive mode
 : Use `@filepath` to read from file (e.g., `--content @/path/to/draft.md`)
 : Use inline text for short content (e.g., `--content "# My PRD..."`)
-: Skips interactive wizard completely
+: Skips LLM generation completely
 : Ideal for importing existing PRDs or automated workflows
 
+`--interactive`, `-i`
+: Use interactive terminal prompts (requires interactive terminal)
+: NOT compatible with Claude Code (use default LLM generation instead)
+: Launches traditional brainstorming wizard with readline prompts
+
 `--force`, `-f`
 : Overwrite existing PRD file if it exists
 
@@ -37,11 +42,16 @@ Create new product requirement document - interactively or from existing content
 
 ## Examples
 
-### Interactive mode (default)
+### LLM-assisted generation (default - works in Claude Code)
 ```
 /pm:prd-new user-authentication
 ```
 
+### Interactive terminal mode (requires interactive terminal)
+```
+/pm:prd-new user-authentication --interactive
+```
+
 ### Local mode
 ```
 /pm:prd-new user-authentication --local
@@ -96,9 +106,311 @@ Current API has performance issues...
 ### Mode Detection
 
 Parse the arguments to detect the mode:
-- If `--content @<filepath>` is present → **Content from file mode**
-- If `--content "<text>"` is present → **Content from inline text mode**
-- Otherwise → **Interactive mode**
+- If `--interactive` flag is present → **Interactive Terminal Mode**
+- If `--content @<filepath>` is present → **Content from File Mode**
+- If `--content "<text>"` is present → **Content from Inline Text Mode**
+- Otherwise → **LLM-Assisted Generation Mode** (default)
+
+### LLM-Assisted Generation Mode (DEFAULT - works in Claude Code)
+
+#### Phase 0: Codebase Analysis (MANDATORY)
+
+**CRITICAL**: Before creating any PRD, perform comprehensive codebase analysis to prevent duplicate implementations and identify reusable components.
+
+1. **Search for Existing Functionality**
+
+   Use code-analyzer agent to search the entire codebase:
+
+   ```markdown
+   Task:
+     subagent_type: "code-analyzer"
+     description: "Search for existing '<feature_name>' functionality"
+     prompt: |
+       Search the entire codebase for anything related to: <feature_name>
+
+       Search criteria:
+       - Function names containing: <feature_name> (or related terms)
+       - File names related to: <feature_name>
+       - Class/module names similar to: <feature_name>
+       - Comments/documentation mentioning: <feature_name>
+       - Similar patterns or implementations
+       - Related API endpoints or routes
+       - Database models/schemas related to feature
+
+       Return findings in this format:
+
+       ## Existing Implementations Found
+       - File: [path] - [brief description]
+       - Function: [name] - [what it does]
+       - Component: [name] - [purpose]
+
+       ## Similar Patterns
+       - [description of similar functionality]
+
+       ## Recommendation
+       ✅ Safe to create new PRD (no conflicts found)
+       OR
+       ⚠️ Existing functionality detected - review before proceeding
+
+       ## Reusable Components
+       - [list components that can be reused]
+       - [list utilities that apply]
+   ```
+
+2. **Analyze Dependencies and Integration Points**
+
+   Use code-analyzer agent to identify dependencies:
+
+   ```markdown
+   Task:
+     subagent_type: "code-analyzer"
+     description: "Identify dependencies for '<feature_name>'"
+     prompt: |
+       Identify systems that '<feature_name>' would interact with:
+
+       - **Databases**: What tables/collections would be needed?
+       - **APIs**: Which endpoints would be affected/created?
+       - **External Services**: Third-party integrations needed?
+       - **Internal Modules**: Which existing modules would be used?
+       - **Authentication**: Auth/authorization requirements?
+       - **State Management**: Frontend state considerations?
+
+       Return integration points and potential conflicts.
+   ```
+
+3. **Present Findings to User**
+
+   Format the analysis results for user review:
+
+   ```markdown
+   🔍 **Codebase Analysis Results for: <feature_name>**
+   ═══════════════════════════════════════════════════
+
+   ### Existing Implementations
+   [If found, list each with file path and purpose]
+   [If none found: "✅ No existing implementations detected"]
+
+   ### Dependencies Identified
+   [List each dependency type and specific items]
+
+   ### Reusable Components
+   [List components that can be leveraged]
+   [If none: "No directly reusable components found"]
+
+   ### Potential Conflicts
+   [List any naming conflicts, duplicate logic, etc.]
+   [If none: "✅ No conflicts detected"]
+
+   ### Technology Stack Detected
+   - Backend: [detected frameworks]
+   - Frontend: [detected frameworks]
+   - Database: [detected systems]
+   - Testing: [detected tools]
+
+   ───────────────────────────────────────────────────
+
+   ## Recommendation
+
+   Based on this analysis:
+
+   ✅ **OPTION 1: Create New PRD**
+      No conflicts found. Safe to proceed with new feature.
+
+   ⚠️ **OPTION 2: Extend Existing Feature**
+      Similar functionality found at [path]. Consider extending instead.
+
+   🔄 **OPTION 3: Refactor Existing Code**
+      Duplication detected. Consider refactoring before adding new feature.
+
+   ───────────────────────────────────────────────────
+
+   **Next Step**: Review the analysis above and confirm your choice:
+   - To proceed: Continue with PRD creation
+   - To abort: Stop here and investigate findings
+   ```
+
+4. **User Decision Point**
+
+   After presenting findings, ask user to confirm:
+   ```markdown
+   Based on the codebase analysis above, do you want to:
+
+   1. ✅ Proceed with new PRD (no conflicts found)
+   2. 🔍 Investigate existing implementations first
+   3. ❌ Cancel PRD creation
+
+   [Wait for user response before continuing]
+   ```
+
+#### Phase 1: PRD Existence Check
+
+1. **Pre-check**: Verify PRD doesn't already exist
+   ```bash
+   if [ -f .claude/prds/<feature_name>.md ]; then
+     echo "❌ PRD already exists: <feature_name>"
+     echo "💡 Use --force to overwrite or edit: /pm:prd-edit <feature_name>"
+     exit 1
+   fi
+   ```
+
+#### Phase 2: Generate PRD Content
+
+1. **Generate PRD Content**: Create a comprehensive PRD based on:
+   - Feature name: `<feature_name>`
+   - **Codebase analysis findings** from Phase 0 (existing implementations, dependencies, conflicts)
+   - Project context (analyze existing codebase structure)
+   - Technology stack (detect from package.json, requirements.txt, etc.)
+   - Existing patterns (check similar features)
+   - **Reusable components** identified in analysis
+   - **Integration points** from dependency analysis
+
+3. **PRD Structure**: Use this template:
+   ```markdown
+   ---
+   title: <Title Case Feature Name>
+   status: draft
+   priority: <from --priority or P2>
+   created: <current ISO timestamp>
+   author: <from git config or "claude">
+   timeline: <from --timeline or "TBD">
+   ---
+
+   # PRD: <feature_name>
+
+   ## Executive Summary
+   [Brief overview of the feature - 2-3 sentences]
+
+   ## Codebase Analysis
+   ### Existing Implementations
+   [List any existing functionality found during pre-analysis]
+   [If none: "✅ No existing implementations detected"]
+
+   ### Reusable Components
+   [List components that can be leveraged from existing codebase]
+   [If none: "No directly reusable components found"]
+
+   ### Integration Points
+   [List systems this feature will interact with]
+   - Database: [tables/models needed]
+   - APIs: [endpoints affected]
+   - External Services: [third-party integrations]
+   - Internal Modules: [existing modules to use]
+
+   ### Potential Conflicts
+   [List any naming conflicts or duplicate logic concerns]
+   [If none: "✅ No conflicts detected"]
+
+   ## Problem Statement
+   ### Background
+   [Context and why this feature is needed]
+
+   ### Current State
+   [What exists today and its limitations]
+
+   ### Desired State
+   [What the solution will provide]
+
+   ## Target Users
+   [Who will use this feature]
+
+   ### User Personas
+   - **Primary Users**: [Main user segment]
+   - **Secondary Users**: [Additional beneficiaries]
+
+   ### User Stories
+   - As a [user type], I want to [action], so that [benefit]
+   - As a [user type], I want to [action], so that [benefit]
+
+   ## Key Features
+   ### Must Have (P0)
+   - [ ] [Core feature 1]
+   - [ ] [Core feature 2]
+
+   ### Should Have (P1)
+   - [ ] [Important feature 1]
+   - [ ] [Important feature 2]
+
+   ### Nice to Have (P2)
+   - [ ] [Enhancement 1]
+   - [ ] [Enhancement 2]
+
+   ## Success Metrics
+   ### Key Performance Indicators (KPIs)
+   - **Adoption Rate**: [Target percentage]
+   - **User Satisfaction**: [Target score]
+   - **Performance**: [Response time targets]
+   - **Quality**: [Error rate targets]
+
+   ## Technical Requirements
+   ### Architecture Considerations
+   [System components affected, integration points, data flow]
+
+   ### Non-Functional Requirements
+   - **Performance**: [Specific targets]
+   - **Scalability**: [Capacity requirements]
+   - **Security**: [Auth/authorization requirements]
+   - **Reliability**: [Uptime targets]
+
+   ### Dependencies
+   - [External services or APIs]
+   - [Internal systems or components]
+   - [Third-party libraries or tools]
+
+   ## Implementation Plan
+   ### Phase 1: Foundation
+   - [ ] [Initial tasks]
+
+   ### Phase 2: Core Features
+   - [ ] [Main development]
+
+   ### Phase 3: Enhancement
+   - [ ] [Additional features]
+
+   ### Phase 4: Release
+   - [ ] [Final testing and deployment]
+
+   ## Risks and Mitigation
+   ### Technical Risks
+   - **Risk 1**: [Description and mitigation]
+
+   ### Business Risks
+   - **Risk 1**: [Impact and contingency]
+
+   ## Open Questions
+   - [ ] [Question requiring clarification]
+   - [ ] [Question needing stakeholder input]
+
+   ## Appendix
+   ### References
+   - [Related documentation]
+
+   ### Changelog
+   - [timestamp]: Initial PRD created
+   ```
+
+4. **Write PRD File**:
+   ```bash
+   mkdir -p .claude/prds
+   # Use Write tool to create .claude/prds/<feature_name>.md
+   ```
+
+5. **Confirm Success**: Show next steps
+
+### Interactive Terminal Mode (`--interactive`)
+
+**⚠️ WARNING**: This mode requires an interactive terminal and **will NOT work in Claude Code**.
+
+Run `node .claude/scripts/pm/prd-new.js $ARGUMENTS` using the Bash tool and show me the complete output.
+
+This will launch an interactive brainstorming session that will:
+1. Prompt for product vision
+2. Gather information about target users
+3. Collect key features through interactive prompts
+4. Define success metrics
+5. Capture technical considerations
+6. Generate a comprehensive PRD with proper frontmatter
+
+The script handles all validation, creates the necessary directories, and saves the PRD to `.claude/prds/<feature_name>.md`.
 
 ### Content from File Mode (`--content @filepath`)
 
@@ -128,20 +440,6 @@ Parse the arguments to detect the mode:
 
 Same as file mode, but use the inline text directly instead of reading from file.
 
-### Interactive Mode (default)
-
-Run `node .claude/scripts/pm/prd-new.js $ARGUMENTS` using the Bash tool and show me the complete output.
-
-This will launch an interactive brainstorming session that will:
-1. Prompt for product vision
-2. Gather information about target users
-3. Collect key features through interactive prompts
-4. Define success metrics
-5. Capture technical considerations
-6. Generate a comprehensive PRD with proper frontmatter
-
-The script handles all validation, creates the necessary directories, and saves the PRD to `.claude/prds/<feature_name>.md`.
-
 ## Output
 
 After successful PRD creation, show:

package/packages/plugin-pm/scripts/pm/epic-sync/create-epic-issue.sh

@@ -74,4 +74,49 @@ if [[ -z "$epic_number" ]]; then
     exit 1
 fi
 
+# Add documentation comment to issue
+echo "📎 Adding local documentation links to issue #$epic_number..."
+
+# Extract PRD name from epic file
+prd_name=$(grep -A 5 "^prd:" "$EPIC_FILE" | grep -v "^prd:" | head -1 | tr -d ' ')
+if [[ -z "$prd_name" ]]; then
+    prd_name="$EPIC_NAME"
+fi
+
+# Create comment with documentation links
+cat > /tmp/epic-doc-comment.md <<EOF
+📁 **Local Documentation**
+
+This epic is tracked locally at:
+- **Epic file**: \`.claude/epics/$EPIC_NAME/epic.md\`
+- **PRD**: \`.claude/prds/$prd_name.md\`
+
+**For developers**: Clone the repository and review these files for:
+- Complete technical specifications
+- Acceptance criteria
+- Implementation details
+- Task breakdown
+
+**File Structure**:
+\`\`\`
+.claude/epics/$EPIC_NAME/
+├── epic.md           # This epic (#$epic_number)
+├── 001.md           # Task 1 (will be issue #XX)
+├── 002.md           # Task 2 (will be issue #XX)
+└── ...              # Additional tasks
+\`\`\`
+
+Tasks will be created as sub-issues and linked here.
+EOF
+
+# Add comment to issue
+if gh issue comment "$epic_number" --body-file /tmp/epic-doc-comment.md &> /dev/null; then
+    echo "✅ Documentation links added to issue #$epic_number"
+else
+    echo "⚠️ Warning: Failed to add documentation comment (issue created successfully)"
+fi
+
+# Cleanup
+rm -f /tmp/epic-doc-comment.md
+
 echo "$epic_number"

package/packages/plugin-pm/scripts/pm/epic-sync/create-task-issues.sh

@@ -72,6 +72,30 @@ for task_file in $task_files; do
         echo "#$issue_number ✓"
         # Save mapping: old_name -> new_number
         echo "$task_basename $issue_number" >> "$MAPPING_FILE"
+
+        # Add documentation comment to task issue
+        cat > /tmp/task-doc-comment.md <<EOF
+📁 **Local Documentation**
+
+This task is tracked locally at:
+- **Task file**: \`.claude/epics/$EPIC_NAME/$task_basename.md\`
+- **Epic file**: \`.claude/epics/$EPIC_NAME/epic.md\`
+
+**For developers**: Clone the repository and review the local task file for:
+- Detailed implementation requirements
+- Acceptance criteria
+- Technical specifications
+- Dependencies and related tasks
+
+**Part of Epic**: #$EPIC_NUMBER
+EOF
+
+        # Add comment (silent to avoid clutter in output)
+        if gh issue comment "$issue_number" --body-file /tmp/task-doc-comment.md &> /dev/null; then
+            echo "      📎 Documentation links added"
+        fi
+
+        rm -f /tmp/task-doc-comment.md
     else
         echo "FAILED"
         echo "⚠️  Failed to create issue for $task_basename"

package/packages/plugin-pm/scripts/pm/epic-sync/update-epic-file.sh

@@ -62,12 +62,17 @@ if [[ -f "$MAPPING_FILE" ]]; then
 
     # Read mapping and update task references
     while read -r old_name new_number; do
+        # Cross-platform sed: create temp file instead of in-place
         # Update checkbox items like "- [ ] 001" to "- [ ] #2"
-        sed -i "s/- \[ \] $old_name\b/- [ ] #$new_number/g" "$EPIC_FILE.tmp"
-        sed -i "s/- \[x\] $old_name\b/- [x] #$new_number/g" "$EPIC_FILE.tmp"
+        sed "s/- \[ \] $old_name\b/- [ ] #$new_number/g" "$EPIC_FILE.tmp" > "$EPIC_FILE.tmp2"
+        mv "$EPIC_FILE.tmp2" "$EPIC_FILE.tmp"
+
+        sed "s/- \[x\] $old_name\b/- [x] #$new_number/g" "$EPIC_FILE.tmp" > "$EPIC_FILE.tmp2"
+        mv "$EPIC_FILE.tmp2" "$EPIC_FILE.tmp"
 
         # Update task links
-        sed -i "s/Task $old_name\b/Task #$new_number/g" "$EPIC_FILE.tmp"
+        sed "s/Task $old_name\b/Task #$new_number/g" "$EPIC_FILE.tmp" > "$EPIC_FILE.tmp2"
+        mv "$EPIC_FILE.tmp2" "$EPIC_FILE.tmp"
     done < "$MAPPING_FILE"
 fi
 

package/packages/plugin-pm/scripts/pm/epic-sync/update-references.sh

@@ -31,7 +31,7 @@ REPO=$(gh repo view --json nameWithOwner -q .nameWithOwner 2>/dev/null || echo "
 
 echo "🔗 Updating task references and renaming files"
 
-# Read mapping file and rename files
+# First pass: Rename files and update frontmatter
 while read -r old_name new_number; do
     old_file="$EPIC_DIR/$old_name.md"
     new_file="$EPIC_DIR/$new_number.md"
@@ -85,5 +85,35 @@ while read -r old_name new_number; do
 
 done < "$MAPPING_FILE"
 
+# Second pass: Update cross-references within renamed files
+echo ""
+echo "   Updating cross-references within task files..."
+
+# Read all renamed files
+find "$EPIC_DIR" -name "[0-9]*.md" -type f | while read -r task_file; do
+    # Create temp file for updates
+    cp "$task_file" "$task_file.tmp"
+
+    # Update all task references using the mapping
+    while read -r old_name new_number; do
+        # Update patterns like "task 001", "Task 001", "#001", "issue 001"
+        sed "s/\btask $old_name\b/task #$new_number/gi" "$task_file.tmp" > "$task_file.tmp2"
+        mv "$task_file.tmp2" "$task_file.tmp"
+
+        sed "s/#$old_name\b/#$new_number/g" "$task_file.tmp" > "$task_file.tmp2"
+        mv "$task_file.tmp2" "$task_file.tmp"
+
+        sed "s/\bissue $old_name\b/issue #$new_number/gi" "$task_file.tmp" > "$task_file.tmp2"
+        mv "$task_file.tmp2" "$task_file.tmp"
+
+        # Update dependency format: "depends on 001" -> "depends on #46"
+        sed "s/depends on $old_name\b/depends on #$new_number/gi" "$task_file.tmp" > "$task_file.tmp2"
+        mv "$task_file.tmp2" "$task_file.tmp"
+    done < "$MAPPING_FILE"
+
+    # Replace original with updated version
+    mv "$task_file.tmp" "$task_file"
+done
+
 echo ""
 echo "✅ Task files renamed and frontmatter updated"

package/packages/plugin-pm/scripts/pm/prd-new.js

@@ -612,6 +612,20 @@ ${data.technical || 'Technical requirements to be specified...'}
   }
 
   async run(args) {
+    // Check if running in non-interactive environment (e.g., Claude Code)
+    if (!process.stdin.isTTY) {
+      console.error('❌ Error: This script requires an interactive terminal');
+      console.error('\n💡 Solutions:');
+      console.error('   1. Use LLM-assisted generation (default):');
+      console.error('      /pm:prd-new <feature-name>');
+      console.error('   2. Use --content flag with existing content:');
+      console.error('      /pm:prd-new <feature-name> --content @path/to/file.md');
+      console.error('   3. Run in a regular terminal (not Claude Code):');
+      console.error('      node .claude/scripts/pm/prd-new.js <feature-name>');
+      console.error('\n📚 See: /pm:help prd-new');
+      process.exit(1);
+    }
+
     // Parse arguments
     let prdName = null;
     let templateName = null;

package/autopm/.claude/.env

@@ -1,158 +0,0 @@
-# ============================================
-# MCP (Model Context Protocol) Configuration
-# ============================================
-
-# Context7 MCP Server Configuration
-# ------------------------------------------
-# Get your API key from https://context7.com/account
-CONTEXT7_API_KEY=your-context7-api-key-here
-
-# MCP endpoint URL (default: mcp.context7.com/mcp)
-CONTEXT7_MCP_URL=mcp.context7.com/mcp
-
-# Context7 API URL (default: context7.com/api/v1)
-CONTEXT7_API_URL=context7.com/api/v1
-
-# Your Context7 workspace ID or name
-CONTEXT7_WORKSPACE=your-workspace-id-or-name
-
-# Context mode: documentation or codebase
-# documentation = for accessing docs, codebase = for code context
-CONTEXT7_MODE=documentation
-
-# Cache TTL in seconds (optional, default: 3600)
-CONTEXT7_CACHE_TTL=3600
-
-# ============================================
-# GitHub MCP Server Configuration
-# ============================================
-
-# GitHub Personal Access Token
-# Create at: https://github.com/settings/tokens
-# Required scopes: repo, workflow, read:org
-GITHUB_TOKEN=your-github-personal-access-token
-
-# GitHub API URL (default for public GitHub)
-GITHUB_API_URL=https://api.github.com
-
-# ============================================
-# Playwright MCP Server Configuration
-# ============================================
-
-# Browser to use for Playwright tests (chromium, firefox, webkit)
-PLAYWRIGHT_BROWSER=chromium
-
-# Run browser in headless mode (true/false)
-PLAYWRIGHT_HEADLESS=true
-
-# ============================================
-# Azure DevOps Configuration (Optional)
-# ============================================
-
-# Azure DevOps Personal Access Token
-# Create at: https://dev.azure.com/{yourorganization}/_usersSettings/tokens
-AZURE_DEVOPS_PAT=your-azure-devops-pat
-
-# Azure DevOps Organization
-AZURE_DEVOPS_ORG=your-organization
-
-# Azure DevOps Project
-AZURE_DEVOPS_PROJECT=your-project
-
-# Azure DevOps API URL (optional, for Azure DevOps Server)
-# AZURE_DEVOPS_API_URL=https://dev.azure.com
-
-# ============================================
-# Cloud Provider Credentials (Optional)
-# ============================================
-
-# AWS Configuration
-# ------------------------------------------
-AWS_ACCESS_KEY_ID=your-aws-access-key
-AWS_SECRET_ACCESS_KEY=your-aws-secret-key
-AWS_DEFAULT_REGION=us-east-1
-# Optional: AWS profile to use
-# AWS_PROFILE=default
-
-# Azure Cloud Configuration
-# ------------------------------------------
-AZURE_SUBSCRIPTION_ID=your-azure-subscription-id
-AZURE_TENANT_ID=your-azure-tenant-id
-AZURE_CLIENT_ID=your-azure-client-id
-AZURE_CLIENT_SECRET=your-azure-client-secret
-# Optional: Azure Cloud environment (AzureCloud, AzureChinaCloud, AzureUSGovernment, AzureGermanCloud)
-# AZURE_CLOUD_ENVIRONMENT=AzureCloud
-
-# Google Cloud Platform Configuration
-# ------------------------------------------
-GCP_PROJECT_ID=your-gcp-project-id
-# Path to service account key JSON file
-GCP_SERVICE_ACCOUNT_KEY=path/to/service-account-key.json
-# Optional: GCP region
-# GCP_REGION=us-central1
-
-# ============================================
-# AI Provider API Keys (Optional)
-# ============================================
-
-# OpenAI Configuration
-# ------------------------------------------
-OPENAI_API_KEY=your-openai-api-key
-# Optional: OpenAI organization ID
-# OPENAI_ORG_ID=your-org-id
-# Optional: API base URL for custom endpoints
-# OPENAI_API_BASE=https://api.openai.com/v1
-
-# Google Gemini Configuration
-# ------------------------------------------
-GEMINI_API_KEY=your-gemini-api-key
-# Optional: Gemini model to use
-# GEMINI_MODEL=gemini-pro
-
-# ============================================
-# Additional MCP Servers (Optional)
-# ============================================
-
-# Database MCP Server
-# ------------------------------------------
-# DATABASE_MCP_URL=your-database-mcp-url
-# DATABASE_MCP_TOKEN=your-database-token
-
-# Custom MCP Server
-# ------------------------------------------
-# CUSTOM_MCP_URL=your-custom-mcp-url
-# CUSTOM_MCP_API_KEY=your-custom-api-key
-
-# ============================================
-# MCP Context Pool Settings
-# ============================================
-
-# Maximum context pool size for shared contexts
-MCP_CONTEXT_POOL_MAX_SIZE=100MB
-
-# Context retention period (e.g., 7d, 24h, 1w)
-MCP_CONTEXT_RETENTION=7d
-
-# Context refresh interval (daily, hourly, on-change)
-MCP_CONTEXT_REFRESH=daily
-
-# ============================================
-# Development & Testing
-# ============================================
-
-# Enable MCP debug logging (true/false)
-MCP_DEBUG=false
-
-# MCP log level (error, warn, info, debug, trace)
-MCP_LOG_LEVEL=info
-
-# ============================================
-# IMPORTANT SECURITY NOTES
-# ============================================
-# 1. NEVER commit this file to version control
-# 2. This file is already in .gitignore
-# 3. Keep this file secure with proper permissions
-# 4. Rotate API keys regularly
-# 5. Use environment-specific .env files for different environments
-# 6. Consider using a secrets management service for production
-# ============================================