blickflick

tools explained ·

[blickflick @blickflick_]

devenv part 8: a claude code hook that exits 1 only shows you a notice. exit 2 hands the failure back to the agent, after every edit and when it says it's done

[blickflick @blickflick_]

devenv part 7: a coding agent's commands get the environment it was started in, so start claude code inside the devenv shell and it gets the project's pinned tools

[blickflick @blickflick_]

devenv part 6: secrets without .env files. declare them with secretspec, everyone keeps their own value in their keyring, and only the command that needs one gets it

[blickflick @blickflick_]

devenv part 5: the same environment on every laptop and in CI. a test against a real database, the same command in github actions, the whole team on one version

[blickflick @blickflick_]

devenv part 4: scripts, tasks and git hooks in the same devenv.nix. name your commands, let setup steps run themselves, and block a bad commit before it lands

[blickflick @blickflick_]

devenv part 3: postgres, redis and your own server running next to the project. no containers, one command starts them all

[blickflick @blickflick_]

devenv part 2: languages and exact versions. pin python and node per project, or any tool at the version you need, without touching the rest of your machine

[blickflick @blickflick_]

devenv part 1: one file for your whole dev environment. install it, add a tool, and the environment switches on by itself when you cd into the project