How g4rcez/dotfiles works
Project type and purpose
• This is a “configuration-as-code” dotfiles management system built with TypeScript and Deno.
• Its purpose is to centralize, version-control, and programmatically generate or symlink all user configurations (shell, editor, window manager, text expander, etc.) via a plugin-based CLI.
File structure
Top-level components:
• bin/ → custom shell utilities and session scripts
• config/ → raw application config subfolders (nvim, wezterm, tmux, zsh, etc.)
• zsh/ → shell initialization, aliases, functions, completions
• dotbot/ → core dotfiles management library and CLI commands
• espanso.config.ts + espanso/ → text-expander plugin & dynamic snippet scripts
• karabiner.config.ts → keyboard remapping plugin entry
• dotfiles.config.ts → main Deno-based orchestrator
• raycast/, vscode/, snippets/ → integrations for those tools
Patterns & choices:
• Plugin system: dotbot/plugins and espanso plugins.
• CLI tasks (deno task dotfiles sync, link, pkg, migrate).
• Config directories mirror target applications.
README for additional insights
• Lists core technologies (Karabiner, Espanso, Zsh, Neovim, Wezterm, Tmux).
• Describes plugin model: espansoPlugin, vscodePlugin, karabinerPlugin.
• Shows end-to-end flow: “deno task dotfiles sync” reads dotfiles.config.ts, loads plugins, writes symlinks, installs packages.