Global-first principle: Immediate fixes needed

## Overview
This issue tracks immediate fixes needed to align with the global-first configuration principle established in #793.

## Immediate Action Items

### 1. Move Claude personalities to global location
- [ ] Create `~/.claude/personalities/` directory structure in setup.sh
- [ ] Move personality files from `.claude/personalities/` to global location
- [ ] Update any references to use the global path
- [ ] Ensure personalities are available in all projects

### 2. Make command templates globally accessible
- [ ] Move command templates to a global location (e.g., `~/.claude/command-templates/`)
- [ ] Update command generation scripts to use global templates
- [ ] Ensure templates work across all projects, not just dotfiles

### 3. Replace hardcoded paths with environment variables
- [ ] Audit all scripts for hardcoded `/home/linuxmint-lp/ppv/pillars/dotfiles/` paths
- [ ] Replace with `$DOT_DEN` or other appropriate environment variables
- [ ] Update documentation to use relative or variable-based paths
- [ ] Test portability across different user environments

### 4. Create true global MCP server installations
- [ ] Investigate global installation paths for MCP servers
- [ ] Update setup scripts to install MCP servers globally
- [ ] Ensure MCP servers work from any directory
- [ ] Remove dependency on local dotfiles directory for MCP functionality

## Success Criteria
- All changes can be completed in a single PR
- No breaking changes to existing functionality
- Configurations work globally after running setup.sh
- No hardcoded user-specific paths remain

## Related Issues
- #793 - Establish global-first configuration principle
- #798 - Audit: Configurations violating global-first principle

These are quick wins that can be implemented immediately to start aligning with the global-first principle.

Start by reading setup.sh and the command generation scripts, then review the audits in #793 and #798. Trace references to the listed hardcoded path and the current local personality, template, and MCP locations. Done means setup.sh establishes global paths, scripts work from any directory, portability is tested, and no user-specific paths remain.

Written by the indexing model from the issue text.