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

# Editing modules

> Add, remove, and refine the modules in your plan.

Modules are the major features of your app — for example, "user accounts," "course catalog," "checkout," "admin dashboard." This page covers how to edit them.

## What a module looks like

Each module in the plan has a name, a short description, and a connection to the user types and services it uses. Modules are the building blocks the generator turns into pages, components, and APIs.

<img src="https://mintcdn.com/archie-e998dbf6/944gHGp2sN9dUVTM/features/plan/modules-card-entries.png?fit=max&auto=format&n=944gHGp2sN9dUVTM&q=85&s=28b8d9ae0a64570286545635a0867165" alt="Module entry with name, description, and supported user types" width="1440" height="900" data-path="features/plan/modules-card-entries.png" />

## Adding a module

1. Open the **Modules** card on the plan page.
2. Click **Add module**.
3. Type a name and a short description.
4. Save.

<img src="https://mintcdn.com/archie-e998dbf6/944gHGp2sN9dUVTM/features/plan/adding-a-module.png?fit=max&auto=format&n=944gHGp2sN9dUVTM&q=85&s=55cdc1185c0908c27d13d6bb7181a7bf" alt="Add module form with name, icon, and description" width="1440" height="900" data-path="features/plan/adding-a-module.png" />

The new module is wired into the plan immediately. The generator will pick it up on the next build.

## Removing a module

Click the module to open it, then delete. Removing a module also removes references to it from related sections — for example, if a user type's permissions referenced the module.

<img src="https://mintcdn.com/archie-e998dbf6/944gHGp2sN9dUVTM/features/plan/removing-a-module.png?fit=max&auto=format&n=944gHGp2sN9dUVTM&q=85&s=f0992b09313196637139377cdc047df9" alt="Module menu with Remove option" width="1440" height="900" data-path="features/plan/removing-a-module.png" />

## Refining a module

You can refine a module two ways:

* **Direct edit** — open the module, change its name or description, save. Best for small changes.
* **Plan chat** — describe what you want ("the checkout module should support guest checkout, not just logged-in users"). The chat updates the module in place. Best for substantive changes.

## Common patterns

* **Split** a vague module into two: "Account" → "User profile" + "Account settings."
* **Merge** two related modules: "Notifications" + "Email preferences" → "Notifications."
* **Rename** for clarity: "Admin stuff" → "Admin dashboard."
* **Drop** anything you do not actually need yet — building it later is easier than removing it later.

## FAQ

<AccordionGroup>
  <Accordion title="How many modules should an app have?">
    Most apps have between three and twelve. Anything beyond that suggests modules you should merge or features you can defer to a later build.
  </Accordion>

  <Accordion title="Will edits propagate to user types?">
    Edits do not auto-propagate. If you remove a module, check the related user types and update their permissions.
  </Accordion>
</AccordionGroup>
