A ready-to-use and adaptable workspace that brings your terminal, editor, shell, and sessions together in one documented workflow.
Start safely
Run a dry preview from any directory. It checks your system and prints the complete installation plan without changing files, installing dependencies, or creating links.
bash -c "$(curl -fsSL https://raw.githubusercontent.com/angelgonzalezev/dotfiles/main/install.sh)" -- --dry-runWhy dotfiles
Stop rebuilding your development environment from memory. Keep the setup, the commands, and the reasoning behind them together in one versioned workspace.
Turn a fresh machine into a familiar development environment through a repeatable, guided installation.
Move between terminal, persistent sessions, project search, editing, and commands without rebuilding context.
Track configuration in Git, understand every shortcut, and restore previous files when a setup is not right for you.
How it works
The installer makes each decision visible before it touches your configuration.
Inspect dependencies, managed paths, conflicts, and the backup location with a dry run.
Select only the tools and configuration packages that belong in your workflow.
Back up conflicting files, install dependencies, and create managed configuration links.
Open a documented workspace and use consistent commands across daily projects.
The workspace
Each tool owns one layer of the workflow, so the full setup stays understandable and every part can be adapted independently.
The terminal window: tabs, panes, fonts, colors, native controls, and keyboard shortcuts.
The interactive shell: prompt, history, suggestions, aliases, and access to local commands.
The persistent workspace: reusable layouts, split panes, sessions, and live system context.
The editor: keyboard-first navigation, file discovery, project search, buffers, and coding shortcuts.
Built for daily use
The value is not a collection of config files. It is the repeatable workflow those files create together.
Search files and project text from Neovim with documented shortcuts.
Open two-pane or four-pane layouts with tmux-dev and tmux-agent.
Detach from tmux, close the terminal, and reconnect to the same session later.
Keep shortcuts, recovery steps, and custom commands searchable beside the configuration.
A typical session
Every layer has a clear responsibility, from drawing the terminal window to keeping sessions alive and editing the project.
Explore the daily workflowReversible by design
Before managed files are linked, conflicts are recorded and moved into a timestamped backup. Installation runs can be inspected, diagnosed, and restored through the same command-line interface.
Open source and adaptable
Created by Angel Gonzalez as a real development workspace, this project is published under the MIT License so you can inspect it, fork it, adapt the configuration, and share improvements.
$ bbldr dotfiles doctor
all checks passed
$ git checkout -b improve/workflow
$ npm run check
$ git push origin improve/workflowBefore you install
macOS, Ubuntu, and Debian have automated dependency support. Other Linux distributions can use the configuration packages after installing dependencies manually.
Only conflicting managed targets are moved into a timestamped backup. Unrelated files remain in place.
No. The interactive installer lets you choose the packages and relevant dependency groups you want.
Yes. Installation manifests record the affected targets so a selected run can be restored with bbldr dotfiles restore.
Yes. Fork the repository for shared changes and use local override files for private or machine-specific values.
Start with confidence
Preview every change first, then choose the parts of the workspace that fit the way you build.