Tmux Config

Manage modular tmux configuration with OS-specific branches and TPM plugins.

Updated Feb 24, 2013
One-click install
npx skills add https://github.com/ysano/dotfiles --skill tmux-config
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Tmux Config
Source: https://github.com/ysano/dotfiles/tree/main/.claude/skills/tmux-config
Command: npx skills add https://github.com/ysano/dotfiles --skill tmux-config

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill centralizes tmux configuration management for dotfiles, reducing manual editing errors and speeding up troubleshooting when adjusting .tmux.conf and its modular components.

Core Features & Use Cases

  • Architecture & Loading Order: Documents the entry point .tmux.conf and its modular includes (base.conf, terminal.conf, appearance.conf, status.conf, keybindings.conf), OS-specific branches (os/wsl.conf, os/linux.conf, os/darwin.conf, os/freebsd.conf), conditional claude.conf, and the TPM plugin setup with resurrect/continuum integration.
  • Claude Voice & Plugins: Describes Claude integration via claude/ directory and plugin management with TPM.
  • Testing & Debugging: Provides scripts to detect configuration conflicts, cross-platform checks, and source-file path validation.
  • Debugging & Do Not Edit areas: Notes on status-right conflict resolution, OS detection order, and how to run tests.

Quick Start

Use the tmux-config skill to audit your current tmux setup by running the conflict check script against your .tmux and .tmux.conf files.

Frequently Asked Questions about Tmux Config

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I organize a modular tmux configuration across different operating systems?

A modular tmux configuration uses a main .tmux.conf that sources separate modules like base.conf, terminal.conf, and appearance.conf, along with OS-specific branches for wsl, linux, darwin, and freebsd environments.

How do I detect conflicts in my tmux configuration files?

You can detect tmux configuration conflicts by running a dedicated conflict check script that audits your .tmux and .tmux.conf files, validates source-file paths, and identifies overlapping status bar or keybinding settings.

Does this tmux setup support TPM plugin management with resurrect and continuum?

Yes, this tmux setup supports TPM plugin management, including the integration of tmux-resurrect and tmux-continuum plugins for session persistence and automatic restoration across terminal restarts.

Can I manage tmux dotfiles across WSL, Linux, macOS, and FreeBSD with OS detection?

Yes, you can manage tmux dotfiles across WSL, Linux, macOS, and FreeBSD by using OS detection scripts to conditionally load the correct os-specific configuration branch during shell startup.

Why is my tmux status-right configuration conflicting after adding new plugins?

Your tmux status-right configuration conflicts because multiple plugins or modules attempt to modify the same status bar variables, requiring structured loading order validation and conflict resolution scripts to isolate the override.

What is the correct loading order for modular tmux configuration files?

The correct loading order for modular tmux configuration starts with the base.conf, followed by terminal, appearance, and status modules, then OS-specific branches, and finally the TPM plugin setup to ensure proper variable inheritance.