test -v -coverprofile=cov.out ./...`; lint `golangci-lint run`; format `go fmt ./... && go vet ./...`.
- Frontend (React/Vite): `cd web && npm install`; dev `npm run dev` (port 3000); build `npm run build`; lint
Research and Assessment metrics
## Nav Tech Stack
- **Backend**: Kotlin with Ktor, PostgreSQL, Apache Kafka
- **Frontend**: Next.js 16+, React, TypeScript, Aksel Design System
- **Platform**: Nais (Kubernetes on Google Cloud Platform)
- **Auth
analyze pages in real time.
- 🧩 This is helpful to make sure all changes to frontend, actually work as intended.
= Use `ast-grep` in terminal instead of `grep` for code searches
express.js)
2. The UI (react)
3. The engine (plain TypeScript, runs in the frontend in the browser)
Business logic should be concentrated in the engine. The API should
defines the tech stack, project structure, state ownership rules, and development constraints for the frontend.
- **`.dev/specs/git-commits-rule.md`** — Read before generating a commit message. This file defines the Conventional Commits format, body
simpler alternatives, better naming, clearer structure
**Project patterns to enforce:**
- Angular signals for all frontend state (never RxJS BehaviorSubject for state)
- Branded types (SessionId, MessageId) — never raw strings
ONLY: reduce decimation target OR return file URLs. Do NOT touch grounding code, prompts, frontend grounding logic, or Hitem3D code to fix this. Isolate the fix to refine endpoint response
visual/browser-level layer that dev-kickoff-edho-ferdian's TEST stage explicitly defers… | `skills/e2e-testing-edho-ferdian/SKILL.md` |
| `frontend-engineering-edho-ferdian` | Authoring and configuration guidance for building React/Next.js frontend applications well from the start
wide guidelines. Path‑scoped files in `.github/instructions/*.instructions.md` provide focused guidance for specific areas (frontend, API, database).
## High-Level Architecture
TypeScript monorepo with:
- `api/` Express REST API (SQLite persistence, repository