← ClaudeAtlas

think-twicelisted

Forces Claude to pause before picking an implementation approach and ask: "Is there a cleverer, cheaper way?" Triggers when the request involves generating data or fixtures (lists, datasets, sample records), implementing a problem that is likely already solved by a stdlib function, package, or public API (validation, parsing, lookups, auth, date/currency/geo data), or any implementation expected to exceed ~20 lines. Does NOT trigger when the user has explicitly chosen the approach or library, when the task is under ~10 lines, when fixing a bug in existing code, or for infra/terraform/k8s and DB queries. Run the checklist before writing code, stop at the first question that reveals a cheaper path, and take that path.
albertobarnabo/lazy-cat · ★ 35 · DevOps & Infrastructure · score 82
Install: claude install-skill albertobarnabo/lazy-cat
# Lazy Agent — Work Smarter, Not Harder > "A great engineer is a lazy engineer. They find the clever shortcut." — Steve Jobs This skill rewires Claude's default instinct. Instead of charging ahead with the most obvious approach, Claude must first ask: **"Is there a smarter way to do this?"** Productive laziness is not about doing less. It's about never doing more than necessary. --- ## When NOT to run this checklist Skip if the task is trivially small (under ~10 lines, no data, no new dependencies) or if the user has explicitly described custom logic that no generic library could cover. In those cases, proceed directly. Also: never hand-roll cryptography or security primitives. "Use an existing implementation" means the language stdlib or a widely-audited library — not a custom implementation. --- ## The Lazy Check Run this before any task that feels heavy — a large block of code, repetitive data, a complex algorithm, a long implementation. Stop at the first question that reveals a better path. ### 1. Am I solving the right problem? Before writing a single line, make sure the task is correctly understood. - What is the user *actually* trying to achieve? - Am I about to solve a symptom instead of the root cause? - Would a 2-sentence clarification save 200 lines of code? **If the answer to any of these is uncertain — ask the user before writing any code.** One targeted question now saves a full redo later. ### 2. Is there an existing solution? Someone has almost ce