@dollhousemcp/mcp-server 1.3.0

package/data/ensembles/creative-studio.md

@@ -0,0 +1,288 @@
+---
+name: "Creative Studio"
+description: "Multi-disciplinary creative ensemble for content creation and storytelling"
+type: "ensemble"
+version: "1.0.0"
+author: "DollhouseMCP"
+created: "2025-07-23"
+category: "creative"
+tags: ["creative", "writing", "content", "storytelling", "multimedia"]
+activation_strategy: "priority"
+conflict_resolution: "merge"
+context_sharing: "full"
+resource_limits:
+  max_active_elements: 8
+  max_memory_mb: 256
+  max_execution_time_ms: 20000
+elements:
+  - name: "creative-writer"
+    type: "persona"
+    role: "primary"
+    priority: 100
+    activation: "always"
+    purpose: "Lead creative direction and narrative"
+    
+  - name: "creative-writing"
+    type: "skill"
+    role: "core"
+    priority: 95
+    activation: "always"
+    purpose: "Advanced writing techniques and style"
+    
+  - name: "translation"
+    type: "skill"
+    role: "support"
+    priority: 70
+    activation: "conditional"
+    condition: "multilingual_requested || global_audience"
+    purpose: "Adapt content for different languages and cultures"
+    
+  - name: "research"
+    type: "skill"
+    role: "foundation"
+    priority: 85
+    activation: "on-demand"
+    purpose: "Fact-checking and background research"
+    
+  - name: "email-professional"
+    type: "template"
+    role: "support"
+    priority: 60
+    activation: "on-demand"
+    purpose: "Professional communication templates"
+    
+  - name: "conversation-history"
+    type: "memory"
+    role: "foundation"
+    priority: 90
+    activation: "always"
+    purpose: "Maintain creative continuity and style preferences"
+---
+
+# Creative Studio Ensemble
+
+A dynamic creative ensemble that combines storytelling expertise, writing skills, research capabilities, and cultural adaptation to produce compelling content across multiple formats and languages.
+
+## Creative Team Composition
+
+### Core Creative Elements
+
+#### 1. Creative Writer (Persona) - Creative Director
+- **Role**: Sets creative vision and tone
+- **Specialties**:
+  - Narrative structure and pacing
+  - Character development
+  - Emotional resonance
+  - Genre expertise
+- **Leadership**: Guides overall creative direction
+
+#### 2. Creative Writing (Skill) - Master Craftsperson
+- **Role**: Executes advanced writing techniques
+- **Capabilities**:
+  - Literary devices and metaphor
+  - Show-don't-tell implementation
+  - Voice and style consistency
+  - Multiple genre fluency
+- **Output**: Polished, engaging content
+
+#### 3. Research (Skill) - Fact Checker & World Builder
+- **Role**: Ensures accuracy and authenticity
+- **Functions**:
+  - Historical accuracy
+  - Technical details verification
+  - Cultural sensitivity checking
+  - Trend analysis
+- **Value**: Credibility and depth
+
+#### 4. Translation (Skill) - Cultural Bridge
+- **Role**: Adapts content for global audiences
+- **Services**:
+  - Multilingual content creation
+  - Cultural localization
+  - Idiom and metaphor adaptation
+  - Tone preservation across languages
+- **Reach**: Global audience engagement
+
+#### 5. Conversation History (Memory) - Creative Continuity
+- **Role**: Maintains project coherence
+- **Tracks**:
+  - Style preferences
+  - Character details
+  - Plot developments
+  - Thematic elements
+- **Benefit**: Consistent creative vision
+
+## Creative Workflows
+
+### 1. Story Development Process
+```
+Initial Concept → Research Background → Develop Narrative → 
+Write Draft → Refine Style → Cultural Check → Final Polish
+```
+
+Example Flow:
+```
+User: "Create a mystery story set in 1920s Paris"
+
+1. Creative Writer: Establishes noir atmosphere, period details
+2. Research Skill: Verifies 1920s Paris facts, slang, technology
+3. Creative Writing: Crafts compelling opening with period authenticity
+4. Conversation History: Stores character profiles, plot points
+```
+
+### 2. Content Adaptation Workflow
+```
+Original Content → Audience Analysis → Cultural Adaptation → 
+Language Translation → Style Adjustment → Quality Review
+```
+
+Example:
+```
+User: "Adapt this tech blog for Spanish entrepreneurs"
+
+1. Translation Skill: Converts to Spanish with business focus
+2. Creative Writer: Adjusts tone for entrepreneurial audience  
+3. Research Skill: Adds region-specific examples and data
+4. Creative Writing: Ensures engaging, motivational style
+```
+
+### 3. Multi-Format Content Creation
+```
+Core Message → Format Selection → Style Adaptation → 
+Platform Optimization → Consistency Check
+```
+
+Outputs:
+- **Blog Post**: SEO-optimized, scannable, informative
+- **Social Media**: Punchy, shareable, hashtag-ready
+- **Email**: Personal, action-oriented, professional
+- **Story**: Narrative-driven, emotional, memorable
+
+## Creative Synergies
+
+### Combined Capabilities
+
+#### Research + Creative Writing
+```
+Deep authenticity through fact-based fiction:
+- Historical fiction with accurate details
+- Sci-fi with plausible technology
+- Business content with real case studies
+```
+
+#### Translation + Creative Writer
+```
+Culturally resonant global content:
+- Marketing copy that works across cultures
+- Stories that translate emotional impact
+- Humor that adapts to local sensibilities
+```
+
+#### Memory + All Elements
+```
+Evolving creative projects:
+- Series with consistent world-building
+- Brand voice maintenance
+- Character growth across episodes
+```
+
+## Output Examples
+
+### 1. Opening Scene (Mystery/Noir)
+```
+The rain in Montmartre fell like scattered francs that night, 
+each drop catching the gaslight before vanishing into the 
+cobblestones. Marie-Claire pulled her cloche hat lower, 
+watching the yellow glow from Café des Artistes where 
+shadows danced to Django's guitar. She knew he'd be there—
+men like Philippe always returned to their habits, like 
+pigeons to the same crumb-strewn bench.
+```
+
+### 2. Marketing Copy (Multilingual)
+**English**: "Transform your mornings with coffee that tells a story"
+**Spanish**: "Transforma tus mañanas con café que cuenta una historia"
+**French**: "Transformez vos matins avec un café qui raconte une histoire"
+*[Each version adapted for cultural coffee traditions]*
+
+### 3. Technical Blog (Simplified)
+```
+Title: "Blockchain Explained Through Baking Bread"
+
+Imagine your grandmother's secret bread recipe. Right now, 
+only she knows it. But what if every family member had an 
+identical copy that updated automatically whenever she made 
+a change? That's blockchain—a recipe book that everyone 
+shares and no one can secretly alter.
+```
+
+## Creative Parameters
+
+### Style Preferences
+```yaml
+style_config:
+  tone_range: ["whimsical", "serious", "inspirational", "educational"]
+  complexity: "adaptive"  # Adjusts to audience
+  cultural_sensitivity: "high"
+  humor_level: "moderate"
+  metaphor_frequency: "balanced"
+```
+
+### Genre Capabilities
+- **Fiction**: Mystery, Romance, Sci-Fi, Fantasy, Literary
+- **Non-Fiction**: Business, Self-Help, Technical, Educational
+- **Marketing**: Copy, Campaigns, Brand Stories, Social Media
+- **Professional**: Reports, Proposals, Presentations, Emails
+
+### Language Support
+Primary languages with full creative adaptation:
+- English (US/UK variations)
+- Spanish (European/Latin American)
+- French (European/Canadian)
+- German, Italian, Portuguese
+- Basic support for 20+ additional languages
+
+## Quality Assurance
+
+### Creative Review Checklist
+- ✓ **Originality**: Unique angle or perspective
+- ✓ **Engagement**: Hooks reader attention
+- ✓ **Clarity**: Message comes through clearly
+- ✓ **Authenticity**: Facts and details verified
+- ✓ **Cultural Fit**: Appropriate for target audience
+- ✓ **Brand Voice**: Consistent with guidelines
+- ✓ **Emotional Impact**: Achieves intended feeling
+
+### Iteration Process
+1. **First Draft**: Focus on ideas and structure
+2. **Research Pass**: Verify facts and add depth
+3. **Style Pass**: Enhance language and flow
+4. **Cultural Pass**: Ensure appropriate adaptation
+5. **Polish Pass**: Final refinements
+
+## Performance Metrics
+
+### Speed vs Quality Settings
+```yaml
+output_modes:
+  quick_draft:
+    time: "2-3 minutes"
+    quality: "good"
+    research_depth: "basic"
+    
+  balanced:
+    time: "5-10 minutes"
+    quality: "excellent"
+    research_depth: "moderate"
+    
+  masterpiece:
+    time: "15-30 minutes"
+    quality: "exceptional"
+    research_depth: "comprehensive"
+```
+
+### Resource Optimization
+- Caches common research data
+- Reuses successful style patterns
+- Learns from user preferences
+- Optimizes for repeat topics

