Write code portfolio

Skill urmzd/dotfiles/dot_agents/skills/write-code-portfolio

Cross-platform dotfiles managed by Chezmoi with Homebrew/apt and per-language version managers. One-command bootstrap for macOS and Linux with Neovim, Tmux, Zsh, and AI agent skills.

Install

npx -y skills add urmzd/dotfiles --skill write-code-portfolio

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Personal portfolio dev-setup: add or remove a package/tool in flake.nix per-language shells, edit chezmoi installer scripts, and adjust Powerlevel10k (dot_p10k.zsh), Nix, or Neovim (private_dot_config/nvim) machine config. Use when editing chezmoi-managed dotfiles, adding/removing a language toolchain or CLI to a Nix shell, changing the zsh prompt, tweaking Neovim, branching dotfiles on machine attributes (is_macos / is_personal / is_work), or bootstrapping a new machine in this portfolio. Do NOT use for portable coding patterns or general tech-stack picks; use write-code for those.

SKILL.md

3.0 KB, 567 tokens by cl100k_base, as published. Nobody here has run it

Portfolio Dev Setup

Personal, opinionated tooling that backs the patterns in write-code. This is not portable. Other users on Bitwarden + asdf + bash will not want any of this.

Composable Toolsets (Nix Flakes)

13 reusable per-language shells combined via flake.nix outputs. Each shell pins a single toolchain (rust-toolchain, go, node, python with uv, etc.). Projects compose the shells they need; nothing pollutes the global env.

Each language shell exposes a devShell and a lib.tools set for downstream composition
Avoid nix-direnv here -- vanilla direnv + a use flake line keeps cold-start fast and predictable on macOS

Machine Polymorphism (chezmoi)

Dotfile templates branch on host attributes:

{{ if .is_macos -}}
# macOS-only block (Homebrew bundle, defaults write, ...)
{{ end -}}

{{ if and .is_personal (not .is_work) -}}
# personal-only block (1Password personal vault, side projects, ...)
{{ end -}}

Attributes come from .chezmoi.toml.tmpl (is_macos, is_linux, is_personal, is_work). Keep templates small and the booleans flat; deeply nested {{ if }} blocks are a smell.

Powerlevel10k

Zsh prompt with instant prompt enabled and cache invalidation tied to plugin dir mtime. Source of truth: dot_p10k.zsh in the chezmoi source. Avoid editing the rendered ~/.p10k.zsh directly -- it is overwritten on next chezmoi apply.

Neovim (HEAD)

Lua config under private_dot_config/nvim/. Highlights:

LSP set: ty, ts_ls, lua_ls, gopls, rust_analyzer, jsonls, yamlls, bashls, jdtls
Subprocess-safe: detects non-interactive sessions and disables clipboard provider (so nvim -c '...' +q in scripts doesn't hang on macOS pbcopy)
Plugin manager: lazy.nvim, pinned via lazy-lock.json
24-hour compinit cache; auto fpath discovery picks up new completions on next shell start

Why split this out

The portable write-code skill answers "what should this codebase look like?" That question is the same for everyone in the org. This skill answers "how is my personal machine wired up?" -- a question only I should be making decisions for, so the router shouldn't pick it for general code-writing requests.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.