Enforce camelCase, kebab-case, and UPPER_CASE naming in Nix code.
npx skills add https://github.com/khaneliman/khanelinix --skill nix-naming
Please help me install this Agent Skill. Skill: nix-naming Source: https://github.com/khaneliman/khanelinix/tree/main/modules/common/ai-tools/skills/naming Command: npx skills add https://github.com/khaneliman/khanelinix --skill nix-naming
In Nix projects, inconsistent naming makes code hard to read, maintain, and collaborate on.
Apply the naming conventions to a sample Nix module to enforce camelCase for variables, kebab-case for files, and UPPER_CASE for constants.
High-intent search queries and answers about installing and using this skill.
To enforce consistent naming in Nix modules, apply specific style rules: camelCase for variables, kebab-case for filenames, and UPPER_CASE for constants. This reduces confusion and errors by validating code with a linter-like process to catch deviations.
The best way to name NixOS configuration files and variables is to use kebab-case for files and directories, camelCase for variables, and UPPER_CASE for constants. This ensures code remains maintainable and collaboration-friendly.
You need UPPER_CASE in Nix expressions specifically for constants and cfg patterns. Maintaining this predictable namespace pattern alongside camelCase variables and kebab-case files ensures clear configuration management across modules.
Yes, the naming convention linter validates Nix scripts automatically by applying a linter-like process to catch deviations from the specified style rules. It checks variables, files, and attributes to prevent inconsistent naming.
Inconsistent Nix code makes maintenance harder because mixed camelCase, kebab-case, and UPPER_CASE patterns reduce readability and create unpredictable namespaces. Enforcing specific style rules for variables, files, and constants solves this by catching deviations early.
elodin-sysManage and troubleshoot Elodin Nix development environments and NixOS configurations.
cjdutoitValidate C# source code for style rules, naming conventions, and comment formatting.
aytordevGenerate NixOS, Home Manager, and nix-darwin module templates with separated options and config.
oaknationalEnforce TypeScript coding conventions and project structure for Oak AI applications.
