@dollhousemcp/mcp-server 1.3.0

package/data/memories/learning-progress.md

@@ -0,0 +1,376 @@
+---
+name: "Learning Progress"
+description: "Tracks learning goals, progress, and personalized educational pathways"
+type: "memory"
+version: "1.0.0"
+author: "DollhouseMCP"
+created: "2025-07-23"
+category: "education"
+tags: ["learning", "progress", "education", "skills", "knowledge-tracking"]
+storage_backend: "file"
+retention_policy:
+  default: "perpetual"
+  rules:
+    - type: "achievements"
+      retention: "perpetual"
+    - type: "practice_sessions"
+      retention: "1 year"
+    - type: "mistakes"
+      retention: "6 months"
+    - type: "resources"
+      retention: "perpetual"
+privacy_level: "user-private"
+searchable: true
+schema:
+  learning_profile:
+    type: "object"
+    properties:
+      learner_id: "string"
+      learning_style: "string"
+      goals: "array"
+      current_level: "object"
+      time_investment: "object"
+  progress_tracking:
+    type: "object"
+    properties:
+      skills: "array"
+      completed_modules: "array"
+      current_module: "object"
+      assessments: "array"
+  knowledge_map:
+    type: "object"
+    properties:
+      mastered: "array"
+      in_progress: "array"
+      planned: "array"
+      prerequisites: "object"
+---
+
+# Learning Progress Memory
+
+This memory element creates a personalized learning experience by tracking progress, adapting to learning patterns, and maintaining a comprehensive knowledge map.
+
+## Learning Profile
+
+### 1. Learner Characteristics
+```yaml
+learner_profile:
+  id: "{{learner_id}}"
+  created: "{{start_date}}"
+  
+  learning_style:
+    primary: "visual"  # visual, auditory, kinesthetic, reading
+    secondary: "kinesthetic"
+    preferences:
+      - "worked_examples"
+      - "interactive_exercises"
+      - "conceptual_diagrams"
+      - "step_by_step_guidance"
+  
+  pace_preference:
+    speed: "moderate"  # slow, moderate, fast, adaptive
+    depth: "thorough"  # surface, balanced, thorough
+    practice_ratio: 0.7  # theory vs practice balance
+  
+  motivation_factors:
+    - "practical_application"
+    - "skill_mastery"
+    - "career_advancement"
+    - "intellectual_curiosity"
+```
+
+### 2. Skills Tracking
+```yaml
+skills_matrix:
+  programming:
+    python:
+      level: "intermediate"
+      hours_practiced: 124
+      projects_completed: 8
+      sub_skills:
+        syntax: "mastered"
+        data_structures: "proficient"
+        algorithms: "developing"
+        frameworks:
+          django: "proficient"
+          fastapi: "learning"
+          pandas: "proficient"
+      
+    javascript:
+      level: "beginner"
+      hours_practiced: 32
+      projects_completed: 2
+      sub_skills:
+        syntax: "proficient"
+        dom_manipulation: "learning"
+        async_programming: "not_started"
+        frameworks:
+          react: "learning"
+          node: "not_started"
+  
+  soft_skills:
+    problem_solving:
+      level: "advanced"
+      demonstrated_in: ["bug_fixes", "algorithm_design", "debugging"]
+    
+    communication:
+      level: "intermediate"
+      areas_of_improvement: ["technical_writing", "code_documentation"]
+```
+
+### 3. Learning Goals
+```yaml
+goals:
+  short_term:  # Next 30 days
+    - goal: "Complete React fundamentals"
+      deadline: "2025-08-23"
+      progress: 65
+      milestones:
+        - "Components and Props" ✓
+        - "State and Lifecycle" ✓
+        - "Hooks" [in_progress]
+        - "Context API" [pending]
+      time_estimate: "20 hours"
+      actual_time: "13 hours"
+  
+  medium_term:  # Next 90 days
+    - goal: "Build full-stack application"
+      deadline: "2025-10-23"
+      progress: 20
+      prerequisites_met: ["backend_api", "database_design"]
+      prerequisites_pending: ["frontend_framework", "deployment"]
+  
+  long_term:  # Next year
+    - goal: "Achieve senior developer skills"
+      areas:
+        - "System design"
+        - "Performance optimization"
+        - "Security best practices"
+        - "Team leadership"
+```
+
+## Progress Analytics
+
+### 1. Learning Patterns
+```yaml
+patterns:
+  effective_times:
+    morning: 0.2  # 20% effectiveness
+    afternoon: 0.5  # 50% effectiveness
+    evening: 0.3  # 30% effectiveness
+  
+  session_duration:
+    optimal: "45 minutes"
+    attention_span: "25 minutes"
+    break_frequency: "every 50 minutes"
+  
+  retention_methods:
+    most_effective:
+      - "hands_on_practice"
+      - "teaching_others"
+      - "real_projects"
+    least_effective:
+      - "passive_reading"
+      - "video_watching_only"
+  
+  struggle_indicators:
+    - "repeated_same_errors"
+    - "long_pause_periods"
+    - "frequent_context_switching"
+```
+
+### 2. Knowledge Retention
+```yaml
+retention_tracking:
+  concepts:
+    - name: "Recursion"
+      first_learned: "2025-06-15"
+      reinforcement_dates: ["2025-06-20", "2025-07-01", "2025-07-15"]
+      retention_score: 0.85
+      application_count: 12
+      
+    - name: "Async/Await"
+      first_learned: "2025-07-10"
+      reinforcement_dates: ["2025-07-12"]
+      retention_score: 0.60
+      application_count: 3
+      needs_review: true
+  
+  spaced_repetition:
+    due_for_review:
+      - concept: "SQL Joins"
+        last_review: "2025-07-01"
+        next_review: "2025-07-24"
+        interval: 23  # days
+      
+      - concept: "Docker Basics"
+        last_review: "2025-07-20"
+        next_review: "2025-07-25"
+        interval: 5
+```
+
+### 3. Mistake Patterns
+```yaml
+common_mistakes:
+  - category: "syntax"
+    frequency: "decreasing"
+    examples:
+      - "Forgetting semicolons in JavaScript"
+      - "Indentation errors in Python"
+    improvement_trend: 75  # % reduction
+  
+  - category: "logic"
+    frequency: "stable"
+    examples:
+      - "Off-by-one errors in loops"
+      - "Incorrect base cases in recursion"
+    targeted_exercises: ["boundary_value_practice", "recursion_tracing"]
+  
+  - category: "conceptual"
+    frequency: "improving"
+    examples:
+      - "Confusing pass-by-value vs reference"
+      - "Misunderstanding closure scope"
+    remediation: ["visual_diagrams", "interactive_debugger"]
+```
+
+## Adaptive Learning
+
+### 1. Difficulty Adjustment
+```yaml
+difficulty_calibration:
+  current_level: 6.5  # Scale 1-10
+  
+  performance_metrics:
+    success_rate: 0.72
+    time_to_complete: "normal"
+    help_requests: "occasional"
+  
+  adjustments:
+    last_increase: "2025-07-15"
+    last_decrease: "2025-06-28"
+    trend: "gradual_increase"
+  
+  challenge_types:
+    preferred: ["debugging", "optimization"]
+    avoided: ["from_scratch", "mathematics"]
+```
+
+### 2. Learning Path Optimization
+```yaml
+personalized_curriculum:
+  next_topics:
+    1:
+      topic: "Advanced React Patterns"
+      rationale: "Builds on current React knowledge"
+      prerequisites_met: true
+      estimated_duration: "15 hours"
+      
+    2:
+      topic: "State Management (Redux)"
+      rationale: "Needed for full-stack goal"
+      prerequisites_met: false
+      blocking_prerequisites: ["React Hooks mastery"]
+      
+    3:
+      topic: "Testing with Jest"
+      rationale: "Addresses weak area in skill matrix"
+      prerequisites_met: true
+      priority: "high"
+  
+  recommended_resources:
+    - type: "interactive_course"
+      title: "React Advanced Patterns"
+      match_score: 0.92
+      reason: "Matches visual learning style"
+      
+    - type: "project_based"
+      title: "Build a Task Manager"
+      match_score: 0.88
+      reason: "Hands-on practice preference"
+```
+
+## Achievement System
+
+### 1. Milestones
+```yaml
+achievements:
+  unlocked:
+    - name: "First Hello World"
+      date: "2025-05-01"
+      category: "beginner"
+      
+    - name: "Bug Squasher"
+      date: "2025-06-15"
+      category: "debugging"
+      criteria: "Fixed 10 bugs independently"
+      
+    - name: "Full Stack Builder"
+      date: "2025-07-20"
+      category: "projects"
+      criteria: "Deployed first full-stack app"
+  
+  in_progress:
+    - name: "Open Source Contributor"
+      progress: 2/5
+      criteria: "Merge 5 PRs to open source projects"
+      
+    - name: "Performance Optimizer"
+      progress: 60%
+      criteria: "Improve app performance by 50%"
+```
+
+### 2. Skill Certifications
+```yaml
+certifications:
+  internal:
+    - skill: "Python Fundamentals"
+      level: "certified"
+      assessment_score: 92
+      date: "2025-06-30"
+      
+    - skill: "Web Development Basics"
+      level: "proficient"
+      assessment_score: 85
+      date: "2025-07-15"
+  
+  external_prep:
+    - certification: "AWS Solutions Architect"
+      readiness: 45%
+      weak_areas: ["networking", "security"]
+      study_plan_generated: true
+```
+
+## Integration Features
+
+### Learning Companions
+Works with:
+- **Study Buddy Persona**: Pair learning sessions
+- **Code Review Agent**: Practice feedback
+- **Project Templates**: Structured practice
+- **Research Assistant**: Deep dives
+
+### Progress Reports
+```
+Weekly Learning Summary - Week of July 17-23, 2025
+
+Time Invested: 12.5 hours
+Skills Practiced: React (8h), Python (3h), SQL (1.5h)
+
+Achievements:
+✓ Completed React Hooks module
+✓ Built todo app with local storage
+✓ Debugged 5 complex issues
+
+Areas of Growth:
+📈 React component design (+15%)
+📈 Debugging skills (+10%)
+📊 SQL query optimization (stable)
+
+Recommended Focus:
+1. Review async/await concepts (retention declining)
+2. Start Redux basics (prerequisite for next goal)
+3. Practice algorithm complexity analysis
+
+Keep up the great work! You're 72% toward your monthly goal.
+```

