Skip to main content

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.

A blueprint is the structured plan for your app. Archie generates one from your idea. You edit it until it matches what you want. Then the build uses it as the spec. Editing the blueprint is where you spend most of your time. That is by design — the blueprint is cheap to change (it is structured text), the build is expensive. Steer the blueprint, then build once.

​
What is in a blueprint

A blueprint has six sections. Each is independently editable:
  • Overview — a high-level summary of the app’s purpose
  • Modules — the features and capabilities your app offers
  • User types — the people who use the app and what each can do
  • System services — built-in services like authentication, file storage, and roles
  • Integrations — third-party services your app talks to (Stripe, SendGrid, and so on)
  • Tech stack — the technical foundation (frameworks, runtime, database)
You will also see a Preview section with sample screens that visualize how the blueprint translates into UI.

​
How the blueprint relates to the rest of Archie

The blueprint is the high-level plan. The specifications hold finer-grained detail (system requirements, visual design principles, technical decisions). When you run the build, Archie reads the blueprint and the specifications together. After the build, the visual editor and frontend surfaces let you make small, direct changes. For larger changes, come back to the blueprint and rebuild.

​
What you will do here

​
FAQ

Yes. Edit and run again. The next build will incorporate your changes.
No. Each project has one blueprint. To explore alternatives, create a new project.
Leave it minimal. For example, an internal tool may not need integrations. Archie will not force features into your build.