dotfiles

Design or review domain models, APIs, state machines, wire contracts, and persistence schemas so invalid states are difficult or impossible to represent. Use when creating or changing lifecycle, status, error, request/result, Rust enum, TypeScript discriminated-union, or boolean/optional-field models.

Use when performing version-control work, including status inspection, diffs, checkpoints, commit descriptions, stack cleanup, splitting, squashing, rebasing mutable stacks, workspace management, or deciding whether jj or git commands are appropriate.

Manage Nix flakes, NixOS or nix-darwin configurations, Home Manager setups, package overlays, dev shells, and lockfiles. Use when Codex needs to inspect or modify `flake.nix`, `flake.lock`, `*.nix`, `home-manager`, `nixos`, `darwin`, `overlays`, `packages`, `checks`, or `devShells`, and when validating changes with `nix flake check`, `nix build`, `nix develop`, `home-manager`, `darwin-rebuild`, or `nixos-rebuild`.

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

A set of resources for building web based applications and the default architectural preferences that should be mmade for projects

Use when adding or reorganizing GNU Stow-managed dotfiles in this repo. Covers the local package layout conventions, when to use dot-config plus --dotfiles, and how Home Manager activation should target each package.