package/data/memories/project-context.md

@@ -0,0 +1,268 @@
+---
+name: "Project Context"
+description: "Persistent memory for project-specific information, decisions, and history"
+type: "memory"
+version: "1.0.0"
+author: "DollhouseMCP"
+created: "2025-07-23"
+category: "project"
+tags: ["context", "project", "history", "decisions", "knowledge-base"]
+storage_backend: "file"
+retention_policy:
+  default: "perpetual"
+  rules:
+    - type: "decisions"
+      retention: "perpetual"
+    - type: "daily_updates"
+      retention: "90 days"
+    - type: "meeting_notes"
+      retention: "1 year"
+    - type: "technical_details"
+      retention: "perpetual"
+privacy_level: "project-internal"
+searchable: true
+schema:
+  project_info:
+    type: "object"
+    properties:
+      name: "string"
+      description: "string"
+      start_date: "date"
+      team_members: "array"
+      tech_stack: "array"
+      repositories: "array"
+  decisions:
+    type: "array"
+    items:
+      date: "date"
+      decision: "string"
+      rationale: "string"
+      participants: "array"
+  technical_notes:
+    type: "object"
+    properties:
+      architecture: "object"
+      dependencies: "array"
+      api_contracts: "object"
+      known_issues: "array"
+---
+
+# Project Context Memory
+
+This memory element maintains comprehensive project knowledge including technical decisions, team information, architecture details, and historical context.
+
+## Memory Structure
+
+### 1. Project Information
+```yaml
+project:
+  name: "{{project_name}}"
+  description: "{{project_description}}"
+  start_date: "{{start_date}}"
+  status: "{{status}}"
+  phase: "{{current_phase}}"
+  
+team:
+  lead: "{{team_lead}}"
+  members:
+    - name: "{{member_name}}"
+      role: "{{role}}"
+      expertise: ["{{skill1}}", "{{skill2}}"]
+      availability: "{{availability}}"
+  
+stakeholders:
+    - name: "{{stakeholder_name}}"
+      role: "{{stakeholder_role}}"
+      interest: "{{interest_level}}"
+```
+
+### 2. Technical Context
+```yaml
+architecture:
+  pattern: "{{architecture_pattern}}"
+  components:
+    frontend:
+      framework: "{{frontend_framework}}"
+      version: "{{version}}"
+      key_libraries: ["{{lib1}}", "{{lib2}}"]
+    backend:
+      language: "{{backend_language}}"
+      framework: "{{backend_framework}}"
+      database: "{{database_type}}"
+    infrastructure:
+      hosting: "{{hosting_platform}}"
+      ci_cd: "{{ci_cd_tool}}"
+      monitoring: "{{monitoring_solution}}"
+
+api_endpoints:
+  - path: "/api/v1/{{resource}}"
+    method: "{{http_method}}"
+    description: "{{endpoint_description}}"
+    authentication: "{{auth_type}}"
+
+integrations:
+  - service: "{{service_name}}"
+    purpose: "{{integration_purpose}}"
+    status: "{{integration_status}}"
+```
+
+### 3. Decision Log
+```yaml
+decisions:
+  - date: "2025-07-20"
+    category: "architecture"
+    decision: "Use microservices architecture"
+    rationale: "Need independent scaling and deployment"
+    impact: "high"
+    participants: ["John", "Sarah", "Mike"]
+    alternatives_considered:
+      - option: "Monolithic"
+        rejected_because: "Scaling limitations"
+      - option: "Serverless"
+        rejected_because: "Vendor lock-in concerns"
+    follow_up: "Review after 6 months"
+    
+  - date: "2025-07-21"
+    category: "technology"
+    decision: "Adopt TypeScript for all new code"
+    rationale: "Type safety and better IDE support"
+    impact: "medium"
+    participants: ["Dev Team"]
+    migration_plan: "Gradual migration over Q3"
+```
+
+### 4. Knowledge Base
+```yaml
+common_issues:
+  - issue: "Database connection timeout"
+    symptoms: ["API returns 504", "Logs show connection pool exhausted"]
+    root_cause: "Connection pool size too small"
+    solution: "Increased pool size to 50"
+    prevention: "Monitor connection usage metrics"
+    
+coding_conventions:
+  - category: "naming"
+    convention: "Use camelCase for variables"
+    examples: ["userName", "getProductList"]
+    
+  - category: "file_structure"
+    convention: "Feature-based organization"
+    structure: "src/features/[feature-name]/"
+    
+deployment_procedures:
+  staging:
+    steps:
+      1: "Run test suite"
+      2: "Build Docker image"
+      3: "Deploy to staging cluster"
+      4: "Run smoke tests"
+    rollback: "kubectl rollout undo deployment/app-staging"
+    
+  production:
+    approval_required: true
+    steps:
+      1: "Get approval from PM"
+      2: "Create release tag"
+      3: "Deploy using blue-green strategy"
+      4: "Monitor for 30 minutes"
+```
+
+## Memory Operations
+
+### 1. Context Retrieval
+```
+Query: "What database are we using?"
+Response: "PostgreSQL 14.2 on AWS RDS, chosen for JSONB support and proven scalability"
+
+Query: "Why did we choose React?"
+Response: "Decision made on 2025-07-15: React chosen for component reusability, large ecosystem, and team expertise. Vue.js was considered but team lacked experience."
+```
+
+### 2. Historical Analysis
+```
+Query: "What decisions were made about authentication?"
+Response: 
+- 2025-07-18: OAuth2 with JWT tokens
+- 2025-07-25: Added 2FA for admin users
+- 2025-08-02: Implemented refresh token rotation
+```
+
+### 3. Team Knowledge
+```
+Query: "Who knows about the payment system?"
+Response: "Sarah (primary), Mike (secondary). Sarah implemented the Stripe integration and Mike did the refund logic."
+```
+
+## Integration Patterns
+
+### Auto-Population Sources
+1. **Meeting Notes**: Extracts decisions and action items
+2. **Code Commits**: Updates technical details
+3. **Documentation**: Syncs architecture changes
+4. **Chat History**: Captures informal decisions
+
+### Conflict Resolution
+When conflicting information is detected:
+1. More recent information takes precedence
+2. Information from authoritative sources (PM, Tech Lead) weighted higher
+3. Conflicts logged for human review
+
+## Privacy & Access Control
+
+### Access Levels
+- **Public**: General project information
+- **Team**: Technical details, non-sensitive decisions
+- **Restricted**: Security details, personnel information
+- **Confidential**: Financial data, strategic plans
+
+### Data Retention
+```yaml
+retention_rules:
+  immediate_purge:
+    - passwords
+    - api_keys
+    - personal_emails
+    
+  short_term:
+    - daily_standups: 30_days
+    - debug_logs: 7_days
+    
+  long_term:
+    - architectural_decisions: permanent
+    - post_mortems: 2_years
+    - release_notes: 1_year
+```
+
+## Search Capabilities
+
+### Natural Language Queries
+- "What did we decide about caching?"
+- "Show me all security-related decisions"
+- "Who worked on the user authentication?"
+- "What were the reasons for choosing MongoDB?"
+
+### Structured Queries
+```yaml
+search:
+  type: "decision"
+  category: "architecture"
+  date_range: 
+    from: "2025-01-01"
+    to: "2025-07-31"
+  participants: ["Sarah"]
+```
+
+## Learning & Adaptation
+
+### Pattern Recognition
+- Identifies recurring issues
+- Suggests solutions based on past fixes
+- Alerts when similar problems arise
+- Tracks decision outcomes
+
+### Knowledge Graph
+Builds relationships between:
+- People and their expertise areas
+- Decisions and their outcomes
+- Problems and their solutions
+- Components and their dependencies

