Using Claude Opus 4.7 at high effort. Elixir code test using the elixir-phase-skills and hooks per 30. April 2026. Highly automated implementation where RealWorld Conduit is used as the goal.
The prompts will be run as automatically as possible, and with no other input than accepting edits on the way.
The first prompt is a one-shot without any fixes or automated code reviews after.
The second prompt is automated code review and automated fixes to the first prompts code.
Prompt 1 :
[use-skills][TDD] Make a milestone plan to build real_world, a Phoenix backend implementing the RealWorld (Conduit) Medium-clone JSON API — users, profiles with follow, articles with tags and favorites, comments, and a personalized feed. Use Elixir 1.9+, Phoenix, Ecto and PostgreSQL (using Docker), JWT authorization, Bcrypt for passwords.
Conform exactly to the RealWorld API specification at realworld-docs.netlify.app— endpoint paths, JSON request/response shapes, status codes, validation-error format, JWT carried in theAuthorization: Token ` header.
Use the Elixir skill with architecture subskill to design a flexible architecture which is easy to change, extend and test. Use TDD during implementation, and make sure the code and architecture is idiomatic best-practice Elixir and conforming to good documentation standards. Keep the code and documentation concise yet easy to read, and add type specifications.
Plan controller-by-controller against the RealWorld Postman collection — auth + users → profiles + follow → articles CRUD + favorites + tags → comments → feed; TDD with controller tests asserting exact spec JSON.
Run the official RealWorld Postman suite as the final acceptance test. Report the degree of achieved compliance as a percentage.
Invoke all relevant skills and use the skills actively. Do not use agents for planning or implementing but do it all yourself. Do not leave implementations for later, cut corners or avoid or skip work. Do not guess or assume when facts or clear specifications are available. Make complete and high quality work.
Do not ask clarification questions on the way just finish it using your skills.
Document issues at the acceptance test, but do not fix.
Prompt 2 :
Archdo is at at /Projects/Archdo/ . Invoke the elixir-reviewing skill. Then use Archdo on this project to find issues, and the elixir-reviewing skill to evalute them. Keep a list of issues and add any issues from the previous acceptance test to them.
Do a manual review using elixir-reviewing skill. On the way look for code smells like try rescue and if else. Also look for code where pattern matching, enum, map and comprehensions would be more idiomatic best-practices.
Then run Credo on strict to check code quality.
Once all the issues has been found make a list of the issues named issues.md. Then make a complete milestone plan to fix all of them them while actively using the relevant skills. Implement all the fixes. Fix all issues flagged by Archdo and Credo.
Then run the official RealWorld Postman suite as the final acceptance test. Document issues at the acceptance test, but do not fix.
Result:
| Tool | Prompt 1 | Prompt 2 |
|---|---|---|
| mix test | 119/119 | 176/176 |
| mix compile | clean | clean |
| mix credo -strict | not run | 0 issues |
| Archdo | 54 findings. (1 warning, 17 info, 36 nitpicks). | 1 info. (Archdo bug) |
| RealWorld Postman acceptance | 23/134=17.2% | 311/311=100% |