@vfarcic/dot-ai 0.4.9 → 0.5.1

package/.claude/commands/context-load.md

@@ -0,0 +1,11 @@
+Load context from tmp/context.md to continue previous work session.
+
+Steps:
+1. Read the context file from `tmp/context.md`
+2. Analyze the saved context to understand:
+   - What work was completed previously
+   - Current status and next steps
+   - Available test data and file locations
+   - Technical implementation details
+3. Provide a brief summary of the loaded context
+4. Ask the user how they'd like to proceed based on the context

package/.claude/commands/context-save.md

@@ -0,0 +1,16 @@
+Save current context to tmp/context.md for session continuity.
+
+Steps:
+1. Clear existing context: Delete or empty tmp/context.md if it exists to ensure fresh state
+2. Analyze the current state of work, tasks completed, and next steps
+3. Create a comprehensive context summary including:
+   - Current status and what was accomplished
+   - Technical implementation details
+   - Test data and file locations
+   - Manual testing instructions
+   - Expected results and next steps
+   - Design decisions and architecture notes
+4. Save the fresh context to `tmp/context.md`
+5. Confirm the context has been saved successfully
+
+This ensures each context save represents only the current session state, preventing confusion from stale information and keeping context files manageable.

package/.claude/commands/prd-done.md

@@ -0,0 +1,115 @@
+# PRD Done - Cleanup and Close Issue
+
+This command provides instructions for completing a PRD (Product Requirements Document) implementation by cleaning up tasks and closing the associated GitHub issue.
+
+## Instructions
+
+### 1. Remove Taskmaster Tasks
+
+I'll use MCP tools to clean up completed tasks from the current PRD:
+
+**Option A: Remove all completed tasks (recommended)**
+```
+Use mcp__taskmaster__get_tasks with status="done" to list completed tasks, then use mcp__taskmaster__remove_task for each completed task ID.
+```
+
+**Option B: Remove all tasks if project is complete**
+```
+Use mcp__taskmaster__get_tasks to list all tasks, then use mcp__taskmaster__remove_task to remove each task ID.
+```
+
+**Option C: Remove specific tasks**
+```
+Use mcp__taskmaster__remove_task with specific task IDs that are no longer needed.
+```
+
+### 2. Close Associated GitHub Issue
+
+Use the GitHub CLI to close the issue where the PRD originated:
+
+```bash
+# Close the issue with a completion comment
+gh issue close <issue-number> --comment "✅ PRD implementation completed successfully.
+
+**Completed Features:**
+- [Brief summary of implemented features]
+
+**Deliverables:**
+- [List key deliverables like packages, workflows, etc.]
+
+**Status:** Ready for production use.
+
+🤖 Generated with [Claude Code](https://claude.ai/code)"
+```
+
+### 3. Optional: Create Summary Comment
+
+Before closing, optionally add a detailed summary:
+
+```bash
+gh issue comment <issue-number> --body "## PRD Implementation Summary
+
+### ✅ Completed Tasks
+- Task 1: [Description]
+- Task 2: [Description]
+- Task N: [Description]
+
+### 📦 Deliverables
+- [Package/Feature 1]: Available at [link/version]
+- [Package/Feature 2]: [Description]
+
+### 🔗 Related Resources
+- Documentation: [link]
+- Repository: [link]
+- CI/CD Pipeline: [link]
+
+### 🚀 Next Steps
+- [Any follow-up items or related PRDs]
+
+Implementation completed successfully! 🎉"
+```
+
+## Example Workflow
+
+For PRD issue #11 (npm package distribution):
+
+1. **Clean up taskmaster tasks using MCP tools**
+2. **Add completion summary to GitHub issue**
+3. **Close the GitHub issue**
+
+```bash
+gh issue comment 11 --body "## ✅ NPM Package Distribution - Implementation Complete
+
+### Deliverables
+- **Package**: @vfarcic/dot-ai@0.3.0 published to npm
+- **Global Install**: \`npm install -g @vfarcic/dot-ai\`
+- **npx Support**: \`npx @vfarcic/dot-ai --version\`
+- **CI/CD**: Automated minor version increments and publishing
+- **Security**: CodeQL analysis and dependency audits
+
+### Testing Verified
+- ✅ 385 tests passing (75 skipped integration tests)
+- ✅ npm package distribution working
+- ✅ MCP server compatibility maintained
+- ✅ CLI functionality preserved
+
+Ready for production use! 🚀"
+
+gh issue close 11 --comment "PRD #11 implementation completed and deployed successfully. Package available at https://www.npmjs.com/package/@vfarcic/dot-ai"
+```
+
+## Tips
+
+- **Always verify completion** before closing issues
+- **Use MCP tools** for task management instead of CLI commands
+- **Document deliverables** clearly for future reference  
+- **Link to deployed resources** (packages, docs, etc.)
+- **Mention any follow-up work** or related PRDs
+- **Use consistent formatting** for professional appearance
+
+## Related Commands
+
+- `/prd-start` - Start working on a PRD issue
+- Use MCP `mcp__taskmaster__get_tasks` - View current taskmaster tasks
+- `gh issue list` - List open issues
+- `gh issue view <number>` - View specific issue details

