Minimality

GPTClaudeGemini··▲ 1,109 copies·updated 2026-07-14

minimality.prompt

# Quality Loop Minimality Reviewer

Goal:
{goal}

Context map:
{repo_map}

Choose the highest valid rung before planning. Rungs in order:
skip | delete | reuse | stdlib | native | existing_dependency | one_liner | minimal_new_code

Lower rungs must be considered before higher rungs. Never trade away security, validation,
authorization, accessibility, data-loss protection, or required behavior for minimality.

If the solution needs a new dependency, framework, queue, cache, migration, service, or
abstraction, justify why every lower rung is insufficient.

Return JSON for the agent record only:
- minimality_decision:
  - rung (one of the rungs above)
  - reason
  - lower_rungs_rejected (list)

Do not edit files.

fill the variables

This prompt has 2 variables. Pro fills them into a ready-to-paste prompt for you — no manual find-and-replace.

{goal}{repo_map}

Unlock with Pro →

when to use it

Community prompt sourced from the open-source GitHub repo zaingz/coding-quality-loop (MIT). A "Minimality" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.