How uliboooo/dotfiles works
Project type and purpose
• This is a personal “dotfiles” repository. Its purpose is to centralize and version-control user configuration files for shells (Zsh, Starship), editors (Neovim, Vim, Zed), terminals (Alacritty, Wezterm), and various command-line utilities. A bootstrap script (setup.sh or setup_arch.bash) installs dependencies and creates symlinks from the home directory to the stored configs.
File structure
• Top-level artifacts
• setup scripts: setup_arch.bash, vm-run.sh, tools/zenn_push.bash
• configuration directories: common-lisp, help_md, and usr/.config/...
• dotfiles in usr/—shell configs (.zshrc, .tmux.conf), editor configs (.vimrc, Emacs under usr/emacs), plus per-tool theme files.
• Patterns
• Everything lives under usr/ to mirror ~/.config and home-dir files.
• setup.sh (implied) clones the repo, then runs setup/links.sh to create symbolic links.
• The repo is OS-agnostic, supporting multiple package managers (Homebrew, APT, DNF, Pacman).
README for additional insights
• It describes a two-step install: clone and run setup.sh.
• The bootstrap installs required packages, then symlinks config files into $HOME.
Elements
[User], [GitHub Repo], [Bootstrap Script], [Package Manager], [Linker Script], [Home Directory], [Shell & Tools]
• User → GitHub Repo (clone)
• User → Bootstrap Script (execute)
• Bootstrap Script → Package Manager (install)
• Bootstrap Script → Linker Script (invoke)
• Linker Script → Home Directory (create symlinks)
• Home Directory → Tools (config consumption)