package/.claude/commands/prd-get.md

@@ -0,0 +1,25 @@
+---
+title: "Fetch Open GitHub Issues with PRD Label"
+description: "Fetch all open GitHub issues from this project that have the 'PRD' label"
+---
+
+# Fetch Open GitHub Issues with PRD Label
+
+Please fetch all open GitHub issues from this project repository that have the label "PRD". 
+
+Use the `gh` command to:
+1. Get the current repository information
+2. List all open issues with the "PRD" label
+3. Display the results in a readable format showing:
+   - Issue number
+   - Title
+   - Created date
+   - Author
+
+Commands to run:
+```bash
+!gh repo view --json owner,name
+!gh issue list --label "PRD" --state open --json number,title,createdAt,author
+```
+
+Format the output in a clear, readable way for easy review of all open PRD-related issues.

package/.claude/commands/prd-start.md

@@ -0,0 +1,87 @@
+---
+title: "Start Working on a PRD"
+description: "Interactive workflow to start working on a Product Requirements Document (PRD) issue using Taskmaster MCP for task management"
+---
+
+# Start Working on a PRD
+
+Interactive workflow to start working on a Product Requirements Document (PRD) issue with structured design discussion, GitHub issue management, and Taskmaster MCP task breakdown.
+
+## Workflow Steps:
+
+### 1. PRD Selection
+- Ask user which PRD issue they want to work on (provide issue number)
+- Fetch the selected PRD issue details using: `gh issue view <issue_number> --json title,body,number,url`
+- Display the PRD content for review
+
+### 2. Design Discussion
+- Engage in detailed design discussion about the PRD
+- Explore technical approaches, architecture decisions, and implementation strategies
+- Discuss trade-offs, dependencies, and potential challenges
+- Clarify requirements and acceptance criteria
+- Document key design decisions
+
+### 3. GitHub Issue Update
+- Update the GitHub issue body with design decisions and approach
+- Replace or enhance the original PRD content with current decisions
+- Keep PRDs up-to-date with architectural changes and design decisions
+- Use: `gh issue edit <issue_number> --body "Updated PRD content with design decisions"`
+- Rationale: Issue body should be single source of truth, not scattered in comments
+
+### 4. Task Breakdown Decision
+- Ask user: "Should we break this PRD into smaller tasks or work on it directly?"
+- If tasks are needed: proceed to Taskmaster task creation workflow
+- If working directly: skip to implementation phase
+
+### 5. Taskmaster Task Creation (if chosen)
+- Create a Taskmaster project for the PRD: `PRD-{issue_number}: {title}`
+- Collaborate with user to identify specific tasks/subtasks
+- For each task, discuss:
+  - Task description and scope
+  - Acceptance criteria
+  - Dependencies on other tasks
+  - Estimated complexity
+- Create tasks in Taskmaster with proper hierarchy and dependencies
+- Link tasks to the parent PRD GitHub issue in task descriptions
+
+### 6. Implementation Planning
+- If no tasks: plan direct implementation approach
+- If tasks exist: discuss which task to start with first using Taskmaster task management
+- Set up todo list for tracking progress
+- Establish success criteria and testing approach
+
+### 7. Begin Work
+- Start implementation (either on full PRD or first Taskmaster task)
+- Use Taskmaster to track task progress and dependencies
+- Use TodoWrite to track implementation progress within tasks
+- Follow test-driven development principles
+- Regular check-ins on progress using Taskmaster status updates
+
+## Implementation Guidelines:
+
+- **Always follow CLAUDE.md instructions** for testing and validation
+- **Write tests first** before implementation
+- **Update documentation** as features are developed
+- **Use Taskmaster** to track task progress and dependencies
+- **Use TodoWrite** to track implementation progress within tasks
+- **Mark Taskmaster tasks as done** when completed
+- **Update GitHub PRD issue** with final implementation status
+- **Commit frequently** with descriptive messages
+
+## Exit Conditions:
+
+- PRD is fully implemented and tested
+- All Taskmaster tasks (if any) are completed and closed
+- GitHub PRD issue is updated with final status
+- Documentation is updated
+- All tests pass
+- Code is committed and pushed
+
+## Notes:
+
+- This workflow ensures structured approach to PRD development
+- Maintains clear communication through GitHub issue tracking for PRDs
+- Uses Taskmaster MCP for hierarchical task management and dependencies
+- Supports both direct implementation and task-based breakdown
+- Follows project quality standards and testing requirements
+- Separates concerns: GitHub for PRD management, Taskmaster for task execution

