nix-naming

Name: nix-naming
Availability: InStock
Author: aytordev

Enforce Nix naming conventions for variables, files, and attributes.

1|Updated Jun 2, 2025

Search Tags:#nix #camelcase #kebab-case #naming #nixos #style-guide #attribute-organization

Ready to run

npx skills add https://github.com/aytordev/system --skill nix-naming-aytordev

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Nix naming conventions and code style ensure consistent, readable configuration code across teams, reducing misinterpretation and integration errors.

Core Features & Use Cases

Standardize variable naming to camelCase for clarity and consistency.
Enforce kebab-case file and directory naming to avoid cross-platform issues.
Provide guidance for attribute organization to improve Nix module structure.

Quick Start

Apply these guidelines by converting existing variables to camelCase, renaming files to kebab-case, and restructuring module attributes according to the recommended organization.

Frequently Asked Questions about nix-naming

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce consistent Nix naming conventions in a team project?▼

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.

What is the standard naming style for NixOS and Nixpkgs file attributes?▼

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.

How do I convert existing Nix variables to camelCase and restructure module attributes?▼

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.

Can I use these Nix style guidelines in CI pipelines and onboarding workflows?▼

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.

Why does Nix attribute organization matter for module structure?▼

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.

What are the limitations of applying frontmatter-driven Nix naming rules?▼

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.