This repository holds my personal configuration files for the majority of applications that I use along with setup scripts that automatically install the configurations with a a single command on Windows (Git Bash) and Unix environments.
| Application | Description |
|---|---|
NeoVim |
A highly configurable text editor that enhances Vim with extensibility features and improved user experience |
Bash |
The standard Unix shell and command language interpreter |
tig |
A TUI for Git that acts as a repository browser |
zellij |
An extensible terminal multiplexer featuring session management, panes, tabs, and layouts |
tmux |
Another terminal multiplexer I was using before zellij |
k9s |
A TUI for managing Kubernetes clusters |
i3 |
A tiling window manager/Desktop environment for Linux that can be fully controlled using keyboard shortcuts |
Windows Terminal |
Microsoft's terminal application |
vscode-neovim |
VS Code extension that integrates Neovim's editing capabilities into Visual Studio Code |
IdeaVim |
Plugin for JetBrains IDEs that emulates Vim keybindings and functionality within their development environments |
.claude/skills/ holds a small set of skills that chain into one engineering
flow: plan → spec (optional) → build → review, with the domain glossary and ADRs kept
up to date along the way.
Run /setup-flow once per repo. It writes the conventions into that repo's
CLAUDE.md and creates .scratch/, where all specs live as markdown — one
directory per feature, one numbered file per work item. Domain docs live at
CONTEXT.md (glossary) and docs/adr/ (decisions).
| Skill | What it does |
|---|---|
/setup-flow |
One-time per repo: writes the CLAUDE.md conventions block and creates .scratch/ |
/plan-work |
Interviews you round by round until the design is settled, invoking /domain-modeling as it goes |
/to-spec |
Turns the conversation into a feature spec plus numbered work item specs in .scratch/ |
/domain-modeling |
Challenges fuzzy terminology; writes CONTEXT.md entries and ADRs as they crystallise |
/review-branch |
Adversarial review of the branch diff in fresh sub-agents, reported as a summary table plus findings |
The setup scripts set up symlinks for the configuration files to the appropriate locations where applications look for them.
Which files to symlink where is defined in the maps at the top of the setup scripts.
After successful installtion, changes to the configuration files (which can be opened through the symlinks as well)
are reflected in the original files in the git repository. By pushing the changes to this GitHub repository, they
can be made available to other machines by executing a simple git pull.
The setup requires no external dependencies.
Run setup.sh as a regular user.
Neither Windows, nor git bash are supported.