package/.claude/commands/task-done.md

@@ -0,0 +1,77 @@
+# Task Done - Complete Task Validation and Submission
+
+Validate that the current development task is complete and ready for submission.
+
+## Steps:
+
+1. **Get Current Task**: 
+   - Identify the current task being worked on from user context
+   - If unclear, ask user which task they want to validate as complete
+
+2. **Validate Task Completion**:
+   - Review the task requirements and implementation details
+   - Verify all acceptance criteria are met
+   - Check that implementation matches the task description
+
+3. **Ensure Test Coverage**:
+   - Identify all code files that were modified for this task
+   - Verify that tests exist for all new/modified functionality
+   - Check test file organization matches source code structure
+   - If tests are missing, write them before proceeding
+
+4. **Update All Relevant Documentation**:
+   - **README.md**: CLI commands, workflow examples, installation steps
+   - **docs/API.md**: New interfaces, MCP tools, TypeScript examples
+   - **docs/cli-guide.md**: CLI usage examples and troubleshooting
+   - **docs/mcp-guide.md**: MCP integration and setup procedures
+   - **docs/STAGE_BASED_API.md**: Workflow changes, API updates
+   - **docs/DEVELOPMENT.md**: Architecture updates, new components
+   - **Other docs**: Context, design, next steps as applicable
+   - Never skip documentation updates for new functionality
+
+5. **Run Full Test Suite**:
+   - Execute `npm test` (unit tests) - ALL tests must pass
+   - Execute `npm run test:integration` (integration tests) - ALL tests must pass
+   - If any tests fail, fix them before proceeding
+
+6. **Mark Task Complete**:
+   - Update task status in your project management system
+   - Update any subtasks that are also complete
+
+7. **Commit and Push Changes**:
+   - Run `git status` to see all changes
+   - Run `git diff` to review changes
+   - Create a descriptive commit message referencing the task
+   - Commit all changes with proper message format
+   - Push changes to GitHub
+
+8. **Summary Report**:
+   - Provide summary of what was completed
+   - List files modified, tests added, and documentation updated
+   - Confirm task is marked as done
+   - Confirm changes are pushed to GitHub
+
+## Validation Criteria:
+
+- ✅ Task requirements fully implemented
+- ✅ All new/modified code has test coverage
+- ✅ All relevant documentation updated
+- ✅ All unit tests pass (npm test)
+- ✅ All integration tests pass (npm run test:integration)
+- ✅ Task marked as done
+- ✅ Changes committed and pushed to GitHub
+
+## Exit Conditions:
+
+- If task is not actually complete, provide specific feedback on what needs to be finished
+- If tests are failing, fix the failures before marking task as done
+- If critical functionality is missing tests, write tests before proceeding
+- If documentation is outdated or missing for new functionality, update all relevant docs
+- Never mark a task as done if any validation criteria are not met
+
+## Notes:
+
+- This command ensures comprehensive task completion following CLAUDE.md guidelines
+- Maintains the high quality standards established in the project
+- Follows the test-driven development approach required by the project
+- Ensures proper task tracking and version control practices

