← ClaudeAtlas

aeolus-fleet-consolelisted

Mandatory with web-frontend for changes under packages/console. Where the console's look and rules come from.
ThomasHendrickx/aeolus-fleet · ★ 0 · AI & Automation · score 64
Install: claude install-skill ThomasHendrickx/aeolus-fleet
# Console in aeolus-fleet Load with `web-frontend`. - The console is `argo`. Plugin calls and parsing their answers run on the web app's server or behind tRPC (decision 0033). The browser imports from `common` only types and `@aeolus-fleet/common/rules`; never zod. - Folders: as CLAUDE.md (Web) states; shared non-UI code sits in the console's root `lib/`. The old-layout features are the ones in `featuresInTheOldLayout` (`eslint.config.js`); the change that moves one drops it from the list. - Look from `docs/design/` (read `conventions.md` and `console-conventions.md` first, then only the parts you build), behaviour from the blueprint. Theme from `@aeolus-fleet/ui`'s `theme.css`, over `tokens.css`, the single copy of the tokens; the header and its atoms (Button, DropdownMenu, Sheet, Dialog, Avatar, Kbd, Tooltip) come from `@aeolus-fleet/ui`, by its entry only. A part a second app shows too moves to ui (`aeolus-fleet-ui`). - API client: tRPC; hooks such as `useFleetSnapshot`, in `lib/` when several features use them. shadcn/ui on Base UI. A route's client part sits beside its server `page.tsx`, such as `(console)/inbox/inbox-page.tsx`; signed-in pages sit in the `(console)` route group, whose layout holds the ConsoleFrame and hands each page `useConsoleFrame()`. Enforced by lint (`eslint.config.js`): layer imports, shared code never importing a feature or `app/`, no feature importing another, a new feature's folders, no tRPC or hooks in shared components or a feature's `ui/`