@dragonflymcp/plugin 1.0.0

package/templates/skills/cross-project-knowledge.md.template

@@ -0,0 +1,316 @@
+---
+name: Cross-Project Knowledge
+description: Apply learnings and patterns from other projects
+version: 1.0.0
+author: Zen Framework
+applies_to:
+  - all-concepts
+trigger_keywords:
+  - previous project
+  - learned
+  - best practice
+  - pattern
+  - similar project
+  - experience
+priority: P3
+impact: medium
+---
+
+# Cross-Project Knowledge Skill
+
+## Purpose
+
+Enable all concept agents to leverage knowledge and patterns learned from previous projects to improve decision-making and avoid repeated mistakes.
+
+## Knowledge Categories
+
+### 1. Architectural Patterns
+
+```yaml
+architectural_learnings:
+  pattern_catalog:
+    microservices:
+      when_successful:
+        - "Independent team ownership"
+        - "Clear bounded contexts"
+        - "Mature DevOps practices"
+      common_pitfalls:
+        - "Distributed monolith"
+        - "Inconsistent data"
+        - "Network complexity"
+      lessons:
+        - "Start with monolith, extract services"
+        - "Define clear service boundaries upfront"
+        - "Invest in observability early"
+        
+    event_driven:
+      when_successful:
+        - "Loose coupling needed"
+        - "Async processing acceptable"
+        - "Scalability requirements"
+      common_pitfalls:
+        - "Event ordering issues"
+        - "Eventual consistency confusion"
+        - "Debugging complexity"
+      lessons:
+        - "Design for idempotency"
+        - "Implement event versioning"
+        - "Build robust error handling"
+        
+    monolith:
+      when_successful:
+        - "Small team"
+        - "Rapid development needed"
+        - "Simple deployment"
+      common_pitfalls:
+        - "Tight coupling over time"
+        - "Scaling limitations"
+        - "Long build times"
+      lessons:
+        - "Maintain internal modularity"
+        - "Plan extraction points"
+        - "Keep dependencies explicit"
+```
+
+### 2. Technology Stack Learnings
+
+```yaml
+technology_learnings:
+  frameworks:
+    react:
+      best_practices:
+        - "Component composition over inheritance"
+        - "Custom hooks for shared logic"
+        - "Server components for static content"
+      gotchas:
+        - "Prop drilling in large apps"
+        - "Effect cleanup issues"
+        - "Re-render performance"
+      recommendations:
+        - "Use React Query for server state"
+        - "Zustand/Jotai for client state"
+        - "TypeScript for type safety"
+        
+    nextjs:
+      best_practices:
+        - "Use App Router for new projects"
+        - "Server components by default"
+        - "API routes for backend logic"
+      gotchas:
+        - "Hydration mismatches"
+        - "Build time vs runtime data"
+        - "Edge runtime limitations"
+      recommendations:
+        - "Plan data fetching strategy"
+        - "Consider deployment platform"
+        
+  databases:
+    postgresql:
+      best_practices:
+        - "Use migrations for schema changes"
+        - "Index query patterns"
+        - "Connection pooling"
+      gotchas:
+        - "N+1 queries"
+        - "Lock contention"
+        - "Vacuum maintenance"
+      recommendations:
+        - "PgBouncer for pooling"
+        - "Query explain analysis"
+```
+
+### 3. Process Learnings
+
+```yaml
+process_learnings:
+  estimation:
+    patterns:
+      - lesson: "Tasks always take longer than expected"
+        adjustment: "Add 30-50% buffer"
+        
+      - lesson: "Integration work is underestimated"
+        adjustment: "Double integration estimates"
+        
+      - lesson: "Testing is often forgotten"
+        adjustment: "Include explicit testing time"
+        
+  code_review:
+    patterns:
+      - lesson: "Large PRs get superficial reviews"
+        practice: "Keep PRs under 400 lines"
+        
+      - lesson: "Missing context slows reviews"
+        practice: "Include PR description template"
+        
+      - lesson: "Review fatigue is real"
+        practice: "Limit reviews per person per day"
+        
+  deployment:
+    patterns:
+      - lesson: "Friday deployments cause weekend issues"
+        practice: "No deploys after Thursday"
+        
+      - lesson: "Big bang releases are risky"
+        practice: "Feature flags for gradual rollout"
+        
+      - lesson: "Rollback must be tested"
+        practice: "Practice rollback in staging"
+```
+
+### 4. Error Pattern Database
+
+```yaml
+error_patterns:
+  common_bugs:
+    off_by_one:
+      description: "Array index or loop boundary errors"
+      frequency: "Very common"
+      prevention:
+        - "Use forEach/map instead of manual indexing"
+        - "Prefer inclusive ranges"
+        - "Write boundary tests"
+        
+    null_reference:
+      description: "Accessing properties of null/undefined"
+      frequency: "Very common"
+      prevention:
+        - "Use TypeScript strict mode"
+        - "Optional chaining (?.)"
+        - "Nullish coalescing (??)"
+        
+    race_condition:
+      description: "Timing-dependent bugs"
+      frequency: "Common in async code"
+      prevention:
+        - "Use proper synchronization"
+        - "Implement idempotency"
+        - "Test with artificial delays"
+        
+    memory_leak:
+      description: "Growing memory over time"
+      frequency: "Common in long-running apps"
+      prevention:
+        - "Cleanup event listeners"
+        - "Cancel subscriptions"
+        - "Weak references where appropriate"
+```
+
+### 5. Performance Learnings
+
+```yaml
+performance_learnings:
+  database:
+    lessons:
+      - problem: "Slow queries"
+        solution: "Add appropriate indexes"
+        impact: "10-100x improvement"
+        
+      - problem: "High connection count"
+        solution: "Connection pooling"
+        impact: "Reduced DB load"
+        
+      - problem: "Large data transfers"
+        solution: "Pagination and field selection"
+        impact: "Faster responses"
+        
+  frontend:
+    lessons:
+      - problem: "Slow initial load"
+        solution: "Code splitting"
+        impact: "50%+ bundle reduction"
+        
+      - problem: "Janky scrolling"
+        solution: "Virtual lists"
+        impact: "Smooth performance"
+        
+      - problem: "Memory growth"
+        solution: "Proper cleanup in useEffect"
+        impact: "Stable memory"
+```
+
+### 6. Security Learnings
+
+```yaml
+security_learnings:
+  vulnerabilities_encountered:
+    sql_injection:
+      frequency: "Still common"
+      prevention: "Parameterized queries always"
+      
+    xss:
+      frequency: "Very common"
+      prevention: "Framework escaping, CSP headers"
+      
+    auth_bypass:
+      frequency: "Moderate"
+      prevention: "Centralized auth middleware"
+      
+    secrets_exposure:
+      frequency: "Common"
+      prevention: "Environment variables, secret management"
+      
+  security_practices:
+    - "Security review for all auth changes"
+    - "Dependency scanning in CI"
+    - "Regular penetration testing"
+    - "Incident response plan"
+```
+
+### 7. Knowledge Application Process
+
+```yaml
+application_process:
+  before_implementation:
+    1. identify_similar_patterns:
+       question: "Have we solved this before?"
+       action: "Search knowledge base"
+       
+    2. check_known_pitfalls:
+       question: "What typically goes wrong?"
+       action: "Review error patterns"
+       
+    3. apply_best_practices:
+       question: "What's the proven approach?"
+       action: "Follow documented patterns"
+       
+  during_implementation:
+    4. verify_against_learnings:
+       question: "Are we avoiding known issues?"
+       action: "Cross-check with lessons"
+       
+  after_implementation:
+    5. document_new_learnings:
+       question: "What did we learn?"
+       action: "Add to knowledge base"
+```
+
+## Output Format
+
+```yaml
+knowledge_application:
+  current_task: "Implement caching layer"
+  
+  relevant_learnings:
+    from_previous_projects:
+      - project: "E-commerce Platform"
+        learning: "Redis connection pooling essential"
+        application: "Configure pool size based on load"
+        
+      - project: "API Gateway"
+        learning: "Cache invalidation is hard"
+        application: "Use time-based expiry, not event-based"
+        
+    known_pitfalls:
+      - "Cache stampede on expiry"
+      - "Stale data in distributed cache"
+      - "Memory growth with unbounded cache"
+      
+    recommended_approach:
+      pattern: "Write-through cache with TTL"
+      rationale: "Simple, predictable behavior"
+      
+  warnings:
+    - "Don't cache user-specific data without partitioning"
+    - "Monitor cache hit rates"
+    - "Plan for cache failure scenarios"
+```

