Skip to main content
prompt GP ChatGPT

Nix Dev Environment taste — ChatGPT prompt: what it does

Nix Dev Environment taste — a prompt for ChatGPT configures reproducible Nix development environments with locked dependencies and container builds.

CC0-1.0 ★ 178,201 updated 2026-10-24

Open on GitHub

What Nix Dev Environment taste does

This prompt sets platform engineering standards for working with Nix, flake.lock, and development shells. It pins exact compiler and runtime versions, supports both x86_64-linux and aarch64-darwin, and defines rules for building container images using dockerTools or nix2container.

The template helps organize linters like statix and deadnix in CI, run tests via nix flake check, and manage secrets using sops-nix or agenix instead of storing them in the world-readable Nix store.

What it helps with

  • lock Nix package versions
  • configure direnv shell loading
  • build container images from flakes
  • manage secrets with sops-nix
  • run tests via nix flake check

Example prompts for the agent

  • Apply Nix Dev Environment taste standards to flake.nix
  • Set up a reproducible environment using Nix Dev Environment taste

How to install Nix Dev Environment taste

How to use

Paste the text at the start of a chat or into project instructions

Questions about Nix Dev Environment taste

How to install Nix Dev Environment taste in Claude Code?

Add the file to your project at .claude/commands/prompts.csv.md.

What does Nix Dev Environment taste do?

It provides engineering standards and best practices for creating reproducible development environments using Nix and flakes.

What tools are integrated in the prompt?

The prompt references direnv, nix-direnv, Cachix, sops-nix, and agenix.

Source text

prompts.csv · CC0-1.0
# Nix Dev Environment taste of a reproducibility-minded platform engineer
- Pin nixpkgs through a flake.lock committed to the repo, and update it on purpose in its own pull request. Confidence: 0.95
- Expose the project shell as a devShell in flake.nix so `nix develop` gives every contributor the same toolchain. Confidence: 0.90
- Load the dev shell automatically with direnv and nix-direnv, and commit a one-line .envrc that only says `use flake`. Confidence: 0.85
- Keep language dependencies in the language's own lockfile (package-lock, uv.lock, Cargo.lock) and let Nix supply only the toolchain and system libraries. Confidence: 0.80
- Pin exact compiler and runtime versions, such as nodejs_22 or python312, instead of the unversioned default attribute. Confidence: 0.90
- Use flake-parts or a small hand-written per-system helper instead of copying the same outputs block for every architecture. Confidence: 0.70
- Support both x86_64-linux and aarch64-darwin from day one, since half the team is usually on Apple Silicon. Confidence: 0.85
- Format Nix files with nixfmt and lint them with statix and deadnix in CI. Confidence: 0.80
- Run `nix flake check` in CI and put tests, linters and format checks under checks so one command validates everything. Confidence: 0.85
- Use a binary cache such as Cachix or an S3 cache for CI, so contributors download builds instead of compiling them. Confidence: 0.85
- Build container images with dockerTools or nix2container from the same flake instead of keeping a separate Dockerfile in sync. Confidence: 0.70
- Avoid `with pkgs;` across large scopes and list packages explicitly so readers can see where each name comes from. Confidence: 0.75
- Keep overlays few and small, and write a comment explaining why each override exists and when it can be removed. Confidence: 0.85
- Put secrets in sops-nix or agenix and never in the Nix store, because everything there is world-readable. Confidence: 0.95
- Set up shell hooks only for fast, idempotent work like exporting variables, never for installs or migrations. Confidence: 0.80
- Prefer `nix run` apps for project tasks, such as running the database locally, over README instructions people forget. Confidence: 0.70
- Keep a short fallback section in the README for people who cannot install Nix, listing the exact tool versions the flake provides. Confidence: 0.75
- Garbage-collect old generations on CI runners and dev machines on a schedule so the store does not fill the disk. Confidence: 0.70
- Avoid impure builds and `--impure` flags; if something needs the network, make it a fixed-output derivation with a hash. Confidence: 0.85
- Explain the lock update in the commit message, including which inputs moved and why. Confidence: 0.75

© f · CC0-1.0 · f/prompts.chat

Similar prompts

All prompts for DevOps and infrastructure →

From the same set218

The whole set →
Ansible Playbook taste Ansible Playbook taste — a prompt for ChatGPT, Claude.ai, and Claude Code setting standards for infrastructure code. It aligns Ansible roles with best practices and ensures task idempotency. GP ChatGPT ★ 178,201repo stars Embedded Firmware taste Embedded Firmware taste — a prompt for ChatGPT that enforces reliability-minded engineering standards for embedded firmware development. GP ChatGPT ★ 178,201repo stars WebAssembly Module taste WebAssembly Module taste — a system prompt for ChatGPT, Claude.ai, and Claude Code that establishes architectural standards for WebAssembly development. It guides developers on performance and safety best practices. GP ChatGPT ★ 178,201repo stars Incident Response taste The Incident Response taste prompt for ChatGPT sets out how a calm on-call engineer can handle incidents. It calls for early declaration and coordinated response before the root cause is known. GP ChatGPT ★ 178,201repo stars Astro Content Site taste The Astro Content Site taste ChatGPT prompt sets out development rules for content sites built with Astro. It covers rendering, images, SEO, and CI checks. GP ChatGPT ★ 178,201repo stars Phoenix App taste Phoenix App taste — a prompt for ChatGPT, Claude.ai, and Claude Code that enforces engineering standards for Elixir and Phoenix applications. It defines architectural patterns, database operations, and testing strategies. GP ChatGPT ★ 178,201repo stars gRPC Service taste The gRPC Service taste prompt for ChatGPT sets design guidelines for gRPC services. It covers .proto schemas, RPC methods, errors, and calls between services. GP ChatGPT ★ 178,201repo stars Spring Boot Service taste ChatGPT prompt Spring Boot Service taste defines architecture standards for Java backend engineering. GP ChatGPT ★ 178,201repo stars

Project sponsors

Companies that keep this analytics open