> ## Documentation Index
> Fetch the complete documentation index at: https://docs.skarmy.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# How Skarmy works

> The two agents you talk to, the loop your company runs on, and how an idea moves from a sentence to a published site to a running business.

Skarmy is built around a loop, not a pipeline: an idea becomes a build, the build creates new tasks, done tasks improve the company, and the improvement suggests what to build next. You move through it by talking to two agents, each with a narrow job.

## The two agents

<Columns cols={2}>
  <Card title="The coach" icon="comments">
    The chat that follows you through the app — full-width on **Home**, a panel on the right everywhere else. It sharpens your idea, answers "what should we do today?", renames your company when you ask, remembers what you tell it, and works your connected apps. It never builds anything.
  </Card>

  <Card title="The Builder" icon="hammer">
    Lives in a workspace. Writes the actual product and proposes publishes. It never renegotiates the idea with you.
  </Card>
</Columns>

That split is deliberate. Thinking about what to build and actually building it are different jobs, and mixing them tends to produce a worse version of both.

<Note>
  These two are the only agents you talk to directly. The daily task suggestions and scheduled automations are Skarmy working in the background — they surface as cards and results, not as new conversations.
</Note>

## The path your idea takes

```mermaid theme={null}
flowchart TD
    A["You type an idea on Home"] --> B["The coach reacts<br/>and asks a question or two"]
    B --> C{"Concrete enough<br/>to build?"}
    C -->|"Not yet"| B
    C -->|"Yes"| D["The coach writes a brief<br/>and offers Open Builder"]
    D --> E["Workspace:<br/>the Builder builds it"]
    E --> F["You ask for changes"]
    F --> E
    E --> G["Publish to yourname.skarmy.ai"]
    G --> H["Daily tasks, inbox,<br/>apps, automations"]
    H --> F
```

### 1. You describe the idea

**Home** asks **What's your idea?**. Whatever you type opens a conversation with the coach. You can paste in a business plan, competitor copy, or notes — the coach treats all of it as material. Attach images or documents if they help; up to five per message.

### 2. The coach sharpens it

The coach behaves like a good early-stage sounding board. It reacts to your specific idea, then asks a question or two per reply, chosen for the answers that would most change what gets built first.

Two or three exchanges is normal. If you want to skip ahead, say so and it will hand off immediately.

### 3. The coach writes a brief

When the idea is concrete enough, the coach produces a short brief in your own language and offers an **Open Builder** button. The brief covers:

| Part of the brief   | What it captures                                                      |
| ------------------- | --------------------------------------------------------------------- |
| Working name        | What to call the product, in your words                               |
| What to build first | The concrete pages or flows for version one                           |
| Audience            | Who this first version is for                                         |
| The edge            | The sharpest insight from your conversation                           |
| Company fit         | Whether this belongs to your current company or is a separate venture |

The brief becomes the Builder's opening instruction. See [Describe your idea](/build/describe-your-idea).

### 4. The Builder builds

Accepting the handoff creates a workspace and opens it. The Builder scaffolds a web app, starts it running, and writes real pages and copy while you watch the preview pane.

It makes every technical decision itself and reports progress in product terms. It only asks you something when the answer would genuinely change what gets built.

### 5. You iterate by asking

Reply in the conversation. The Builder makes the change and the preview reloads. This is the loop you will spend most of your build time in.

### 6. You publish

Select **Publish**, claim your address once, and approve the exact version going out. Nothing deploys without your approval. See [Publish your site](/publish/publish-your-site).

### 7. Skarmy keeps working with you

After the first build, the rest of the app wakes up around your company:

* **Tasks** suggests a short slate of next steps every day, grounded in your business plan and what has actually happened. See [Daily tasks](/company/tasks).
* **Inbox** gives your company its own email address at `mail.skarmy.ai`. See [Your company inbox](/company/inbox).
* **Apps** connects Skarmy to the tools you already use, so you can ask it to work across them in chat. See [Connect your apps](/company/apps).
* **Automations** runs repeat work on a schedule — a morning note, an inbox catch-up, a weekly recap. See [Automations](/company/automations).

## What the Builder actually produces

The Builder writes a modern web app with real pages, real copy tailored to your idea, and a design chosen to suit your domain. It verifies its own work before reporting a milestone done.

What it deliberately does not do in a first version:

* Sign real customers up for accounts
* Wire third-party services into the product it builds
* Ship a native mobile app

One exception: if you have connected Stripe, the Builder can create a real payment link in your own Stripe account and put it on your site — so you can take money the day you publish.

If your idea is not a web product — hardware, a native app, an in-person service — the coach will say so and steer you toward the web version that proves the idea, such as a landing page with a waitlist or a booking flow with sample data.

## Where your work lives

| Surface                   | What it holds                                                  |
| ------------------------- | -------------------------------------------------------------- |
| **Home**                  | The composer that starts everything, and your Company Overview |
| **Workspaces**            | Every workspace in the current company, grouped by department  |
| **Tasks**                 | Today's suggested tasks and your board                         |
| **Inbox**                 | Your company's email                                           |
| **Automations**           | Work Skarmy does for you on a schedule                         |
| **Apps**                  | The tools connected to your company                            |
| **Search (⌘K)**           | Jump to any page, workspace, or task                           |
| **Usage** and **Billing** | Credits, plan, and payment                                     |
| **Settings**              | Company details and your account                               |

## Next

<Columns cols={2}>
  <Card title="Core concepts" icon="book-open" href="/concepts">
    How companies, workspaces, and sessions fit together.
  </Card>

  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Do the whole loop once, end to end.
  </Card>
</Columns>