Develop
Best practices
Ren Code does its best work when it understands what you want and can verify the result. A few habits make every change more reliable.
Describe intent, not keystrokes
Tell Ren Code the outcome you want and the constraints that matter — the behavior to preserve, the edge cases to handle, the parts of the system to avoid. Astra reasons about the change from there, rather than being walked through it line by line.
Let it analyze before it acts
On an existing repository, give Astra the chance to understand the codebase first. The more it knows about your architecture and conventions, the better its changes fit.
Keep changes reviewable
- Prefer focused requests that map to a single pull request over sprawling, multi-feature asks.
- Keep your tests and checks in place — they are how both you and Astra confirm a change is safe.
- Read every diff. Review is the safeguard, and Ren Code is designed around it.
Scope access deliberately
Grant repository access per repo, and only where you want Ren Code working. Narrow scope keeps the model focused and keeps you in control of what it can see.