wrapper-module

What problem does it solve?

This skill removes ambiguity and structural drift in wrapper modules by guiding creation, refactoring, and audits so that generic module.nix files remain reusable and local defaults stay repository-specific.

Core Features & Use Cases

• Audit Guidance: Step-by-step checklist to compare local wrapper options, naming, and implementation shape against BirdeeHub upstream idioms.
• Creation Workflow: Clear instructions for splitting a wrapper into a generic module.nix and a repo-specific default.nix using constructFiles, flags, env, passthru, and runShell only when justified.
• Decision Framework: Criteria for when to keep logic in module.nix versus default.nix, how to name options, and how to model writable runtime state safely.
• Use Case: Split an existing wrappers/foo.nix into wrappers/foo/module.nix and wrappers/foo/default.nix and update options to match upstream patterns while preserving necessary repo policies.

Quick Start

Audit the wrapper in wrappers/<name> and produce a concise plan to create or adjust module.nix and default.nix so they follow BirdeeHub wrapper-module conventions.