MfGames Project Setup Flake



An opinionated setup for projects using Nix flakes.

According to Larry Wall, there are three virtues of a great coder: laziness, impatience, and hubris.

Over the years, the complexity of being a developer has only increased. Fortunately (or unfortunately depending the mood), we have embraced laziness and developed tools to help automate some of the more tedious tasks to ensure everything is formatted correctly and properly recorded. This has resulted in libraries such as:

In addition, we need to document policies that guide our projects:

But, like the rest of the development world, all of these tools change and evolve. New tools become useful to ensure formatting while others are taken over by successors. Not to mention opinions and aesthetics change and what works yesterday doesn't always look right today.


This project is intended to be used with Nix flakes and can be used directly as an input.

  inputs.mfgames-project-setup.url = "git+";

This flake provides a function in mfgames-project-setup.lib.mkConfig that creates a shell hook and the various tools required to run those hooks (because programs like lefthook assume that the program is in the PATH).

config = mfgames-project-setup.lib.mkConfig {
    inherit system pkgs;
    # Options go here.

Of course, this being Nix, there are many ways of creating a devShell. This is one way of using the config inside the shell.

devShells = forEachSupportedSystem ({ system, pkgs }:
    config = inputs.mfgames-project-setup.lib.mkConfig {
        inherit system pkgs;
        conform.scopes = [ "cli" "website" ];
        rust.enable = false;
    default = pkgs.mkShell {
        # Add in the required packages for the configuration.
        packages = [] ++ config.packages;

        # Add in the
        shellHook = ''


This is definately opinionated, mainly by the virtue that is primarily used by a single developer. Internally, this uses Nixago (including a little hacking for text files).


Controls which scope is allowed inside the Conventional Commit.

Defaults to []. An example would be ["cli" "infra"].


If set to true, then a will be created using information from for the contact information. If the contact is missing, this will assert.

Defaults to false.

Set this to the value for the contact information inside the file. This can be an email or a website.


The copyright statement to include, if needed. This should be in the format of ", ". The “Copyright” and any symbols will be included if needed.


If set to true, then write out a Creative Commons BY-NC-SA license file to creativeCommonsAttributionNonCommercialShareAlike.filename.


The name of the file to emit.

Defaults to


If set to true, then write out a Creative Commons BY-SA license file to creativeCommonsAttributionShareAlike.filename.


The name of the file to emit.

Defaults to


If set to true, then a will be created using the boilerplate text from

Defaults to false.


If set to true, then write out a MIT license file to mit.filename. This requires copyright to be set because the resulting file will contain it.


The name of the file to emit.

Defaults to


Allows changing the proseWrap setting to one of the known values: preserve, always, never.

Defaults to preserve.


If set to true, then rustfmt.toml will be created.

Defaults to false.