macOS Dotfiles Management (bare git)

Manage a personal dotfiles repository using the bare git repository approach. This skill helps you work with macOS development environment configurations including terminal emulators, editors, shell configurations, and utility scripts.

Repository Structure

This dotfiles repository uses a bare git approach where the git directory is separate from the working tree:

Core Alias

All dotfiles git operations use the `config` alias:

```bash

alias config='/usr/bin/git --git-dir=/Users/filipmellqvist/.dotfiles/ --work-tree=/Users/filipmellqvist'

```

**Usage:**

```bash

config status

config add .vimrc

config commit -m "update vim config"

config push

```

Key Configuration Areas

Terminal Environment

**Ghostty Terminal:**

**Zsh Shell:**

Editor Configuration

**Vim:**

**Vim Keymap System:**

Dynamic keymap switching with hot-reload support:

Features:

Key files:

File Management

**SPF (Superfile):**

Development Aliases

Port Management

Kill processes and restart development servers:

```bash

Kill single ports

kill3000, kill3001, kill3002, kill3003, kill5555

Kill + start dev servers

3000, 3001, 3002, 3003

Start npm servers on specific ports

npm3001, npm3002, npm3003

Prisma Studio

5555 # Kill port 5555 and start Prisma Studio

Kill all npm dev ports

killnpmall # Kills ports 3000-3002

```

Application Shortcuts

```bash

sp # Start SPF file manager

mw # Start MacroWhisper

tm # Start task-master

```

Utility Scripts

Located in `my_scripts/.script/`:

Certificate Management

Audio Configuration

System Utilities

Theme Consistency

All applications use coordinated theming:

Working with Dotfiles

When making configuration changes:

1. **Edit files in place** in your home directory

2. **Stage changes** using the `config` alias:

```bash

config add path/to/modified/file

```

3. **Check status** to see tracked vs untracked:

```bash

config status

```

4. **Commit changes**:

```bash

config commit -m "descriptive message"

```

5. **Push to remote**:

```bash

config push

```

Best Practices

1. **Test before committing:** Verify changes work in target application

2. **Use config alias:** Never use plain `git` in this repository

3. **Maintain theme consistency:** Match catppuccin/nightfox themes

4. **Backup before major changes:** Copy existing configs first

5. **Document new additions:** Update documentation for new aliases/scripts

6. **Respect file structure:** Keep configs in their application directories

7. **Avoid tracking sensitive data:** Use `.gitignore` for secrets

Development Environment Details

**Configured Runtimes:**

**Editor Integration:**

File Organization

```

~/

├── ghostty/.config/ghostty/config

├── vim/.vimrc

├── vim/.vim/keymap_state

├── zsh/.zshrc

├── spf/.spf.toml

├── macrowhisper/.config/macrowhisper/

├── mypaint/.config/mypaint/

├── iterm/Default.json

├── my_scripts/.script/

│ ├── vim-keymap-toggle.sh

│ ├── vscode-vim-keymap-manager.sh

│ ├── ca-cert-creator/

│ ├── pulseaudio/

│ ├── keyboard_layouts/

│ └── miniscripts/

└── MW Macros.kmmacros

```

Notes