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

# Core concepts

> Companies, workspaces, departments, tasks, sessions, previews, and credits — what each one means in Skarmy and how they relate.

A handful of ideas explain almost everything in Skarmy. This page defines each one and shows where you meet it.

## Company

A **company** is the unit. Everything you do in Skarmy happens inside one: its workspaces, its tasks, its inbox, its connected apps, its business plan, its published sites. It has a name, and once the first build finishes, a one-line description and a cover image that Skarmy writes for you.

Every account gets a company automatically, called **Untitled Company** until you name it. You can create more from the company switcher at the top of the sidebar, and hold up to ten. The sidebar, tasks, files, and dashboard are all scoped to whichever company is currently active.

<Note>
  A company today belongs to one person — you. Team invites are coming with the Business plan, but there is no way to add another member yet.
</Note>

## Workspace

A **workspace** is one thing your company is making. Today that is a web app: your main product, a landing page for a campaign, a separate tool. A company can hold several.

Each workspace has its own conversation with the Builder, its own files, its own preview, and its own published address. They live on the **Workspaces** page, grouped by department, and your ten most recent appear in the sidebar under **Recent Workspaces**.

When the coach hands off an idea, it decides whether the idea is a new workspace in your current company or a genuinely separate venture that deserves its own company. Most ideas belong to the company you already have open.

## Department

Workspaces are grouped by **department**: Engineering, Design, Legal, Marketing, Hiring, Research, and Finances. A new workspace starts in Engineering; move it from the workspace's menu. Departments are how the Workspaces page stays readable once your company is making more than one thing.

## Task

A **task** is one concrete step for your company: publish your first version, share your site with three people, polish the website. Every day Skarmy generates a short slate of suggestions, grounded in your business plan and what has actually happened. You accept, edit, or dismiss them, and work accepted tasks on a board with three columns: **To do**, **Doing**, **Done**.

See [Daily tasks](/company/tasks).

## Brief

A **brief** is what the coach hands to the Builder: a short description of what to build first, who it is for, and what makes the idea distinct — written in your own language.

You never edit a brief directly. You shape it by what you say in the conversation before accepting the handoff. See [Describe your idea](/build/describe-your-idea).

## Session

A **session** is one continuous working relationship between you and the Builder in a workspace. It survives you closing the tab: come back tomorrow and the conversation, the files, and the built app are all still there.

Each workspace has one active session at a time. A session moves through a small set of states — building, waiting on you, asleep, finished — and the workspace tells you which one you are in. See [Session states](/account/session-states).

If you want to abandon everything and start over, **Start fresh** archives the current session and begins a new one on your next message.

<Warning>
  **Start fresh** cannot be undone. Use it when you want a clean slate, not when a build is merely slow.
</Warning>

### Sleeping and waking

Between turns, the machine running your build goes to sleep. This is normal and saves your credits. The preview shows `preview asleep`, and either **Wake preview** or your next message brings it back in seconds.

## Preview

The **preview** is the pane on the right of the workspace showing your app running live. It reloads itself as the Builder makes changes, so you see each edit land.

The preview is private and temporary — it is for you, while you work. It is not the address you share with anyone. For that you publish. See [Read the live preview](/build/live-preview).

## Published site

**Publishing** deploys your workspace to a permanent public address at `yourname.skarmy.ai`. You choose the name once, on your first publish, and it stays with that workspace.

A published site is a snapshot. It does not change when the Builder changes your app — it changes when you publish again, and every publish waits for your explicit approval. See [Publish your site](/publish/publish-your-site).

## Apps and skills

**Apps** are the third-party tools you connect to your company — Gmail, Stripe, Notion, Slack, and dozens more. Each app exposes **skills**, the individual actions Skarmy can take in it, and you can switch skills on and off per app.

Skarmy works your apps only when you ask, one action at a time, and can never delete anything in them. See [App permissions](/company/app-permissions).

## Credits

**Credits** are what building costs. One credit corresponds to one US dollar of usage. They are spent on three things: the Builder thinking and writing, the machine running your app while you work, and each publish.

Credits come from three pools, spent in this order:

1. **Daily** — a free allowance that refills every day
2. **Monthly** — included with a paid plan, refilling each billing cycle
3. **Top-ups** — credits you buy, which never expire

Talking to the coach is free. See [How credits work](/credits/how-credits-work).

## How they fit together

```mermaid theme={null}
flowchart TD
    A["Company<br/>(Kilnwork)"] --> B["Workspace<br/>(the studio site)"]
    A --> C["Workspace<br/>(workshop campaign)"]
    A --> T["Tasks, inbox, apps,<br/>automations, plan"]
    B --> D["Session<br/>(your conversation<br/>with the Builder)"]
    D --> E["Preview<br/>(private, live)"]
    D --> F["Files<br/>(what got written)"]
    D --> G["Published site<br/>(kilnwork.skarmy.ai)"]
```

## You versus the agents

Knowing who does what saves a lot of confusion.

| You decide                                      | The agents decide                         |
| ----------------------------------------------- | ----------------------------------------- |
| What the product is for                         | Which framework and libraries to use      |
| What it should say and show                     | How the code is structured                |
| Which of two options to take when asked         | Whether the build passes its own checks   |
| When to publish, and whether to approve it      | How to fix an error mid-build             |
| The company name and site address               | The design direction that suits your idea |
| Which tasks to accept and which apps to connect | Which task suggestions to draft each day  |

The Builder will not ask you about technical choices. If it asks you something, it is because the answer changes what gets built.

## Next

<Columns cols={2}>
  <Card title="Describe your idea" icon="comments" href="/build/describe-your-idea">
    Get a better brief out of the coach.
  </Card>

  <Card title="Glossary" icon="book-open" href="/account/glossary">
    Every term on one page.
  </Card>
</Columns>