InnerVault

Makefile taste

Indexedprompts.chat (CC0 prompt collection), f

# Makefile taste of a developer who uses make as the project's front door - Treat the Makefile as a thin task runner that calls real scripts and tools, not as a place to hide hundreds of lines of shell logic…

Open the source (opens github.com) https://github.com/f/prompts.chat

What it is

Prompts from f.

The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.

The prompt

# Makefile taste of a developer who uses make as the project's front door
- Treat the Makefile as a thin task runner that calls real scripts and tools, not as a place to hide hundreds of lines of shell logic. Confidence: 0.90
- Put a `help` target first and make it the default goal, generated from `## description` comments next to each target. Confidence: 0.85
- Declare every non-file target in `.PHONY` so a stray file named `test` or `build` never silently skips a task. Confidence: 0.95
- Set `SHELL := bash` and `.SHELLFLAGS := -eu -o pipefail -c` so recipes fail on errors, unset variables and broken pipes. Confidence: 0.85
- Add `.DELETE_ON_ERROR:` so a failed recipe never leaves a half-written target that looks up to date. Confidence: 0.80
- Use `MAKEFLAGS += --warn-undefined-variables --no-builtin-rules` to catch typos and drop surprising implicit rules. Confidence: 0.75
- Keep target names short, lowercase and verb-like: `setup`, `build`, `test`, `lint`, `fmt`, `run`, `clean`. Confidence: 0.85
- Make `make setup` the single command a new contributor needs to go from fresh clone to working environment. Confidence: 0.90
- Use `?=` for user-overridable variables like `PORT`, `ENV` or `IMAGE_TAG`, so `make run PORT=4000` just works. Confidence: 0.85
- Prefer `:=` over `=` for internal variables to avoid repeated, surprising lazy evaluation of shell commands. Confidence: 0.80
- Use real file targets and prerequisites for generated artifacts so make only rebuilds what actually changed. Confidence: 0.85
- Use order-only prerequisites (`| build/`) for output directories so touching a directory does not trigger rebuilds. Confidence: 0.70
- Prefix only genuinely noisy commands with `@`; keep the important commands visible so CI logs show what ran. Confidence: 0.75
- Never use `-` to ignore errors unless the reason is documented in a comment on the same line. Confidence: 0.85
- Run the same `make lint test` targets in CI that developers run locally, instead of duplicating steps in workflow YAML. Confidence: 0.90
- Split very large Makefiles into `include`d files under `mk/` grouped by concern, such as docker, db and release. Confidence: 0.65
- Use tabs for recipe lines and set `.editorconfig` accordingly so editors never turn them into spaces. Confidence: 0.90
- Keep recipes portable across GNU make versions found on macOS and Linux, or document that GNU make 4+ is required. Confidence: 0.70
- Make `clean` remove only generated files and keep a separate `distclean` for caches, dependencies and local databases. Confidence: 0.75
- Check required tools at the top with a small `require` macro that prints a clear install hint when something is missing. Confidence: 0.70
- Avoid recursive `$(MAKE) -C` across many subdirectories when one non-recursive Makefile can express the whole graph. Confidence: 0.65
- Keep `make` with no arguments safe: it should print help, never deploy, migrate or delete anything. Confidence: 0.95

Written by the prompts.chat (CC0 prompt collection) community (f). Not tested by InnerVault.

How to get it

Setup steps: not applicable.

Related

  1. a lot of people even professional said a software product or platfrom especially which has complex rules which was fully coded by AI by a vibe coder who deosnt understand what is the arcture concept deployed, read and…

    Indexed hussen.sepa@gmail.com · via prompts.chat (CC0 prompt collection) CC0-1.0

  2. code-hacker

    Prompts

    Code Hacker - VS Code Custom Agent + Web + TUI

    Stale hackerlibs · via GitHub 55 ★MITUpdated 20 days ago

    Source for code-hacker (opens github.com) git clone https://github.com/hackerlibs/code-hacker.git
  3. builder prompts which can be sent to builders like cursor, bolt.diy, bolt.new, trae, project idx, Claude code, lovable.dev, llmacoder, geminicoder, windsurf, deepseek-artifact, cline, aider etc

    Stale KingLeoJr · via GitHub 278 ★MITUpdated 2 months ago

    Source for awesome-vibe-coding-prompt-code-templates (opens github.com) git clone https://github.com/KingLeoJr/awesome-vibe-coding-prompt-code-templates.git
  4. Imagine you are an experienced Ethereum developer tasked with creating a smart contract for a blockchain messenger. The objective is to save messages on the blockchain, making them readable (public) to everyone…

    Indexed ameya-2003 · via prompts.chat (CC0 prompt collection) 177.9k ★CC0-1.0

  5. Manim Code

    Prompts

    Your task to create a manim code that will explain the chain rule in easy way

    Indexed industry5designers@gmail.com · via prompts.chat (CC0 prompt collection) CC0-1.0

  6. I’m tired of using Claude Code to build my code because of tokens limits can Ollama build code scripts agentic workflow?

    Indexed BuiltByPhil · via prompts.chat (CC0 prompt collection) CC0-1.0