Stacks
You describe language, framework, versions and check commands once in a stack profile, and every work step sticks to it. Java with Spring Boot is the most thoroughly travelled path; other stacks take the same path, they are just less travelled.
You wrote the target version into the rules file three times, and the agent builds for one you do not run. A stack profile ends that: language, versions and conventions stand in every prompt, and the gate commands say at the end whether the result passes them. Your project brings the build tools for that; the profile describes them, it does not install them.
| Stack | Status | What you need |
|---|---|---|
| Java / Spring Boot | Proven: the path Anvil Coder itself is built on. | Java and build-tool versions that match your repository. |
| PHP / Laravel | Proven in a reference run: fix and regression test in three commits. | PHP, Composer and the test runner in the sandbox. |
| TypeScript / Angular, Node.js, Python, Go | Configurable as a stack profile; no published run yet. | Your project's dependencies and build and test commands. |
Read the Laravel reference run, including what the sandbox could not check there.
A configured profile acts twice. Up front it is translated into conditions that accompany every prompt, the same mechanism as the guardrails. At the back stand the gate commands: the result has to pass them, otherwise the step does not count as done. You switch the rear check on separately per project.
A rule that only acts up front is a request. One that only acts at the back comes too late. Both together turn a declaration into a commitment.
The path on which Anvil Coder itself was built is Java with Spring Boot in a hexagonal architecture. Whoever starts there enters known terrain.
Other stacks work through the same path, they are simply less travelled. We will tell you honestly up front where you would be the first; that is cheaper for both sides than finding out afterwards. The system also works without a profile: the rules then come from the requirements and the guardrails.
How a run proceeds and how the per-run rules act is explained in the customer documentation (in German). Entry points: following runs andguardrails.