Create and validate dotfiles font presets for nixpkgs attr paths and runtime family names.
npx skills add https://github.com/axelcool1234/.dotfiles --skill font-preset
Please help me install this Agent Skill. Skill: font-preset Source: https://github.com/axelcool1234/.dotfiles/tree/main/wrappers/code/skills/font-preset Command: npx skills add https://github.com/axelcool1234/.dotfiles --skill font-preset
This Skill removes guesswork when adding or updating font presets in the dotfiles repository by ensuring preset data matches runtime font family names, nixpkgs package attribute paths, and any required Kitty PostScript names so consumers and builds behave predictably.
Add or update a fonts/<preset-name>.nix file matching the repo's role schema, verify the packageAttrPath with nix search or MCP, confirm the runtime family name by building and inspecting the installed font files, check the PostScript name with fc-scan when needed, and run a nix eval plus a nix build to validate.
High-intent search queries and answers about installing and using this skill.
To verify nixpkgs font package attribute paths and runtime family names, you must resolve the attr path reliably and confirm the runtime family name by building the package and inspecting the installed font files. This ensures dotfiles presets match runtime behavior.
You validate Kitty PostScript names for terminal fonts by using the fc-scan tool to inspect installed font files. This optional verification step ensures the postscriptName recorded in your dotfiles font preset matches the actual font metadata.
The correct schema for dotfiles font presets mirrors the exact role and attribute footprint used by the repository, specifically covering ui, monospace, terminal, emoji, and symbols roles. This ensures consumers read consistent data from the fonts/*.nix files.
To validate Nix font presets and ensure system and wrapper builds work, you must perform at least one nix eval and one targeted nix build. This verification confirms that wrapper and host consumers will behave predictably with the updated preset data.
No, when adding a new Nerd Font preset you must determine the correct nested package attr path and build the package to confirm the displayed runtime family name from installed files. This manual inspection prevents consumer mismatches.
Nix dotfiles font presets cause unpredictable behavior in wrapper packages when preset data does not match runtime font family names or nixpkgs package attribute paths. Validating with nix eval and nix build resolves these consumer mismatches.
ruchernchongAdd, remove, or update packages in a Brewfile with correct types and alphabetical order.
ekala-projectEvaluate Nix expressions and inspect derivations using nix-instantiate and nix eval.
kimprobablyDiagnose and recover broken Spec Kitty installations using verification commands.
cslsoftwaresInspect and manipulate Delphi type information at runtime using RTTI.
