Get pytest green
Run pytest tests/ -q in /home/piren/projects/GOFAI until exit code 0, ensuring .venv and dev dependencies are installed.
/goal pytest tests/ -q exits 0 in /home/piren/projects/GOFAI with a working .venv, and the transcript shows pip install -e ".[dev]" succeeded. Stop after 15 turns
claude-code
More testing loops
Ground a feature before you build it
Anchor one small feature in the current code, APIs, data contracts, and tests before implementing and verifying the user path.
Implement one bounded feature slice in [repository]. Read project instructions, the current implementation, relevant services, types, UI, tests, and architecture notes before editing. Report the evidence, risks, affected files, persistence impact, and validation plan; stop for approval if inspection materially changes scope or reveals destructive, production, or silent-persistence behavior. Make the smallest change, preserve unknown data and unrelated work, run relevant checks, and manually verify user-facing states. Stop after this slice and return evidence, limitations, and the next recommended slice.
testinghigh risk
Refactor in tested checkpoints
Reshape the architecture in small, independently reviewed steps — live-test, commit a checkpoint, and log progress each pass.
Refactor until you are happy with the architecture. After each significant step, live-test the system, run autoreview, and commit. Track progress in /tmp/refactor-{projectname}.md.
testingmedium risk
Trim what loads before first paint
Reduce the data downloaded before the first screen appears, with tests and screenshots guarding behavior and appearance.
Reduce the data [web app] downloads before its first screen appears. First record passing tests, mobile and desktop screenshots, and compressed transferred bytes—the data actually downloaded. Use the build report only to suggest candidates. Defer, compress, or remove one item, then rebuild and rerun every check. Keep it only if tests pass, screenshots are pixel-identical, and bytes decrease; otherwise revert. Stop when no safe candidate remains, progress stalls, or approval is needed. Return measurements, changes, and untested states.
testingmedium risk