Main

---
name: main
description: Use when working across more than one OMEGA framework, in the monorepo itself, or when the right home for a change is not yet known — which package owns a thing, the docs topology, the brand map, or where project state lives.
user-invocable: true
---

# OMEGA — the hub

The `@omega.js` framework ecosystem lives in ONE monorepo: npm workspaces under `packages/`, test brands under `brands/`, one family version bumped by hand. Start at the map, `docs/omega.md` (the repo-root `AGENTS.md` imports it and adds the hard rules: the legacy manager repos are read-only, and the seven publishables ship at one family version on Ian's word). This skill orients; every fact belongs to a guide below.

## The roster

| Package | Skill | Guide |
|---|---|---|
| `@omega.js/web` | `omega:web` | `docs/web/index.md` |
| `@omega.js/backend` | `omega:backend` | `docs/backend/index.md` |
| `@omega.js/desktop` | `omega:desktop` | `docs/desktop/index.md` |
| `@omega.js/extension` | `omega:extension` | `docs/extension/index.md` |
| `@omega.js/client` | `omega:client` | `docs/client/index.md` |
| `@omega.js/manager` | `omega:manager` | `docs/manager/index.md` |
| `@omega.js/devkit` | — | `docs/devkit/index.md` |
| `@omega.js/config` | — | `docs/shared/config.md` |
| `@omega.js/account` | — | `packages/account/src` |
| `@omega.js/template-kit` | — | `docs/web/template-kit.md` |
| `@omega.js/mcp-router` | `omega:browser` | `docs/mcp-router/index.md` |

Every framework ships the same context-aware `omega` / `omg` / `mgr` dispatcher: the nearest `package.json` walking up from cwd names the framework whose CLI runs.

## The docs topology

`docs/` is the SSOT. Cross-framework contracts are `docs/shared/*.md` — config, local-dev, testing, deploys, updates, publishing, icons, theming, translation, analytics, agent-docs, brands, rulings. Each framework's guide is `docs/<framework>/index.md` with its deep docs beside it, and the package's own `README.md` carries long-form detail. The four framework guides (web, backend, extension, desktop) mirror each other section for section — each guide's header states the rule.

The map is `docs/omega.md`, and every agent entry imports it: the repo-root `AGENTS.md` here, and in a brand the manager's one-line `AGENTS.md`, reached through `node_modules/@omega.js/manager/AGENTS.md`. The manager ships the whole `docs/` tree; no other package carries docs. The brand-root guide is `docs/manager/brand.md`; the contract is `docs/shared/agent-docs.md`.

## The brands

Brand work happens in one of four places — resolve which before touching files, never guess a path:

| Brand | What it is |
|---|---|
| `brands/sandbox-brand` | Synthetic fixture; test runs mangle and reset it |
| `brands/playground-omega` | "OMEGA Playground" — the standing live test brand, classy theme |
| `brands/newsflash-brand` | "The Daily Build" — the second-skin brand, newsflash theme |
| `../omega-omega` | The REAL brand, omegajs.dev — a sibling repo, LIVE |

Nothing in this monorepo is ever the production brand. Topology, history, and the local-era `file:` dependency contract: `docs/shared/brands.md`. Linking a brand against the local frameworks: `docs/shared/local-dev.md`.

## Inspecting a running system — grep the logs FIRST

Every OMEGA surface tees its whole run to a file, truncated on each launch: an app's `logs/dev.log` / `logs/build.log` / `logs/test.log`, a brand root's `logs/manage.log` (the manage walk) and `logs/dev.log` (the `omega dev` fan-out), the backend's `dist/emulator.log`, this monorepo's `.temp/logs/<lane>.log` (`grep '✗' .temp/logs/<lane>.log` names the failing case) and `.temp/logs/watch-all.log`, and each e2e lane's environment logs under `.temp/<lane>/`. Server state, build errors, test failures and emulator traffic are ALREADY on disk — never restart a dev server, emulator or watcher, and never re-run a suite, just to see output. The mechanism, the retention rule and the full path table: `docs/shared/logging.md`.

## Project state

Live work is GitHub issues (project-state spec v4): the queue is a query (`gh issue list`), status labels carry state, and a spec is the `## Spec` section of its issue — never a file. Shipped work is `CHANGELOG.md`; durable rulings from the retired board era are `docs/shared/rulings.md`.