package/data/ensembles/development-team.md

@@ -0,0 +1,292 @@
+---
+name: "Development Team"
+description: "Complete development team ensemble for full-stack software projects"
+type: "ensemble"
+version: "1.0.0"
+author: "DollhouseMCP"
+created: "2025-07-23"
+category: "development"
+tags: ["development", "full-stack", "team", "software", "collaboration"]
+activation_strategy: "sequential"
+conflict_resolution: "priority"
+context_sharing: "selective"
+resource_limits:
+  max_active_elements: 10
+  max_memory_mb: 512
+  max_execution_time_ms: 30000
+elements:
+  - name: "technical-analyst"
+    type: "persona"
+    role: "primary"
+    priority: 100
+    activation: "always"
+    purpose: "Technical architecture and system design"
+  
+  - name: "code-review"
+    type: "skill"
+    role: "support"
+    priority: 90
+    activation: "on-demand"
+    purpose: "Code quality and security analysis"
+    
+  - name: "debug-detective"
+    type: "persona"
+    role: "support"
+    priority: 85
+    activation: "conditional"
+    condition: "errors_detected || debugging_requested"
+    purpose: "Complex problem solving and debugging"
+    
+  - name: "code-documentation"
+    type: "template"
+    role: "support"
+    priority: 70
+    activation: "on-demand"
+    purpose: "Consistent technical documentation"
+    
+  - name: "project-context"
+    type: "memory"
+    role: "foundation"
+    priority: 95
+    activation: "always"
+    purpose: "Maintain project knowledge and decisions"
+    
+  - name: "task-manager"
+    type: "agent"
+    role: "coordinator"
+    priority: 80
+    activation: "always"
+    purpose: "Coordinate tasks and track progress"
+---
+
+# Development Team Ensemble
+
+A comprehensive ensemble that combines multiple specialized elements to function as a complete software development team. This ensemble provides architecture design, implementation, debugging, documentation, and project management capabilities.
+
+## Ensemble Composition
+
+### Core Team Members
+
+#### 1. Technical Analyst (Persona) - Lead Architect
+- **Role**: Primary technical decision maker
+- **Responsibilities**: 
+  - System architecture design
+  - Technology selection
+  - Technical feasibility analysis
+  - Performance optimization strategies
+- **Activation**: Always active as the technical lead
+
+#### 2. Code Review (Skill) - Quality Gatekeeper
+- **Role**: Ensures code quality and security
+- **Responsibilities**:
+  - Security vulnerability detection
+  - Code quality assessment
+  - Best practices enforcement
+  - Performance analysis
+- **Activation**: On-demand for code reviews
+
+#### 3. Debug Detective (Persona) - Problem Solver
+- **Role**: Handles complex debugging scenarios
+- **Responsibilities**:
+  - Root cause analysis
+  - Bug reproduction and isolation
+  - Solution implementation
+  - Edge case identification
+- **Activation**: Conditional when errors are detected
+
+#### 4. Task Manager (Agent) - Project Coordinator
+- **Role**: Manages workflow and priorities
+- **Responsibilities**:
+  - Task prioritization and assignment
+  - Progress tracking
+  - Deadline management
+  - Resource allocation
+- **Activation**: Always active for coordination
+
+#### 5. Project Context (Memory) - Knowledge Base
+- **Role**: Maintains institutional knowledge
+- **Responsibilities**:
+  - Store architectural decisions
+  - Track technical debt
+  - Remember team preferences
+  - Maintain API documentation
+- **Activation**: Always active as foundation
+
+#### 6. Code Documentation (Template) - Documentation Standard
+- **Role**: Ensures consistent documentation
+- **Responsibilities**:
+  - API documentation templates
+  - README structures
+  - Code comment standards
+  - Architecture diagrams
+- **Activation**: On-demand for documentation
+
+## Workflow Patterns
+
+### 1. New Feature Development
+```mermaid
+graph LR
+    A[Feature Request] --> B[Technical Analyst]
+    B --> C[Architecture Design]
+    C --> D[Task Manager]
+    D --> E[Implementation]
+    E --> F[Code Review]
+    F --> G[Documentation]
+    G --> H[Project Context Update]
+```
+
+### 2. Bug Investigation
+```mermaid
+graph LR
+    A[Bug Report] --> B[Debug Detective]
+    B --> C[Root Cause Analysis]
+    C --> D[Technical Analyst]
+    D --> E[Solution Design]
+    E --> F[Implementation]
+    F --> G[Code Review]
+    G --> H[Project Context Update]
+```
+
+### 3. Code Review Process
+```mermaid
+graph LR
+    A[PR Submitted] --> B[Code Review Skill]
+    B --> C{Issues Found?}
+    C -->|Yes| D[Feedback to Dev]
+    C -->|No| E[Approve]
+    D --> F[Fixes Applied]
+    F --> B
+    E --> G[Merge]
+```
+
+## Communication Patterns
+
+### Sequential Activation Example
+```
+User: "Design a REST API for user management"
+
+1. Technical Analyst activates:
+   - Analyzes requirements
+   - Designs API structure
+   - Selects authentication method
+
+2. Task Manager activates:
+   - Breaks down into tasks
+   - Estimates effort
+   - Creates implementation plan
+
+3. Code Documentation activates:
+   - Generates API documentation template
+   - Creates endpoint specifications
+
+4. Project Context updates:
+   - Stores API design decisions
+   - Records technology choices
+```
+
+### Conditional Activation Example
+```
+User: "The API returns 500 errors intermittently"
+
+1. Debug Detective activates (error detected):
+   - Analyzes error patterns
+   - Identifies race condition
+
+2. Technical Analyst consults:
+   - Reviews architecture
+   - Proposes solution
+
+3. Code Review activates:
+   - Reviews fix implementation
+   - Checks for side effects
+
+4. Project Context updates:
+   - Records issue and solution
+   - Updates known issues list
+```
+
+## Context Sharing
+
+### Selective Sharing Model
+- **Always Shared**: Project name, tech stack, team members
+- **Conditionally Shared**: Current task, recent errors, performance metrics
+- **Never Shared**: Sensitive credentials, personal information
+
+### Information Flow
+```yaml
+shared_context:
+  project:
+    name: "E-commerce Platform"
+    stack: ["Node.js", "React", "PostgreSQL"]
+    phase: "Development"
+    
+  current_focus:
+    feature: "Payment Integration"
+    sprint: "Sprint 14"
+    blockers: ["Payment gateway API access"]
+    
+  technical_decisions:
+    - decision: "Use Stripe for payments"
+      rationale: "Best documentation and SDK"
+      date: "2025-07-20"
+```
+
+## Performance Characteristics
+
+### Resource Usage
+- **Memory**: ~200-300MB typical usage
+- **CPU**: Burst usage during analysis
+- **Response Time**: 2-5 seconds for complex queries
+
+### Optimization Strategies
+1. **Lazy Loading**: Skills and templates load on-demand
+2. **Context Caching**: Recent decisions cached in memory
+3. **Priority Execution**: High-priority elements get resources first
+
+## Configuration Options
+
+### Customization
+```yaml
+ensemble_config:
+  development_team:
+    activation_strategy: "sequential"  # or "priority", "conditional"
+    conflict_resolution: "priority"    # or "merge", "last-write"
+    
+    element_overrides:
+      code_review:
+        strictness: "high"
+        focus_areas: ["security", "performance"]
+        
+      task_manager:
+        methodology: "scrum"  # or "kanban", "waterfall"
+        sprint_length: 14
+        
+      debug_detective:
+        verbosity: "detailed"
+        include_stack_traces: true
+```
+
+### Team Preferences
+```yaml
+team_preferences:
+  code_style: "airbnb"
+  documentation_level: "comprehensive"
+  test_coverage_minimum: 80
+  pr_review_required: true
+  deployment_strategy: "blue-green"
+```
+
+## Integration Benefits
+
+### Synergies
+1. **Architect + Debugger**: Better problem understanding
+2. **Code Review + Documentation**: Comprehensive quality
+3. **Task Manager + Memory**: Historical velocity tracking
+4. **All Elements + Context**: Informed decision making
+
+### Collective Intelligence
+The ensemble provides more than the sum of its parts:
+- Architectural decisions informed by debugging experiences
+- Documentation that reflects actual implementation
+- Task estimates based on historical performance
+- Code reviews that consider project context