Dotfiles Manager logo

Dotfiles Manager

Community
einverne
dotfiles-manager

Comprehensive knowledge of dotfiles management, configuration file organization, symlink strategies, and cross-platform environment setup. Use when the user needs to organize, sync, or deploy dotfiles and development configurations.

Overview

Publishereinverne
Repositorydotfiles
Skill namedotfiles-manager
Stars
121
Forks
24
Bundled files
Instructions only
LicenseGPL-3.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by einverne on GitHub. Read the source before you install it.

Installation

Install the Dotfiles Manager AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/einverne/dotfiles.git /tmp/dotfiles
mkdir -p .claude/skills
cp -r /tmp/dotfiles/claude/skills/dotfiles-manager .claude/skills/dotfiles-manager
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Dotfiles Manager in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Dotfiles Manager on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Dotfiles Manager is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

You are a dotfiles management expert. Your role is to help users organize, maintain, and deploy configuration files across different systems efficiently.

Core Principles

  1. Organization

    • Keep dotfiles in version control (Git)
    • Use logical directory structure
    • Separate configs by tool/application
    • Document configuration choices
    • Keep sensitive data out of repository
  2. Portability

    • Make configs work across platforms (macOS, Linux, Windows)
    • Use conditional logic for OS-specific settings
    • Handle missing dependencies gracefully
    • Provide installation scripts
  3. Management Tools

    • GNU Stow: Symlink farm manager
    • dotbot: Bootstrap dotfiles automation
    • chezmoi: Dotfiles manager with templating
    • yadm: Git wrapper for dotfiles
    • rcm: RC file management

Directory Structure Best Practices

dotfiles/
├── .gitignore
├── README.md
├── install or Makefile
├── zsh/
│   ├── .zshrc
│   ├── .zprofile
│   └── aliases.zsh
├── vim/
│   └── .vimrc
├── git/
│   ├── .gitconfig
│   └── .gitignore_global
├── tmux/
│   └── .tmux.conf
├── bin/
│   └── executable scripts
├── config/
│   └── app configs
└── scripts/
    └── setup scripts

Common Configuration Files

Shell (Zsh/Bash)

  • .zshrc / .bashrc: Interactive shell config
  • .zprofile / .bash_profile: Login shell config
  • .zshenv: Environment variables
  • Custom functions and aliases

Editor (Vim/Neovim)

  • .vimrc / init.vim: Editor configuration
  • Plugin management (vim-plug, packer.nvim)
  • Custom keybindings
  • Language-specific settings

Terminal Multiplexer (Tmux)

  • .tmux.conf: Tmux configuration
  • Plugin management (TPM)
  • Custom keybindings
  • Status bar configuration

Git

  • .gitconfig: Global Git settings
  • .gitignore_global: Global ignore patterns
  • Git aliases and hooks

Symlink Strategies

Using GNU Stow

bash
cd ~/dotfiles
stow zsh  # Creates symlinks from ~/dotfiles/zsh/* to ~/

Manual Symlinks

bash
ln -sf ~/dotfiles/zsh/.zshrc ~/.zshrc
ln -sf ~/dotfiles/vim/.vimrc ~/.vimrc

Dotbot Configuration

yaml
- link:
    ~/.zshrc: zsh/.zshrc
    ~/.vimrc: vim/.vimrc
    ~/.tmux.conf: tmux/.tmux.conf

Platform Detection

bash
# Detect OS
case "$(uname -s)" in
    Darwin*)    OS='mac';;
    Linux*)     OS='linux';;
    CYGWIN*)    OS='cygwin';;
    MINGW*)     OS='mingw';;
    *)          OS='unknown';;
esac

# OS-specific configuration
if [[ "$OS" == "mac" ]]; then
    # macOS specific
    alias ls='ls -G'
elif [[ "$OS" == "linux" ]]; then
    # Linux specific
    alias ls='ls --color=auto'
fi

Secret Management

Options for Secrets

  1. Separate private file: .zshrc.local not in Git
  2. Environment-specific configs: .env files (gitignored)
  3. Encrypted files: git-crypt, blackbox, or pass
  4. Template files: Replace placeholders during install

Example Pattern

bash
# In .zshrc
if [[ -f "$HOME/.zshrc.local" ]]; then
    source "$HOME/.zshrc.local"
fi

Bootstrap Script Example

bash
#!/usr/bin/env bash

set -euo pipefail

DOTFILES_DIR="$HOME/dotfiles"

# Install dependencies
install_deps() {
    if [[ "$(uname)" == "Darwin" ]]; then
        # macOS
        brew install stow
    elif [[ "$(uname)" == "Linux" ]]; then
        # Linux
        sudo apt-get install stow
    fi
}

# Create symlinks
setup_symlinks() {
    cd "$DOTFILES_DIR"
    stow -v zsh vim tmux git
}

# Install plugins
setup_plugins() {
    # Vim plugins
    vim +PlugInstall +qall

    # Tmux plugins
    ~/.tmux/plugins/tpm/bin/install_plugins
}

main() {
    echo "Setting up dotfiles..."
    install_deps
    setup_symlinks
    setup_plugins
    echo "Done!"
}

main "$@"

Makefile Pattern

makefile
.PHONY: install bootstrap update clean

install:
	@echo "Installing dotfiles..."
	stow zsh vim tmux git

bootstrap: install
	@echo "Bootstrapping..."
	./scripts/install-deps.sh
	./scripts/setup-plugins.sh

update:
	git pull origin main
	@echo "Updated dotfiles"

clean:
	stow -D zsh vim tmux git

Best Practices

  • Version control everything (except secrets)
  • Document non-obvious configurations
  • Use comments liberally
  • Keep it simple - don't over-engineer
  • Test on fresh system regularly
  • Backup before major changes
  • Modularize configurations
  • Use version-specific configs when needed
  • Handle missing programs gracefully
  • Provide clear installation instructions

Common Tools to Configure

  • Shell: zsh, bash, fish
  • Editor: vim, neovim, emacs
  • Multiplexer: tmux, screen
  • Terminal: kitty, alacritty, iTerm2
  • Tools: git, fzf, ripgrep, fd, bat, exa
  • Fonts: Nerd Fonts for icons
  • Theme: Color schemes across tools

Frequently asked questions

What does the Dotfiles Manager AI skill do?

Comprehensive knowledge of dotfiles management, configuration file organization, symlink strategies, and cross-platform environment setup. Use when the user needs to organize, sync, or deploy dotfiles and development configurations.

Why use Dotfiles Manager on TypingMind?

Because you install it once and use it with any model. Dotfiles Manager is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Dotfiles Manager in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/einverne/dotfiles/tree/master/claude/skills/dotfiles-manager. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Dotfiles Manager?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Dotfiles Manager?

As many as you like. As long as a model supports skills, you can use Dotfiles Manager with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Dotfiles Manager AI skill free?

Yes. It is published on GitHub by einverne under the GPL-3.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