> ## 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.

# Quick start

> Submit a prompt, shape the plan, generate the prototype, and go full-stack — Archie's idea-to-app flow, end to end.

The fastest way to understand Archie is to run through it once. You create an account, describe the app, shape the plan Archie generates, click through a prototype of your screens, and then turn it into a real, deployed full-stack application.

<Steps>
  <Step title="Create your account">
    There are two ways in, and both start you on the **Free** plan with no credit card:

    * **Sign up at [app.archie.com](https://app.archie.com)** with Google, Microsoft, GitHub, or email. If you use email, open the verification link Archie sends before you build. Signing in with GitHub also makes GitHub sync smoother later.
    * **Start from a prompt at [archie.com](https://archie.com).** Type your idea into the prompt bar without an account. Archie remembers what you typed, creates your account when you finish signing in, and continues straight into plan generation — a good way to see what Archie does before you commit.

    Free includes 50 AI credits per month, unlimited plan and prototype projects, plan export as PDF, unlimited viewers, and Discord community support.
  </Step>

  <Step title="Submit your prompt">
    Type what you want to build into the prompt bar. One or two sentences that name the product and its users is enough — for example, "A scheduling app for hairstylists where clients book appointments by service and stylist."

    Archie may ask a few clarifying questions, and you can attach reference material to give it more context. See [Generating a plan](/docs/features/plan/generating).
  </Step>

  <Step title="Shape your plan">
    Archie generates a [plan](/docs/features/plan/overview) — the structured definition of your app:

    * **Overview** — what the app is for
    * **Modules** — the feature areas (e.g. Scheduling, Stylist profiles, Notifications)
    * **User types** — who uses the app and what each can do (e.g. Client, Stylist, Salon Admin)
    * **System services** — built-in services like authentication, file storage, and roles
    * **Integrations** — third-party services like Stripe, SendGrid, and Twilio

    A preview section shows sample screens so you can see how the plan becomes UI. Archie chooses and manages the tech stack for you, so it doesn't appear in the plan.

    Shape the app by editing the plan, not by re-prompting. Click into any [module](/docs/features/plan/editing-modules), [user type](/docs/features/plan/editing-user-types), [service](/docs/features/plan/editing-services), or [integration](/docs/features/plan/editing-integrations) to change it. For larger changes, use the [plan chat](/docs/features/plan/iterating) — describe the change in plain language and Archie applies it across the right sections.
  </Step>

  <Step title="Generate the frontend">
    When the plan is ready ([here's how to tell](/docs/features/plan/when-to-build)), click **Generate Frontend**. Archie first lays out the UI architecture: a sitemap of every screen your app needs, grouped by module and color-coded by who can access it.

    Review a screen's spec before it's built, then pick the screens you want and click **Generate**. The result is a click-through [prototype](/docs/features/frontend/prototype/overview) with your design system applied — real navigation, no real data yet. See [Generating the frontend](/docs/features/frontend/generating).
  </Step>

  <Step title="Generate the backend">
    Click **Generate Backend** to build your database schema and APIs on [Archie Core](/docs/features/backend/overview). The backend track doesn't depend on the frontend, so you can run it before, after, or alongside it.
  </Step>

  <Step title="Go full-stack">
    Once the prototype holds together, click **Generate Full-Stack**. Archie turns your prototype and plan into a real, deployed application: a React frontend on a global CDN, connected to a backend with a relational database, GraphQL and REST APIs, authentication, and role-based access.

    From there, keep building by [talking to Archie](/docs/features/frontend/talking-to-archie), with the [visual editor](/docs/features/frontend/visual-editor), or in the [code editor](/docs/features/frontend/code-editor).
  </Step>
</Steps>

<Note>
  Converting a prototype into a deployed application requires a paid plan. See [Plans and credits](/docs/introduction/getting-started/plans-and-credits).
</Note>

## FAQ

<AccordionGroup>
  <Accordion title="I never received my verification email. What should I do?">
    Check your spam folder first. If it's still missing after a minute, try signing in and use the resend link, or open the password reset flow — both send a fresh email. Corporate email filters sometimes block the first message.
  </Accordion>

  <Accordion title="I signed up with email but want to use Google instead. Can I switch?">
    Yes. Open [Profile and preferences](/docs/introduction/account/profile-and-preferences) and link a Google, Microsoft, or GitHub identity. Once linked, you can sign in with any connected provider — they all point to the same account.
  </Accordion>

  <Accordion title="I'm joining an existing organization. Should I sign up first or wait for an invite?">
    Either works. If you accept an invitation before creating an account, signup lands you straight on the organization's plan. If you already have an account, ask the admin to invite that same email and you'll join from your existing account.
  </Accordion>

  <Accordion title="What if my prompt isn't specific enough?">
    The plan is where Archie sharpens vague ideas. If your first prompt is light, Archie still drafts a reasonable structure, and you refine it from there — adding modules, renaming user types, swapping integrations. Editing the plan is faster and more accurate than re-prompting. See [Best practices](/docs/introduction/getting-started/prompting-best-practices).
  </Accordion>

  <Accordion title="Do I have to generate every screen at once?">
    No. Tick only the screens you want and click Generate. The rest stay pending, and you can generate them later, one at a time or in batches. Most builders generate a handful, check the pattern, then generate the rest.
  </Accordion>

  <Accordion title="Should I generate the frontend or the backend first?">
    Either order works — the two tracks don't depend on each other. Most projects start with the frontend to validate the screens and flows before wiring up real data.
  </Accordion>

  <Accordion title="What happens if generation fails partway?">
    The page shows the error and the credit usage. Your plan and anything already generated stay intact, and failed generations are not charged in full. Re-run the generation once you've checked the error.
  </Accordion>

  <Accordion title="Can I change the plan after I generate?">
    Yes. Edit the plan and generate again — the next build picks up your changes. For small changes to a running app, use chat or the visual editor instead.
  </Accordion>
</AccordionGroup>

## What's next

<CardGroup cols={2}>
  <Card title="Best practices" icon="lightbulb" href="/docs/introduction/getting-started/prompting-best-practices">
    How to prompt and shape a plan so the build lands close to what you want.
  </Card>

  <Card title="Frontend" icon="arrow-pointer" href="/docs/features/frontend/overview">
    Prototype, visual editor, code editor, theming, and deployment.
  </Card>

  <Card title="Backend" icon="database" href="/docs/features/backend/overview">
    Data model, GraphQL and REST APIs, environments, and settings.
  </Card>

  <Card title="Plans and credits" icon="receipt" href="/docs/introduction/getting-started/plans-and-credits">
    Pricing, AI credits, and Archie Core backend tiers.
  </Card>
</CardGroup>