Analyze** the objective and break it into specialized tasks
2. **Spawn** coordinated agents (backend → frontend → testing → documentation)
3. **Coordinate** agent dependencies and communication
4. **Monitor** progress through real-time agent
committing.
## Gotchas
- The test database resets between runs. Do not rely on seed data.
- Frontend environment variables need the `VITE_` prefix or they are not exposed.
## Compact instructions
When compacting
workspace-wide single-test shortcut. `cd` into the module directory and run:
```bash
cd frontend && go test -run TestMyFunction -v ./...
cd internal && go test -run TestSomething -v ./path/to/package/...
```
For integration
must keep this signature even when the current body is trivial:
```go
func (f *Frontend) newXxxAdmissionContext(
ctx context.Context,
op operation.Operation,
/* required inputs */ ...,
) (*admission.XxxAdmissionContext, error)
```
Keep `ctx` and the `error` return
metrics the charts query
Service metric names come from the services themselves, e.g. the frontend HTTP
metrics are defined in `frontend/pkg/frontend/metrics.go` (names in
`frontend/pkg/frontend/const.go`): `frontend_http_requests_total` (counter
test-integration
Artifact-driven integration tests for frontend, backend, and admin services. Tests run against a mock Cosmos DB by default.
## Directory Layout
```
test-integration/
├── admin/ # Admin API integration tests
agents. It's a full-stack monorepo with a FastAPI backend (`api/`) and Next.js frontend (`web/`).
## Development Commands
### Backend (api/)
```bash
cd api
# Install dependencies
uv sync # Using uv (recommended
binary into bin/hypitoken
make web-dev # Vite dev server with API proxy to :8317 (frontend hot reload)
make tidy # go mod tidy
make lint # all linters: golangci-lint (Go) + Biome
rozhraní a guardy, návrh API, automatika a vnější systémy, naming, git, bezpečnost, TypeScript, SQL, frontend) – načti si ho vždy, když navrhuješ datový model nebo píšeš či upravuješ kód; v doméně
bash SDK can be injected
(see **HTML Apps Runtime**)
- `/public/html-lib/` - Same-origin hosted frontend libs for HTML apps
(React, ReactDOM, Babel, `theme.css`, and the standalone
markdown / json / csv / pdf widget
managing Claude Code workspaces. It consists of:
- Node.js/Express backend server (REST API)
- React/Vite frontend (single-page application)
- CLI tool for workspace initialization and server management
## Common Commands
### Development
```bash
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.