I noticed some of the install scripts `install/*sh` hard wraps  `yay -S` command with backslashes. here is an example from ` install/3‑terminal.sh`:

```sh
yay -S --noconfirm --needed \
  wget curl unzip inetutils impala \
  fd eza fzf ripgrep zoxide bat \
  wl-clipboard fastfetch btop \
  man tldr less whois plocate bash-completion \
  alacritty
```

 **Why this is sub optimal**:
- Adding a package means hunting for the trailing back‑slash or risking a missing one.
- Inline comments cannot be added per package without splitting the command even further
- Diffs are noisy when you add or remove tools.

**Here is my Proposal**:
- we declare package as a bash array 
- Expand with "${pkgs[@]}".
- we can keep one liner comments to explain why a tool is present. this is optional but can help new comers.

below is a sample rewrite:

```sh
pkgs=(
  wget            # file downloads
  curl            # HTTP client
  unzip           # ZIP extractor
  iputils         # ping, arping
  alacritty       # GPU terminal
# add more packages if needed.
)

yay -S --noconfirm --needed "${pkgs[@]}"
```

**Trade offs**:
- Scripts gain a few lines of boilerplate.
- Diverges from the current style.


**Next Steps**:
If you’re OK with the change, I’ll open a pilot PR for install/3-terminal.sh.
If merged, I’ll migrate the rest in small, focused PRs.

Thanks for considering.