Linux Dotfiles Manager

Manage mainliufeng's personal dotfiles repository for configuring a Linux development environment with Neovim, Zsh, AwesomeWM, Zellij, and development tools.

What This Skill Does

This skill helps you work with a modular dotfiles repository where each component (nvim, git, awesome, zsh, zellij, etc.) has its own directory with setup scripts, configuration files, and linking scripts. It provides guidance on installation, configuration updates, and understanding the architecture of the development environment.

Instructions

When the user asks about or wants to work with this dotfiles repository, follow these steps:

1. Understanding Repository Structure

The repository follows a modular pattern:

- `setup.sh` - Installs dependencies for that component

- `link.sh` - Creates symbolic links to `~/.config/` or appropriate locations

- Configuration files specific to that component

Key directories:

2. Initial Setup Commands

For complete environment setup:

```bash

Run main development setup script

sh 1_dev/setup.sh

```

For individual components:

```bash

Install dependencies for specific component

sh <component>/setup.sh

Create symbolic links for component configs

sh <component>/link.sh

```

For all component links at once:

```bash

Run root linking script

sh link.sh

```

For custom scripts installation:

```bash

Copy all custom scripts to /usr/local/bin/

sh scripts/dotfiles-setup-scripts

```

3. Key Components to Know

**Neovim (`nvim/`)**:

**Zellij (`zellij/`)**:

**AwesomeWM (`awesome/`)**:

**Shell (`zsh/`)**:

**Custom Scripts (`scripts/`)**:

**Claude Code & Codex**:

4. Making Configuration Changes

When the user wants to modify configurations:

1. **Identify the component**: Determine which component directory contains the config

2. **Edit in place**: Files are already linked to system locations, so edits in the repo affect the active config

3. **Test changes**: Reload the relevant service (e.g., `:source $MYVIMRC` for Neovim, restart AwesomeWM)

4. **Commit changes**: Help user commit and document the changes

5. Adding New Components

When adding a new tool configuration:

1. Create a new directory for the component

2. Add configuration files

3. Create `setup.sh` for dependency installation

4. Create `link.sh` for symbolic linking

5. Update root `link.sh` to include the new component

6. Development Tools

The setup includes:

7. Language-Specific Notes

**Go Development**:

**Python**:

**JavaScript/Node**:

8. Common Tasks

**Update a single component**:

```bash

sh <component>/setup.sh && sh <component>/link.sh

```

**Refresh all scripts**:

```bash

sh scripts/dotfiles-setup-scripts

```

**Full environment refresh**:

```bash

sh 1_dev/setup.sh

```

Examples

Example 1: User wants to update Neovim configuration

1. Navigate to `nvim/` directory

2. Help user edit the relevant Lua file (e.g., `init.lua` or files in `lua/mainliufeng/`)

3. Test changes with `:source $MYVIMRC` in Neovim

4. Commit changes if successful

Example 2: User wants to add a new custom script

1. Create the script in `scripts/` directory

2. Make it executable: `chmod +x scripts/new-script`

3. Run `sh scripts/dotfiles-setup-scripts` to install to `/usr/local/bin/`

4. Test the script

5. Commit the new script

Example 3: User wants to understand Zellij configuration

1. Navigate to `zellij/config.kdl`

2. Explain the keybinds (Alt+m for fullscreen, Alt-based navigation)

3. Show how `zellij/setup.sh` handles installation

4. Demonstrate how to test changes by restarting Zellij

Important Notes