---
title: The entry point
description: "@be-category-name is the only way in. One command, working directory, team up."
---

# The entry point

There is one way in. You type the name of the area you want to work on, and
you are in it — right directory, team already running.

```bash
# ~/.zshrc
be-category-name() {
  cd ~/github/be-internal/docs/be-category-name && claude
}
```

Generate one for every area, so a new folder works the moment it exists:

```bash
for d in ~/github/be-internal/docs/be-*/; do
  n=$(basename "$d")
  eval "$n() { cd \"$d\" && claude; }"
done
```

## What happens when you type it

```text
  @be-category-name
        │
        ├─▶ cwd = that area's folder
        ├─▶ CLAUDE.md loaded, rules in effect
        ├─▶ five agents up: researcher · historian · librarian
        │                   designer · writer
        └─▶ advisor attached (advisorModel, from settings.json)
                    │
                    ▼
        write · research · diagram · commit · push
        all of it from here, without moving
```

No setup command, no briefing step, no checklist to run first. The entry
point *is* the setup.

## You work where you land

Everything happens in that directory: editing pages, analysing, asking the
researcher a question, committing and pushing. Push is the deploy — see
[editing the wiki](/handbook/editing-the-wiki).

Switching areas means typing a different name. That is the whole navigation
model.

## What is in scope

| Piece | Comes from | Scope |
|---|---|---|
| lead agent | session default | session |
| five agents | `be-internal/.claude/agents/` | whole repo |
| advisor | `advisorModel` in `.claude/settings.json` | session |
| rules | `CLAUDE.md` at repo root | whole repo |
| subject matter | the folder you landed in | this area |

The team is the same everywhere. What changes is what you are looking at.