package/.claude/commands/tests-reminder.md

@@ -0,0 +1,32 @@
+# Tests Reminder
+
+Remind Claude about testing requirements when making code changes.
+
+## Reminder for Claude
+
+**🔴 BEFORE MARKING ANY TASK/SUBTASK AS COMPLETE:**
+
+□ **Tests Written**: Have you written tests for new functionality?
+□ **All Tests Pass**: Have you run `npm test` to ensure all 562+ tests pass?
+□ **No Test Failures**: Are there any failing tests that need to be fixed?
+
+**❌ TASK IS NOT COMPLETE IF:**
+- Any tests are failing
+- New code lacks test coverage  
+- You haven't run `npm test` to verify
+
+## Required Actions
+
+1. **Write/Update Tests**: For any new functionality or code changes
+2. **Run All Tests**: Execute `npm test` to verify everything passes
+3. **Fix Failures**: Address any test failures before proceeding
+4. **Update CLAUDE.md**: Check if documentation needs updates
+
+## Testing Commands
+
+```bash
+npm test                    # Run all tests (562+ tests across 21 suites)
+npm run build              # Build project
+```
+
+**Remember**: Changes are only considered successful when validated by passing tests!

package/.claude/settings.local.json

@@ -0,0 +1,20 @@
+{
+  "permissions": {
+    "allow": [
+      "WebFetch(domain:modelcontextprotocol.io)",
+      "WebFetch(domain:modelcontextprotocol.io)",
+      "WebFetch(domain:modelcontextprotocol.io)",
+      "Bash(rg:*)",
+      "Bash(npm run build:*)",
+      "Bash(npm test)",
+      "Bash(grep:*)",
+      "Bash(gh repo view:*)",
+      "Bash(gh issue list:*)",
+      "Bash(gh run view:*)"
+    ]
+  },
+  "enableAllProjectMcpServers": true,
+  "enabledMcpjsonServers": [
+    "dot-ai"
+  ]
+}

package/.eslintrc.json

@@ -0,0 +1,25 @@
+{
+  "env": {
+    "browser": true,
+    "es2021": true,
+    "node": true,
+    "jest": true
+  },
+  "extends": [
+    "eslint:recommended"
+  ],
+  "parser": "@typescript-eslint/parser",
+  "parserOptions": {
+    "ecmaVersion": "latest",
+    "sourceType": "module"
+  },
+  "plugins": [
+    "@typescript-eslint"
+  ],
+  "rules": {
+    "no-unused-vars": "off",
+    "@typescript-eslint/no-unused-vars": ["error", { "argsIgnorePattern": "^_" }],
+    "no-console": "warn"
+  },
+  "ignorePatterns": ["dist/", "node_modules/", "coverage/"]
+} 

package/.github/workflows/ci.yml

