Stacks
With Anvil Coder the stack is not a built-in feature but a declared contract: you store language, framework, architecture, versions, conventions and check commands as a profile. Once set up, it acts at both ends — up front as a condition in every prompt, at the back as a gate the result has to pass.
The obvious question is "which frameworks are supported", and the honest answer is: that is the wrong question. A system that maintains a fixed list can do exactly what is on the list — and your stack is rarely on it in exactly that form.
Anvil Coder turns this around. Instead of building in knowledge about frameworks, it takes your declaration and makes it a condition. What you declare is what applies.
The profile is not restricted to a fixed framework list. The proven path is Anvil Coder's own stack: Java 25 with Spring Boot 4. Profiles for TypeScript with Angular, Node.js or Python projects can be stored just as well, provided you state language, framework, versions and check commands explicitly. The system ships no hidden project template for this, and therefore claims no certification of any particular framework.
"Supported" here means: the stack can be described as a contract and wired into the run. Whether a concrete repository with its dependencies, build tools and tests fits is decided by the stored project contract — not by a logo on this page.
The technical documentation (in German) explains the stack contract, the model strategy and the course of a run in detail. The most relevant entry points areStack-Vertrag und lernende Guardrails andWie ein Lauf abläuft.
Once a profile is set up, it 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. This rear check is enabled separately — the profile acts up front as soon as it is in place; the back needs a second switch.
A rule that only acts up front is a request. One that only acts at the back comes too late. Both together are the reason a declaration becomes a commitment.
The path on which Anvil Coder itself was built, and which has accordingly been walked most thoroughly, 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.
Stack profiles are an optional feature. Without them the system works as before — the rules then come from the requirements and the guardrails.