agentleFS
Sign inStart free
htlin222htlin222/dotfiles/start/CLAUDE.md

dotfiles / start

CLAUDE.md78 starsChanged 4 months agoMITView on GitHub

See setup.md for the human/agent-facing install guide (flags, env vars, one-liners). Four entry points, all built on the shared TUI library in lib/: - bootstrap — full machine setup: Homebrew → oh-my-zsh (--unattended) → symlinks → macOS deps (sources bin/dot). - link_dotfiles — symlinks only: every *.symlink (maxdepth 2) under the repo becomes ~/.<basename>. Idempotent; safe to re-run. - install — brew bundle (streamed) + every topic install.sh (spinnered; failures don't abort the rest). - setuplinux.sh — Pop!OS/apt setup: packages,…

  • Installs packages

We split this CLAUDE.md into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    No associative arrays, no ${var,,}, no readarray.

    line 39
  2. Distinctive:

    Don't spinner commands that prompt (sudo apt, brew bundle) — stream them.

    line 42
  3. Very specific:

    Verify with bash -n, shellcheck --severity=warning, and a sandbox run: fake $HOME + fake repo, execute with /bin/bash (3.2).

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 25,680 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

start/ — installers

See setup.md for the human/agent-facing install guide (flags, env vars, one-liners).

Four entry points, all built on the shared TUI library in lib/:

  • bootstrap — full machine setup: Homebrew → oh-my-zsh (--unattended) → symlinks → macOS deps (sources bin/dot).
  • link_dotfiles — symlinks only: every *.symlink (maxdepth 2) under the repo becomes ~/.<basename>. Idempotent; safe to re-run.
  • install — brew bundle (streamed) + every topic install.sh (spinnered; failures don't abort the rest).
  • setup_linux.sh — Pop!_OS/apt setup: packages, oh-my-zsh + plugins, TPM, explicit link list, chsh. Unattended: backup_all=true, never prompts.

lib/

  • ui.sh — source first. Capability-detected TUI: banner boxes, step counters (ui_steps_total + ui_step), status lines (ui_ok/info/warn/err), ui_fail (aborts), ui_run LABEL CMD… (spinner; captures output, shows last 15 lines on failure, returns the command's rc), ui_done (elapsed). Degrades for non-tty / NO_COLOR / TERM=dumb / non-UTF-8 locales.
  • links.sh — source after ui.sh; needs $DOTFILES_ROOT set. link_file src dst with conflict policy globals (overwrite_all/backup_all/ skip_all — set before calling to skip prompts), install_dotfiles (the find loop), links_summary (counters). Has an -ef self-link guard so linking the repo onto itself can't move it away. Non-interactive support: noninteractive/on_conflict globals (auto-set from UI_TTY/DOTFILES_NONINTERACTIVE/DOTFILES_ON_CONFLICT); when no TTY or -y, link_file applies on_conflict (default backup) instead of the read </dev/tty prompt. links_parse_args "$@" parses the shared flags (-y/--non-interactive, --backup/--overwrite/--skip, -h → calls the caller's usage).

Constraints

  • Bash 3.2 — runs on fresh macOS before Homebrew installs bash 5. No associative arrays, no ${var,,}, no readarray.
  • Pad TUI strings by character count, not printf %-*s (bytes) — multibyte glyphs break box alignment otherwise.
  • Don't spinner commands that prompt (sudo apt, brew bundle) — stream them.
  • Verify with bash -n, shellcheck --severity=warning, and a sandbox run: fake $HOME + fake repo, execute with /bin/bash (3.2).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free