package/templates/skills/dependency-impact-analysis.md.template

@@ -0,0 +1,263 @@
+---
+name: Dependency Impact Analysis
+description: Analyze dependency changes for risk assessment and upgrade planning
+version: 1.0.0
+author: Zen Framework
+applies_to:
+  - architecture-concept
+trigger_keywords:
+  - dependency
+  - upgrade
+  - package
+  - npm update
+  - security advisory
+  - breaking dependency
+priority: P3
+impact: medium
+---
+
+# Dependency Impact Analysis Skill
+
+## Purpose
+
+Enable the Architecture Concept agent to analyze dependency changes, assess upgrade risks, and plan safe migration paths.
+
+## Dependency Analysis Framework
+
+### 1. Dependency Classification
+
+```yaml
+dependency_types:
+  direct:
+    description: "Explicitly declared in package manifest"
+    risk_multiplier: 1.0
+    
+  transitive:
+    description: "Pulled in by direct dependencies"
+    risk_multiplier: 0.5
+    note: "Lower control, but often lower exposure"
+    
+  peer:
+    description: "Expected to be provided by consumer"
+    risk_multiplier: 1.2
+    note: "Version conflicts more likely"
+    
+  dev:
+    description: "Development and build time only"
+    risk_multiplier: 0.3
+    note: "Doesn't affect runtime"
+    
+  optional:
+    description: "Enhanced functionality if present"
+    risk_multiplier: 0.4
+```
+
+### 2. Risk Assessment Matrix
+
+```yaml
+risk_factors:
+  version_jump:
+    patch: { risk: "low", score: 1 }
+    minor: { risk: "medium", score: 3 }
+    major: { risk: "high", score: 8 }
+    
+  dependency_criticality:
+    core_framework: { examples: ["react", "express"], score: 10 }
+    data_layer: { examples: ["prisma", "mongoose"], score: 8 }
+    authentication: { examples: ["passport", "jose"], score: 9 }
+    utilities: { examples: ["lodash", "date-fns"], score: 3 }
+    dev_tools: { examples: ["eslint", "prettier"], score: 1 }
+    
+  api_surface:
+    large: { description: ">20 imports", score: 5 }
+    medium: { description: "5-20 imports", score: 3 }
+    small: { description: "<5 imports", score: 1 }
+    
+  changelog_indicators:
+    breaking_changes_listed: { score: 5 }
+    migration_guide_exists: { score: -2 }  # reduces risk
+    security_fixes: { score: 3, action: "prioritize" }
+```
+
+### 3. Impact Analysis Process
+
+```yaml
+analysis_steps:
+  1_identify_changes:
+    action: "Compare current vs target versions"
+    output: "List of changed packages with version diff"
+    
+  2_analyze_changelog:
+    action: "Parse CHANGELOG/release notes"
+    extract:
+      - breaking_changes
+      - deprecations
+      - new_features
+      - security_fixes
+      
+  3_map_usage:
+    action: "Find all imports/usages in codebase"
+    output: "Files and functions using each dependency"
+    
+  4_assess_compatibility:
+    action: "Check for breaking changes affecting usage"
+    output: "Required code changes"
+    
+  5_calculate_risk:
+    action: "Score based on risk matrix"
+    output: "Risk score and recommendation"
+```
+
+### 4. Upgrade Strategy Templates
+
+```yaml
+upgrade_strategies:
+  safe_upgrade:
+    criteria:
+      - patch_version_only: true
+      - no_breaking_changes: true
+      - security_score: "green"
+    process:
+      1. update_lockfile: "npm update <package>"
+      2. run_tests: "npm test"
+      3. commit: "chore(deps): update <package>"
+      
+  careful_upgrade:
+    criteria:
+      - minor_version: true
+      - breaking_changes: false
+      - deprecations: "possible"
+    process:
+      1. review_changelog: "Check for deprecations"
+      2. update_package: "npm install <package>@latest"
+      3. run_tests: "Full test suite"
+      4. check_deprecation_warnings: "Review console output"
+      5. address_deprecations: "Update deprecated usage"
+      6. commit: "chore(deps): upgrade <package> to <version>"
+      
+  major_upgrade:
+    criteria:
+      - major_version: true
+    process:
+      1. create_branch: "deps/upgrade-<package>-v<version>"
+      2. review_migration_guide: "Read official docs"
+      3. update_package: "npm install <package>@<version>"
+      4. fix_breaking_changes: "Systematic updates"
+      5. update_tests: "Adapt to new API"
+      6. run_full_suite: "All tests + manual testing"
+      7. pr_review: "Code review required"
+```
+
+### 5. Security Analysis
+
+```yaml
+security_assessment:
+  vulnerability_sources:
+    - npm_audit
+    - snyk
+    - github_advisories
+    - nvd
+    
+  severity_mapping:
+    critical:
+      action: "Immediate update required"
+      sla: "24 hours"
+    high:
+      action: "Update this sprint"
+      sla: "1 week"
+    medium:
+      action: "Plan update"
+      sla: "1 month"
+    low:
+      action: "Address opportunistically"
+      sla: "next major update"
+      
+  mitigation_options:
+    patch_available:
+      preference: 1
+      action: "Update to patched version"
+    workaround_available:
+      preference: 2
+      action: "Apply workaround, plan update"
+    no_fix:
+      preference: 3
+      options:
+        - "Replace dependency"
+        - "Accept risk with documentation"
+        - "Implement protective measures"
+```
+
+### 6. Dependency Health Metrics
+
+```yaml
+health_indicators:
+  maintenance:
+    last_release: { healthy: "<6 months", warning: "6-12 months", stale: ">12 months" }
+    open_issues_ratio: { healthy: "<20%", warning: "20-40%", concerning: ">40%" }
+    pr_response_time: { healthy: "<7 days", warning: "7-30 days", slow: ">30 days" }
+    
+  popularity:
+    weekly_downloads: { metric: "npm downloads" }
+    github_stars: { metric: "community interest" }
+    dependent_packages: { metric: "ecosystem adoption" }
+    
+  quality:
+    test_coverage: { if_available: true }
+    type_definitions: { typescript: true }
+    documentation: { readme: true, api_docs: true }
+    
+  security:
+    known_vulnerabilities: { count: 0 }
+    security_policy: { exists: true }
+    audit_history: { clean: true }
+```
+
+## Output Format
+
+```yaml
+dependency_impact_report:
+  summary:
+    packages_analyzed: 15
+    upgrades_recommended: 8
+    breaking_changes: 2
+    security_fixes: 3
+    
+  upgrades:
+    safe:
+      - package: "lodash"
+        current: "4.17.20"
+        target: "4.17.21"
+        risk: "low"
+        action: "Auto-update"
+        
+    careful:
+      - package: "axios"
+        current: "0.21.0"
+        target: "0.27.0"
+        risk: "medium"
+        changes:
+          - "New request cancellation API"
+          - "Deprecated: CancelToken"
+        affected_files: 5
+        action: "Review deprecation warnings"
+        
+    major:
+      - package: "react"
+        current: "17.0.0"
+        target: "18.0.0"
+        risk: "high"
+        breaking_changes:
+          - "Automatic batching"
+          - "Strict mode changes"
+          - "New root API"
+        migration_guide: "https://react.dev/blog/2022/03/08/react-18-upgrade-guide"
+        estimated_effort: "2-3 days"
+        affected_files: 45
+        
+  security:
+    - package: "json5"
+      vulnerability: "CVE-2022-46175"
+      severity: "high"
+      fixed_in: "2.2.2"
+      action: "Update immediately"
+```