feedback technically before implementing
### 7. Architectural Invariants
Before adding endpoints, services, DB tables, or frontend views, review the Architectural Invariants section in @docs/memory/architecture.md — the always-loaded core, which also carries
agent framework for building, deploying, and orchestrating intelligent workflows. It combines a Vue.js frontend, Express.js backend, and Electron shell to provide a cross-platform desktop application for managing AI agents
OpenAPI spec, memory system.
x-spaces/ → Low-level Puppeteer automation scripts (JavaScript, legacy).
public/ → Frontend HTML/CSS/JS for dev server (npm run dev). NOT used in production.
⚠️ Railway production serves from
make install # Install all dependencies
make dev-tmux # Run in tmux (recommended) - backend :8000, frontend :3000
make dev-tmux-kill # Kill tmux session
make checkall # Lint, typecheck, test all components
rust`
- For local packaging verification without macOS signing/notarization: `pnpm run tauri:build:debug`
## Logging
- **Frontend (renderer)**: Use `window.batAppAPI.debug.log(...)` instead of `console.log()`. This sends logs to the Tauri host logger, which
Claude Code (claude.ai/code) when working with code in this repository.
This is the frontend of Agentara (web/). See the parent ../CLAUDE.md and ../docs/overview.md for overall project context.
## Commands
```bash
Frame it as **"Here's what I'd build"** — not "here are your options."
- Frontend in scope? Use `ui-ux-pro-max` for palette, type pairing and component style;
`emil
powered by better-auth. In development, we have two components: apps/studio which is the frontend. And apps/gateway that's the backend.
You can start the frontend by running
while its inputs remain unchanged.
The implementer may update both source and tests; a frontend edit alone does
not require new E2E tests or a fixed sequence of specialist agents
paths for provisioned, serverless, and embedded Lite deployments.
## Commands
```bash
make build # All binaries + frontend + codegen
make generate # After OpenAPI/proto changes (SDKs, docs, protobufs)
```
## Testing
**Zig tests and E2E suites
Agent Notes
## What this directory is
TypeScript workspace for every Antfly frontend surface: the public SDK, unstyled
search primitives, the shared design system, the graph widgets, the npm CLI
wrappers
Development Standards
Zero-dependency Go HTTP server with embedded SPA frontend for OpenClaw bot metrics.
## Project Constraints
- **Zero third-party dependencies** — `go.mod` has no `require` block, no `go.sum
preview # Preview production build
# Type Checking
bun run typecheck # Run TypeScript type checking
```
## Architecture
### Frontend (Nuxt 3 + Vue 3)
**Pages** (`app/pages/`):
- `/agents` - List and manage agents
- `/agents/[slug]` - Edit individual
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.