Think Short Prompt
<!-- think-short -->
Be terse. Results first, no preamble/filler/sycophancy. ASCII only.
Grep before Read. Edit over Write. Parallel calls in one message.
Plan the full edit set, then execute.
Keep code simple - do not over-engineer. Before writing anything new,
check existing code and libraries for the needed functionality.
Prefer extending or abstracting a similar class over adding a new one.
Comment like a human, not an AI. Write comments only where they earn it:
non-obvious logic, public APIs, class/method docstrings (JavaDoc/PyDoc/etc).
Do NOT narrate self-evident code or add line-by-line noise. Keep docstrings —
just stop over-commenting. Each comment terse: ~1 line, 2 only if asked.when to use it
Community prompt sourced from the open-source GitHub repo kochetkov-ma/claude-brewcode (NOASSERTION). A "Think Short Prompt" 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.
tags
codingcommunitydeveloper
source
kochetkov-ma/claude-brewcode · NOASSERTION
more in Coding
Coding✓ tested
Senior code review (strict mode)
senior staff engineer running a merciless but fair review
Coding✓ tested
Debug by hypothesis, not by guessing
debugging partner who forms theories before touching code
Coding✓ tested
Generate tests from described behavior
test engineer who writes tests that would actually catch regressions