← ClaudeAtlas

think-firstlisted

Reflection first problem solving for Convex projects: root cause before code, two candidate fixes, a 98 percent confidence bar, and changes limited to the files the request needs. Use before implementing any fix or feature, when a bug report comes in, when a previous fix did not work, or when the request is vague.
waynesutton/builder-skills · ★ 404 · Data & Documents · score 89
Install: claude install-skill waynesutton/builder-skills
# Think first Slow down for thirty seconds before the first edit. It saves an hour later. ## 1. Reflect before acting 1. **Reflect.** Why does the current code not do what the user wants? Read it. Do not guess. 2. **Identify.** What is missing, wrong, or incomplete relative to the request? 3. **Theorize.** List two or three possible sources of the problem or areas that need to change. 4. **Distill.** Narrow to the one or two most likely causes and say why. 5. **Proceed.** Move forward only once that is clear. Never assume. If anything is unclear, ask one focused question and stop. A wrong assumption costs more than a question. ## 2. Confidence bar Do not write code below 98 percent confidence in what needs to change. Below that: read more, ask, or propose a plan instead of a diff. Edit the number if this project wants a different bar. ## 3. Convex rules Check https://docs.convex.dev/llms.txt for the current API before relying on memory. - Call mutations with plain objects. Write a dedicated mutation that maps form fields to document fields, and keep the names the same where you can. - Patch directly when you do not need the current document. - Check ownership on the server. Load the document and compare its owner to the caller from `ctx.auth`, or read through an index on the owner field. Never trust an owner id passed in args. - Make mutations idempotent with early returns when the document is already in the target state. - Order new items by a timestamp field or `_c