Personal macOS Organization

Manage and configure a personal macOS environment with organization files, system settings, security tooling, and AI assistant operational rules.

Purpose

This skill helps you work with a repository that centralizes:

Core Operations

Git Security Management

Set up comprehensive git-secrets protection across all repositories:

1. **Global setup**: Run `./setup-git-hooks.sh` to configure git-secrets globally with automatic pre-commit hooks

2. **Per-repository setup**: Use `./apply-git-hooks.sh /path/to/repository` to add security hooks to existing projects

3. **Historical scanning**: Execute `./scan-repo-for-secrets.sh /path/to/repository` to audit git history for leaked credentials

4. **Prevention patterns**: All scripts automatically detect AWS keys, API tokens, private keys, and other sensitive patterns

macOS System Configuration

Apply and manage declarative system preferences:

1. **Apply settings**: Run `./defaults_settings.sh` to configure macOS system defaults (Dock, Finder, keyboard, trackpad, etc.)

2. **Export current settings**: Use `./export_defaults.sh` to capture current macOS configuration into version-controlled scripts

3. **Package management**: Modify `Brewfile` for applications and tools, then run `brew bundle install --file=Brewfile`

4. **Repeatability**: All configurations are scriptable for new machine setup or system rebuilds

AI Assistant Rules

The repository uses a unified rules system:

File Structure

Configuration Files

Security Utilities

Documentation

Operational Guidelines

When Modifying Configuration

1. **Document changes**: Update corresponding `.md` files when changing configurations

2. **Test scripts**: Verify shell scripts work before committing

3. **Brewfile changes**: Always run `brew bundle install` after modifying `Brewfile`

4. **Defaults changes**: Test `defaults_settings.sh` on non-critical settings first

Security Best Practices

1. **Never commit secrets**: All scripts are pre-configured to prevent credential leaks

2. **Use environment variables**: Store sensitive data in `.env` files (globally gitignored)

3. **Regular audits**: Periodically run `scan-repo-for-secrets.sh` on important repositories

4. **Global protection**: Install git-secrets globally so all new repositories inherit protection

Adding New Tools or Scripts

1. **Follow existing patterns**: Match naming conventions and structure

2. **Add documentation**: Include usage instructions in comments and corresponding `.md` files

3. **Update CLAUDE.md**: Add new commands or architecture changes to this context file

4. **Test security hooks**: Ensure new scripts don't trigger false positives in git-secrets

Common Tasks

Setting Up a New Mac

```bash

1. Install Homebrew first (see brew.sh)

2. Clone this repository

3. Set up git security globally

./setup-git-hooks.sh

4. Apply macOS system preferences

./defaults_settings.sh

5. Install applications and tools

brew bundle install --file=Brewfile

```

Auditing an Existing Repository

```bash

Scan git history for potential secrets

./scan-repo-for-secrets.sh /path/to/repository

Apply security hooks to prevent future leaks

./apply-git-hooks.sh /path/to/repository

```

Updating System Configuration

```bash

Export current macOS settings

./export_defaults.sh

Review changes to defaults_settings.sh

git diff defaults_settings.sh

Apply updated settings

./defaults_settings.sh

```

Constraints

Notes

This repository serves as a living configuration system for personal macOS environments. All changes should maintain:

When working with this repository, prioritize maintaining the security infrastructure and documentation quality over adding new features.