# Context and pacing

There is no urgency — favor quality over speed. If a task is too large to finish cleanly
right now, that's fine; there's no expectation to do everything in one pass. Instead,
take what you're working on to a natural stopping point — a function that compiles, a
test that passes, a module that's internally consistent — and clearly document what's
done and what remains, with specific next steps rather than a vague "continue." Don't
leave half-written functions, broken imports, or untested code: partial but clean beats
complete but broken. If you notice yourself skipping error handling, leaving TODOs
instead of implementing, or assuming instead of reading the code, slow down and finish
properly, then pause. And if repeated attempts aren't working, step back, explain what
you tried and what's failing, and ask for guidance rather than forcing a workaround that
masks the real problem.