Global-first principle: Long-term vision

## Overview
This issue captures the long-term vision for fully implementing the global-first configuration principle established in #793.

## Long-term Vision

### 1. All AI assistant configurations globally available
- [ ] Create unified AI configuration system that works across all assistants
- [ ] Implement provider-agnostic configuration format
- [ ] Ensure Claude, Amazon Q, Cursor, etc. all share global configs
- [ ] Build translation layers for provider-specific requirements

### 2. System-wide MCP server installations
- [ ] Design global MCP server registry
- [ ] Implement system service management for MCP servers
- [ ] Create package manager integration (homebrew, apt, etc.)
- [ ] Build MCP server discovery mechanism
- [ ] Ensure MCP servers run as background services when needed

### 3. Universal command templates and personalities
- [ ] Create global command template repository
- [ ] Implement personality marketplace/sharing mechanism
- [ ] Build version control for templates and personalities
- [ ] Enable cross-project template inheritance
- [ ] Create template/personality packaging format

### 4. Clear separation of concerns
- [ ] Establish "dotfiles management" as purely configuration sync
- [ ] Create separate "global developer tools" ecosystem
- [ ] Build plugin architecture for tool integration
- [ ] Implement dependency management for global tools
- [ ] Create clear boundaries between personal config and shared tools

## Architecture Vision

### Global Developer Tools Platform
```
~/.devtools/
├── ai/ # AI assistant configurations
│ ├── personas/ # Shared across all assistants
│ ├── templates/ # Command templates
│ └── config/ # Provider configs
├── mcp/ # Global MCP servers
│ ├── servers/ # Installed servers
│ ├── registry/ # Available servers
│ └── config/ # Server configurations
├── tools/ # Other developer tools
└── config/ # Global tool configurations
```

### Integration Points
- Package managers for easy installation
- Service management for background processes
- Plugin architecture for extensibility
- Version control and updates
- Cross-platform compatibility

## Success Criteria
- Developer tools work identically across all projects
- Zero configuration needed in individual projects
- Tools can be shared and discovered easily
- Clear separation between personal preferences and shared tools
- Ecosystem supports community contributions

## Philosophical Alignment
This vision aligns with several core principles:
- **Systems Stewardship**: Building reusable, maintainable systems
- **Subtraction Creates Value**: Removing per-project configuration overhead
- **Global-First**: Everything useful should be globally accessible
- **Developer Experience**: Tools should delight and empower

## Related Issues
- #793 - Establish global-first configuration principle
- #798 - Audit: Configurations violating global-first principle
- #799 - Global-first principle: Immediate fixes needed
- #800 - Global-first principle: Medium-term improvements

This represents the ultimate goal: a cohesive global developer tools ecosystem where configurations enhance every project without manual setup.

No files, tests, or entry points are identified; begin by reviewing the related issues #793, #798, #799, and #800. This issue is a long-term architecture vision rather than a bounded implementation task, with completion defined by the broad success criteria and multiple unchecked systems.

Written by the indexing model from the issue text.