| ▲ | xtiansimon 3 hours ago | |
I’m getting into the agentic coding (I know, late to the party, and that’s been a good spot for my experience and use case), so I’m reading with interest. The first tip: “give Claude a way to verify its own work”. So what’s the recommendation for Claude to have a feedback loop? Because it’s not what follows in the article: _“Explore, then plan, then code.”, “Use plan mode…”, “Reference, do not describe.”_ | ||
| ▲ | pramodbiligiri an hour ago | parent | next [-] | |
Have tests, provide screenshots (or enable it to navigate the UI): https://code.claude.com/docs/en/best-practices#give-claude-a... | ||
| ▲ | sebmellen 3 hours ago | parent | prev | next [-] | |
In my experience, the biggest benefit comes from having good quality integration and unit tests that are easy for the agent to run on its own to verify its work against. | ||
| ▲ | kingkongjaffa 2 hours ago | parent | prev [-] | |
Typically for most code it's telling claude how to run tests. For front end code it's giving claude a way to 'see' the work for example a Playwrite MCP server seems common. https://playwright.dev/docs/getting-started-mcp | ||