Specifications are what code generation reads. When you click Generate, Archie’s build agents read the entire specification set and produce frontend, backend, or full-stack code based on the stack you picked.Documentation Index
Fetch the complete documentation index at: https://archie.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
The whole spec set, one generation
Code generation is not run per spec type. There is no “generate just visual design” or “regenerate just functional design” mode. The agents need the full picture to generate consistent code. The split happens on a different axis: the stack you pick at generation time.| Stack | What it generates | Reads from specs |
|---|---|---|
| Full-Stack | Frontend, backend, APIs, and database schema | All spec groups (Functional, Visual, Technical) |
| Frontend-Only | UI components, pages, client-side routing | Functional (user types, features) + Visual + Technical (strategy) |
| Backend-Only | APIs, services, database schema, server logic | Functional (features, requirements) + Technical (strategy, data model) |
When edits affect code
Spec edits don’t touch existing code until you re-run generation. Editing the data model, adding a feature, swapping a UI framework — all of these queue up for the next generation pass. A few edits are exceptions and apply immediately:- Toggling a system service that has runtime configuration (e.g. enabling SMS) takes effect once the corresponding integration credentials are set
- Changes in the Data Model editor commit to the database via tracked migrations rather than going through code generation
What gets regenerated vs. preserved
Archie tries hard to preserve hand edits in non-generated files. Edits inside generated files may be merged or overwritten depending on the change. The build view shows a diff before applying so you can review what’s about to happen. For protected work — custom logic in custom functions, hand-written tests, your own utility files — keep them outside the generated paths and Archie won’t touch them.Generation phases
A typical full-stack generation moves through these phases:- Queued — generation request accepted
- Initializing — agents load the spec set
- Configuring foundations — base config, dependencies, scaffolding
- Generating — agents write code module by module
- Building — the generated code compiles and tests run
- Completed (or Failed with a reason)
FAQ
Can I regenerate just one feature?
Can I regenerate just one feature?
Not as a separate generation type, but you can edit one feature’s spec and run a regular generation — the agents focus changes on the affected files. Most generations are partial in practice.
What if I want to start over?
What if I want to start over?
Re-running generation from scratch is supported, but most builders find it faster to edit specs and run incremental generations. The exception is if your blueprint drifts far from your intent — then start from a refreshed blueprint.
Do spec edits cost AI credits?
Do spec edits cost AI credits?
No. Editing specs is free. Code generation is what consumes credits — the generation cost depends on the stack (Full-Stack, Frontend-Only, Backend-Only) and the size of your spec set.
What happens to my generated code if a generation fails partway?
What happens to my generated code if a generation fails partway?
Existing code stays intact. The new generation either completes or rolls back — you don’t end up with a half-applied diff. Open the activity feed to see why generation failed.