agentleFS
jwrobesjwrobes/skills/setup-nvim-tmux/SKILL.md

setup-nvim-tmux

Skill1 starsChanged 7 months agoMITView on GitHub

Set up a macOS development environment with Neovim and tmux, matching Jonathan's config. Use when the user says "set up neovim", "set up tmux", "configure my terminal", "copy dev environment", or wants to replicate this Neovim + tmux workflow on a new machine.

  • Installs packages

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 1 is distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read and write each config file from this skill's configs/ directory:

    line 48
  2. Very specific:

    Read configs/vimrc → write to ~/.vimrc

    line 50
  3. Very specific:

    Read configs/init.vim → write to ~/.config/nvim/init.vim (create dir with mkdir -p ~/.config/nvim)

    line 51
  4. Very specific:

    Read configs/tmux.conf → write to ~/.tmux.conf

    line 52
  5. Very specific:

    Read configs/save-scrollback.sh → write to ~/.tmux/scripts/save-scrollback.sh

    line 53
  6. Very specific:

    Read configs/restore-scrollback.sh → write to ~/.tmux/scripts/restore-scrollback.sh

    line 54
  7. Distinctive:

    Wait for "TMUX environment reloaded" message

    line 72

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Neovim + Tmux Environment Setup

Automated setup for a macOS dev environment with Neovim, tmux, vim-plug, TPM, and seamless vim/tmux navigation.

Prerequisites

  • macOS with Homebrew installed
  • A terminal emulator (iTerm2 recommended)

Setup Workflow

Copy this checklist and track progress:

- [ ] Step 1: Install core tools via Homebrew
- [ ] Step 2: Install config files
- [ ] Step 3: Install tmux scripts and plugins (TPM)
- [ ] Step 4: Install Neovim plugins (vim-plug)
- [ ] Step 5: Verify the setup

Step 1: Install Core Tools

brew install neovim tmux the_silver_searcher reattach-to-user-namespace node fzf
ToolPurpose
neovimEditor (init.vim sources ~/.vimrc)
tmuxTerminal multiplexer
the_silver_searcherag — fast code search, used by fzf and vim grep
reattach-to-user-namespacemacOS clipboard integration for tmux copy/paste
nodeRequired by coc.nvim and markdown-preview.nvim
fzfFuzzy finder (also installed as a vim plugin)

Step 2: Install Config Files

Read and write each config file from this skill's configs/ directory:

  1. Read configs/vimrc → write to ~/.vimrc
  2. Read configs/init.vim → write to ~/.config/nvim/init.vim (create dir with mkdir -p ~/.config/nvim)
  3. Read configs/tmux.conf → write to ~/.tmux.conf
  4. Read configs/save-scrollback.sh → write to ~/.tmux/scripts/save-scrollback.sh
  5. Read configs/restore-scrollback.sh → write to ~/.tmux/scripts/restore-scrollback.sh
  6. Make scripts executable:
mkdir -p ~/.tmux/scripts
chmod +x ~/.tmux/scripts/save-scrollback.sh ~/.tmux/scripts/restore-scrollback.sh

Step 3: Install Tmux Plugin Manager (TPM)

git clone https://github.com/tmux-plugins/tpm ~/.tmux/plugins/tpm

Then install the tmux plugins:

  1. Start tmux: tmux
  2. Press Ctrl-a then I (capital I) to install plugins (tmux-resurrect, tmux-continuum)
  3. Wait for "TMUX environment reloaded" message

Step 4: Install Neovim Plugins (vim-plug)

vim-plug auto-installs on first launch (see the curl in .vimrc). Just run:

nvim +PlugInstall +qall

This installs all plugins defined in the plug#begin / plug#end block. Key plugins:

PluginWhat it does
fzf + fzf.vimFuzzy file finder (Ctrl-p) and history (Ctrl-b)
vim-tmux-navigatorSeamless Ctrl-h/j/k/l between vim splits and tmux panes
vim-tmux-runnerSend commands from vim to a tmux pane
coc.nvimAutocomplete engine (needs Node.js)
vim-fugitiveGit wrapper (:Git blame, :Git diff, etc.)
vim-surroundChange surrounding chars (cs"' to swap " → ')
vim-commentaryToggle comments with gcc
vim-test + tslimeRun tests from vim, output in a tmux pane
markdown-preview.nvimLive markdown preview in browser
vim-easy-alignAlign text across lines
jellybeans.vimColor scheme

Step 5: Verify

# Neovim launches without errors
nvim --version

# Tmux launches with correct prefix (Ctrl-a)
tmux new -s test
# Press Ctrl-a then : — should open tmux command prompt

# ag works
ag --version

# Clipboard integration works
echo "test" | pbcopy && pbpaste

Key Bindings Quick Reference

Tmux (prefix = Ctrl-a)

BindingAction
Ctrl-a |Split pane horizontally
Ctrl-a -Split pane vertically
Ctrl-a h/j/k/lNavigate panes (vim-style)
Ctrl-a H/J/K/LResize panes
Ctrl-a rReload tmux.conf
Ctrl-a IInstall TPM plugins
Ctrl-h/j/k/lNavigate between vim splits AND tmux panes seamlessly

Neovim (leader = Space)

BindingAction
Ctrl-pFuzzy find files
Ctrl-bFuzzy find from file history
Space sRun nearest test
Space tRun current test file
Space vRe-run last test
Space lpStart markdown preview
Space lcStop markdown preview
gccToggle comment on line
jkExit insert mode (alternative to Esc)
Space SpaceSwitch between last two files
Space ffToggle fold
KGrep word under cursor
\Start an Ag search

Customization Notes

  • Color scheme: Set by jellybeans.vim. Change in .vimrc if preferred.
  • Tab width: 2 spaces (set in .vimrc via tabstop/shiftwidth).
  • Tmux status bar: Red with session name, positioned at top. Customize in .tmux.conf.
  • Test runner: Configured for RSpec and Mocha via vim-test. Adjust test#ruby#rspec#executable for your project.
  • Copilot: Commented out in .vimrc — uncomment the Copilot section if desired.
  • Tree-sitter: Commented out in both init.vim and .vimrc — uncomment to enable better syntax highlighting.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.