AGENT SKILL

ams-linux-desktop-pro

暂无简介

License 许可
MIT
所属仓库
TanNhatCMS/jarvis
最近更新
2026-11-07
Stars
★ 0
Forks
1

03 SKILL.md 正文

Linux Desktop Pro

Overview

Linux on the desktop rewards understanding: you choose the distro, desktop environment, and tools — and own the result.

The pro stack: a stable distro, a keyboard-driven workflow (tiling WM or well-configured DE), declarative dotfiles, and terminal fluency.

This skill is about building a fast, stable, reproducible Linux workstation — not distro-hopping forever.

When to use

  • Choosing a distro and desktop environment for daily work
  • Setting up a new Linux workstation productively
  • Moving to a tiling window manager (i3, Sway, Hyprland)
  • Managing dotfiles and reproducible setups
  • Troubleshooting and maintaining a Linux desktop long-term

Core concepts

  • Distro choice. For workstations: stable, well-supported releases (Ubuntu LTS, Fedora, Debian stable). Rolling releases are fun; LTS is productive.
  • Desktop environment vs. tiling WM. GNOME/KDE for approachable defaults; i3/Sway/Hyprland for keyboard-driven tiling. Tiling WMs maximize screen use and eliminate window management overhead.
  • Package management. Know your manager (apt, dnf, pacman) plus Flatpak for desktop apps. Prefer repo packages; be deliberate about third-party sources.
  • Dotfiles. Version-control your configs (~/.config, shell, editor, WM). New machine or reinstall = clone repo, run install script, done.
  • Terminal fluency. The terminal is a first-class citizen: shell (bash/zsh/fish), tmux or editor-integrated terminals, coreutils for file ops.
  • Keyboard-driven workflow. Launcher (rofi/wofi or DE equivalent), WM keybindings for windows/workspaces, browser vim-bindings. The mouse becomes optional.
  • Systemd basics. Enable/disable services, read logs with journalctl, create user services for things that should auto-start reliably.
  • Backups. Timeshift for system snapshots, plus file backups (restic, borg) to external storage. Rolling release without snapshots is gambling.

Practical workflow

  1. Pick distro and DE deliberately. Match to your tolerance for tinkering. Workstation rule: boring and stable beats exciting and broken.
  2. Install and update fully. Full update post-install, enable firewall, set up backups before customizing anything fun.
  3. Configure the desktop. Workspaces, keybindings, launcher hotkey, display scaling, night light. Get the daily ergonomics right first.
  4. Set up dotfiles repo. Initialize git in ~/.config (or a manager like chezmoi/stow). Commit before experimenting — rollbacks beat reinstalls.
  5. Learn the tiling basics. If tiling: workspaces, split directions, focus movement, floating toggle. One week of deliberate use to rewire habits.
  6. Install your stack. Editor, browser, terminal, communication apps — via package manager where possible, Flatpak for the rest.
  7. Automate with user services. Things that should always run (sync, backups, agents) as systemd user services, not fragile autostart hacks.
  8. Document the setup. README in the dotfiles repo: distro, DE/WM, key decisions. Future you (and new machines) will thank present you.

Common pitfalls

  • Distro-hopping. Reinstalling monthly instead of working. Pick stable, commit for a year, customize deeply instead of broadly.
  • Rice before work. Perfecting themes for weeks before the system does anything useful. Function first; aesthetics after productivity works.
  • No dotfiles. Hand-configured system that can't be reproduced. One disk failure = weeks of re-setup. Version-control everything.
  • Ignoring backups. 'Linux doesn't crash' until it does. Timeshift + file backups before you need them, not after.
  • PPA / AUR recklessness. Adding random repositories for shiny versions. Each third-party source is trust + breakage risk. Prefer official repos.
  • Fighting the DE. Installing GNOME then replacing every component instead of choosing the DE/WM that matches your workflow. Choose, don't fight.
  • Terminal avoidance. On Linux the terminal is the fast path for many tasks. Learn the core 20 commands; the GUI-only route is the slow one here.
  • No update discipline. Ignoring updates for months (security) or updating recklessly mid-deadline (stability). Schedule updates; snapshot first.

04 同仓库更多 Skills

TanNhatCMS
TanNhatCMS/jarvis

web-scrape

Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open/fetch fails on JS-heavy pages, or when you need clean markdown/structured extraction from a site. Requires FIRECRAWL_API_KEY.

★ 0
TanNhatCMS
TanNhatCMS/jarvis

design-taste-frontend

tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML/CSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, "AI-made", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.

★ 0
TanNhatCMS
TanNhatCMS/jarvis

test-driven-development

Use when implementing any feature or bugfix, before writing implementation code

★ 0
TanNhatCMS
TanNhatCMS/jarvis

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

★ 0
TanNhatCMS
TanNhatCMS/jarvis

requesting-code-review

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

★ 0
TanNhatCMS
TanNhatCMS/jarvis

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).

★ 0