about-pick-theme-original

Document the original pick-theme flow across Neovim, tmux, Ghostty, Zed, and shell configurations.

Updated Jun 17, 2025
One-click install
npx skills add https://github.com/nikbrunner/dots --skill about-pick-theme-original
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: about-pick-theme-original
Source: https://github.com/nikbrunner/dots/tree/main/common/.agents/skills/about-pick-theme-original
Command: npx skills add https://github.com/nikbrunner/dots --skill about-pick-theme-original

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Knowledge Unit documents the original pick-theme implementation to guide migration work and replacement in the livery updater project, ensuring developers understand the prior behavior.

Core Features & Use Cases

  • Behavior reference: captures the flow of selecting and applying themes across Neovim, tmux, Ghostty, Zed, and related tools.
  • Migration guidance: serves as a blueprint for implementing equivalent updaters in the new desktop or cross-platform setup.
  • Source traceability: lists source files and command sequences needed to reproduce the behavior during onboarding or auditing.

Quick Start

Review the documented flow and updaters to replicate the original pick-theme behavior in your migration tasks.

Frequently Asked Questions about about-pick-theme-original

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

FAQPage Schema
How do I document legacy theme switching behavior for a dotfiles migration?

Documenting legacy theme switching behavior for a dotfiles migration involves capturing the end-to-end flow of selecting and applying themes across Neovim, tmux, Ghostty, and Zed. This process details updaters, target files, and reload sequences to guide accurate implementation.

What is the original pick-theme behavior for cross-platform theme updates?

The original pick-theme behavior for cross-platform theme updates encompasses selecting and applying themes across Neovim, tmux, Ghostty, Zed, and shell configurations. It details the specific updaters, target files, reload sequences, and path conventions required for accurate replication.

How do I migrate my Neovim and tmux theme updaters to a new desktop setup?

To migrate Neovim and tmux theme updaters to a new desktop setup, review the documented flow of the original behavior. This serves as a blueprint for implementing equivalent updaters by listing source files and command sequences needed to reproduce the configuration.

Does this documentation cover reload sequences and path conventions for Ghostty and Zed?

Yes, this documentation covers reload sequences and path conventions for Ghostty and Zed. It satisfies requirements to detail the specific updaters and target files needed to reproduce the original cross-platform theme application behavior during onboarding or auditing.

Why do I need to trace source files when replacing a shell configuration theme updater?

Tracing source files when replacing a shell configuration theme updater ensures source traceability and accurate implementation. It lists the exact command sequences and target files needed to reproduce the original behavior, preventing configuration drift during migration.