@@ -0,0 +1,170 @@
+name: CI Pipeline, Security & Publish
+
+on:
+  push:
+    branches: [ main, develop ]
+  pull_request:
+    branches: [ main ]
+  release:
+    types: [ published ]
+
+permissions:
+  actions: read
+  contents: write
+  security-events: write
+  id-token: write
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    
+    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: Create mock kubeconfig for tests
+      run: |
+        cat > kubeconfig.yaml << 'EOF'
+        apiVersion: v1
+        kind: Config
+        clusters:
+        - cluster:
+            server: https://test-cluster.example.com
+          name: test-cluster
+        contexts:
+        - context:
+            cluster: test-cluster
+            user: test-user
+          name: test-context
+        current-context: test-context
+        users:
+        - name: test-user
+          user:
+            token: fake-token
+        EOF
+    
+    - name: Run linter
+      run: npm run lint
+    
+    - name: Build project
+      run: npm run build
+    
+    - name: Run tests
+      run: npm test
+
+  security:
+    name: Security Analysis
+    runs-on: ubuntu-latest
+    
+    steps:
+    - name: Checkout code
+      uses: actions/checkout@v4
+      
+    - name: Initialize CodeQL
+      uses: github/codeql-action/init@v3
+      with:
+        languages: typescript
+        
+    - name: Setup Node.js
+      uses: actions/setup-node@v4
+      with:
+        node-version: '20.x'
+        cache: 'npm'
+        
+    - name: Install dependencies
+      run: npm ci
+      
+    - name: Build project
+      run: npm run build
+      
+    - name: Run dependency security audit
+      run: npm audit --audit-level moderate
+      
+    - name: Perform CodeQL Analysis
+      uses: github/codeql-action/analyze@v3
+
+  publish:
+    needs: [test, security]
+    runs-on: ubuntu-latest
+    if: github.ref == 'refs/heads/main' && github.event_name == 'push'
+    
+    steps:
+    - name: Checkout code
+      uses: actions/checkout@v4
+      with:
+        fetch-depth: 0
+        token: ${{ secrets.GITHUB_TOKEN }}
+    
+    - name: Setup Node.js
+      uses: actions/setup-node@v4
+      with:
+        node-version: '20.x'
+        registry-url: 'https://registry.npmjs.org'
+        cache: 'npm'
+    
+    - name: Install dependencies
+      run: npm ci
+    
+    - name: Build project
+      run: npm run build
+    
+    - name: Auto-increment version and check for changes
+      id: version-check
+      run: |
+        PUBLISHED_VERSION=$(npm view @vfarcic/dot-ai version 2>/dev/null || echo "0.0.0")
+        echo "published-version=$PUBLISHED_VERSION" >> $GITHUB_OUTPUT
+        
+        # Auto-increment minor version
+        npm version minor --no-git-tag-version
+        NEW_VERSION=$(node -p "require('./package.json').version")
+        echo "new-version=$NEW_VERSION" >> $GITHUB_OUTPUT
+        echo "Version incremented from $PUBLISHED_VERSION to $NEW_VERSION"
+        echo "version-changed=true" >> $GITHUB_OUTPUT
+    
+    - name: Publish to npm
+      if: steps.version-check.outputs.version-changed == 'true'
+      run: npm publish --access public
+      env:
+        NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+    
+    - name: Commit version bump and create Git tag
+      if: steps.version-check.outputs.version-changed == 'true'
+      run: |
+        VERSION=${{ steps.version-check.outputs.new-version }}
+        git config --local user.email "action@github.com"
+        git config --local user.name "GitHub Action"
+        git add package.json
+        git commit -m "chore: bump version to $VERSION [skip ci]"
+        git tag -a "v$VERSION" -m "Release version $VERSION"
+        git push origin main
+        git push origin "v$VERSION"
+    
+    - name: Generate release notes
+      if: steps.version-check.outputs.version-changed == 'true'
+      run: |
+        VERSION=$(node -p "require('./package.json').version")
+        echo "# Release v$VERSION" > RELEASE_NOTES.md
+        echo "" >> RELEASE_NOTES.md
+        echo "## Changes" >> RELEASE_NOTES.md
+        git log --oneline $(git describe --tags --abbrev=0 HEAD~1)..HEAD >> RELEASE_NOTES.md 2>/dev/null || echo "Initial release" >> RELEASE_NOTES.md
+    
+    - name: Create GitHub Release
+      if: steps.version-check.outputs.version-changed == 'true'
+      uses: actions/create-release@v1
+      env:
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      with:
+        tag_name: v${{ steps.version-check.outputs.new-version }}
+        release_name: Release v${{ steps.version-check.outputs.new-version }}
+        body_path: RELEASE_NOTES.md
+        draft: false
+        prerelease: false

package/.prettierrc.json

@@ -0,0 +1,10 @@
+{
+  "semi": true,
+  "trailingComma": "es5",
+  "singleQuote": true,
+  "printWidth": 80,
+  "tabWidth": 2,
+  "useTabs": false,
+  "bracketSpacing": true,
+  "arrowParens": "avoid"
+} 

package/.teller.yml

@@ -0,0 +1,8 @@
+providers:
+  google_secrets_manager:
+    kind: google_secretmanager
+    maps:
+      - id: secrets
+        path: projects/vfarcic
+        keys:
+          anthropic-api-key: ANTHROPIC_API_KEY