custom solution — document-creation skills (`docx`, `xlsx`, `pptx`, `pdf`), visualisation tools, code execution, maps/places, frontend design guidance, and so on. If the task is "build a presentation", the `pptx` skill
Auditor)
You are an inflexible Quality Gate. You review all code written by Backend, Frontend, and Database Architects. If the code does not meet the following 3-tier validation criteria
changes |
| Playwright (default) | Verify UI changes render correctly; check console errors; screenshot before finishing frontend work |
| GitHub (default) | Issues, PRs, code search, prior art in this and related repos
architecture.
### [CRITICAL] no-typescript
**Rule:** Do not introduce TypeScript files — ReScript is the frontend language
**Why:** ReScript provides better type safety with less overhead. This is a deliberate, ecosystem-wide
Instructions
> **REPO REFACTOR — FOUR-STACK LAYOUT IN EFFECT.** The original single-stack
> tree (`backend/`, `frontend/`, `orchestrator/`, `infra/`,
> `docker-compose.yml` at the repo root) has been split into four
> independently deployable stacks
Basebuild planner may replace it in the future but is not
worth building today.
- **Frontend**: React 19 + TypeScript + Vite 7 (Tauri webview), Tailwind, xterm.js.
- **Desktop core**: Rust + Tauri
every feature or bugfix:
- Identify the changed surface before coding: `desktop` (Electron main process), `frontend` (Vue/TS UI), `engine` (AI engine), `electron` (IPC/preload), `docs`, or `CI`.
- Add same-area tests with
single test
uv run python -m pytest tests/test_api.py::TestMeetingsEndpoint::test_upload_unsupported_format -v
```
### Frontend (`frontend/`)
```bash
# Install dependencies
npm ci
# Run dev server
npm run dev
# Build
network calls.
- **`run`** — Long-lived Tauri GUI. Watches status file, emits events to WebView frontend. Auto-binds to the most recently updated session when launched without `--status-file`.
### Adapter system
protect against excessive calls
- Require realistic human timing for business logic flows
### V3: Web Frontend Security
#### V3.2: Unintended Content Interpretation
- Prevent browsers from rendering content in incorrect context using
language, distributed architecture:
- **Backend (Scala)**: Located in `scala/turnstile/` - Core MCP gateway and server management
- **Frontend (TypeScript/React)**: Located in `js/console/` - Web-based console UI
- **Protocol Definitions**: Located in `resources/proto/` - gRPC/Protobuf definitions
412mo agoReviewMountCreate a free account to mount