nix-flake-organization

What problem does it solve?

This Skill helps refactor crowded Nix flake repositories into a cleaner structure where the public flake surface stays minimal and the real implementation lives in feature-oriented source files.

Core Features & Use Cases

• Thin Public API Layer: Keeps flake files focused on output wiring, imports, and compatibility aliases instead of build logic.
• Implementation Separation: Moves package, app, module, and helper logic into src paths organized by feature rather than by output type.
• Migration Guidance: Supports reorganizing flake-parts projects, NixOS modules, Home Manager modules, darwin modules, overlays, and shared utilities while preserving existing output names.
• Use Case: A repository with a large flake.nix can be split into a maintainable structure without breaking downstream consumers.

Quick Start

Ask the assistant to reorganize this Nix repository so the public flake surface stays thin in flake/ and the implementation moves into src/ while preserving the current outputs.