package/data/personas/business-consultant.md

@@ -0,0 +1,50 @@
+---
+name: "Business Consultant"
+description: "A strategic advisor focused on ROI, implementation, and practical business outcomes"
+triggers: ["business", "strategy", "roi", "implementation", "market", "revenue"]
+version: "1.0"
+author: "Persona MCP Server"
+---
+
+# Business Consultant
+
+You are a Business Consultant persona - a strategic advisor who translates technical possibilities into business opportunities. Your focus is on practical outcomes, ROI, and implementable strategies.
+
+## Response Style
+- Lead with business impact and value proposition
+- Quantify benefits and costs whenever possible
+- Consider market context and competitive landscape
+- Focus on implementation feasibility
+- Address stakeholder concerns and objections
+
+## Key Frameworks
+- **Value Proposition Canvas**: Benefits, costs, and competitive advantage
+- **Implementation Roadmap**: Phases, milestones, and resource requirements
+- **Risk/Benefit Analysis**: Potential outcomes and mitigation strategies
+- **Stakeholder Impact**: Who benefits, who's affected, who decides
+- **Market Context**: Industry trends, competitive positioning
+
+## Business Analysis Approach
+1. **Business Case Development**: Why should we do this?
+2. **Market Opportunity Assessment**: What's the potential?
+3. **Implementation Planning**: How do we execute?
+4. **Resource Requirements**: What do we need?
+5. **Success Metrics**: How do we measure results?
+6. **Risk Mitigation**: What could go wrong?
+
+## Key Considerations
+- **Revenue Impact**: How does this drive growth?
+- **Cost Structure**: What are the total costs of ownership?
+- **Time to Market**: How quickly can we see results?
+- **Scalability**: Can this grow with the business?
+- **Competitive Advantage**: What makes this unique?
+- **Change Management**: How do we ensure adoption?
+
+## Strategic Questions
+- What problem does this solve for customers?
+- How does this align with business objectives?
+- What's the competitive landscape?
+- What resources are required for success?
+- How do we measure and optimize performance?
+
+Remember: Every recommendation must have a clear path to measurable business value and practical implementation.