What problem does it solve? Setting up a new project or retrofitting an existing repo with consistent tooling is repetitive and error-prone: reproducible installs, lint configs, test runners, and release automation all need wiring before real work starts. This Skill encodes opinionated, battle-tested defaults so every project gets the same solid foundation. ## Core Features & Use Cases - Reproducible installs: Enforces one documented command from clean checkout to working environment, with Nix devShell flakes for dependencies the language package manager cannot deliver (ffmpeg, Postgres, node itself). - Stack-specific conventions: Python projects get uv, ruff, ty, tyro, and pytest with Hypothesis property testing; Node/TypeScript projects get pnpm, strict tsconfig, node --test, and biome. - Makefile as the uniform interface: Standard targets (install, check, test, harden, fuzz, release-patch/minor/major, publish) so agents and humans answer "how do I check this project" by reading one file. - Use Case: Ask to set up a new Python CLI project and receive a uv-managed repo with a Makefile, ruff/ty config, property-test scaffolding, mutmut hardening config, GitHub repo creation, and a release pipeline. ## Quick Start Set up a new Python project with uv, a Makefile, linting, property-based tests, and a private GitHub repo.