Enforce Nix naming conventions for variables, files, and attributes.
npx skills add https://github.com/aytordev/system --skill nix-naming-aytordev
Please help me install this Agent Skill. Skill: nix-naming Source: https://github.com/aytordev/system/tree/main/modules/common/ai-tools/skills/nix/naming Command: npx skills add https://github.com/aytordev/system --skill nix-naming-aytordev
Nix naming conventions and code style ensure consistent, readable configuration code across teams, reducing misinterpretation and integration errors.
Apply these guidelines by converting existing variables to camelCase, renaming files to kebab-case, and restructuring module attributes according to the recommended organization.
High-intent search queries and answers about installing and using this skill.
You can enforce Nix naming conventions by standardizing variables to camelCase, renaming files to kebab-case, and restructuring module attributes. This ensures consistent, readable configuration code across teams, reducing misinterpretation and integration errors.
The standard NixOS and Nixpkgs naming style uses camelCase for variables and kebab-case for files and directories. Applying these file naming standards and attribute organization checks improves Nix module structure and avoids cross-platform issues.
To convert existing variables to camelCase, apply the provided naming guidelines to your Nixpkgs configurations. You also rename files to kebab-case and restructure module attributes according to the recommended organization to enforce consistent style.
Yes, you can apply these Nix style guidelines directly in CI pipelines and onboarding workflows. The guidelines satisfy explicit frontmatter-driven naming rules, file naming standards, and section-based organization checks for team projects.
Nix attribute organization matters because it improves Nix module structure and readability. Enforcing consistent naming conventions and attribute organization across NixOS configurations ensures consistent code, reducing misinterpretation and integration errors.
The Nix naming rules focus strictly on variables, files, and attributes. They satisfy explicit frontmatter-driven naming rules, file naming standards, and section-based organization checks, but do not extend beyond these specific style guide constraints.
Dimon94Route user requests to the correct CC-DevFlow agents and commands.
stravinestCreate and maintain Claude skills with standardized SKILL.md templates and packaging.
cameronraysmithEnforce Nix development conventions for flakes, modules, and platform configurations.
knckknckStandardize Go code quality and style across projects.
