Finding signal on Twitter is more difficult than it used to be. We curate the best tweets on topics like AI, startups, and product development every weekday so you can focus on what matters.
By story 10, Ralph knows patterns from stories 1-9.
Two places for learnings:
progress.txt — session memory for Ralph iterations
AGENTS.md — permanent docs for humans and future agents
Before committing, Ralph updates AGENTS.md files in directories with edited files if it discovered reusable patterns (gotchas, conventions, dependencies).
5. AGENTS.md Updates
Ralph updates AGENTS.md when it learns something worth preserving:
6. Browser Testing
For UI changes, use the dev-browser skill by @sawyerhood. Load it with `Load the dev-browser skill`, then:
Not complete until verified with screenshot.
Common Gotchas
Idempotent migrations:
Interactive prompts:
Schema changes:
After editing schema, check:
Server actions
UI components
API routes
Fixing related files is OK:
If typecheck requires other changes, make them. Not scope creep.
Monitoring
Real Results
We built an evaluation system:
13 user stories
~15 iterations
2-5 min each
~1 hour total
Learnings compound. By story 10, Ralph knew our patterns.
When NOT to Use
Exploratory work
Major refactors without criteria
Security-critical code
Anything needing human review
For a great video walkthrough of how to use Ralph, checkout the video from @mattpocockuk ...
