brainstorming` before any new creative task. For aesthetic direction without brand context, invoke `Skill: frontend-design`.
## Agent-autonomy discipline (Phase 0 pre-flight)
**Before asking the user anything**, every workflow
cloned locally at `/Users/luqmannul.hakim/htdocs/9router`.
> For complete codebase mapping, Golang optimization standards, Svelte 5 frontend standards, standard Go unit testing conventions, and upstream sync protocols, **ALWAYS READ `AGENTS.md`**.
## graphify
This project
Backend Developer", "Build REST API with Express. Use hooks for coordination.", "backend-dev")
Task("Frontend Developer", "Create React UI. Coordinate with backend via memory.", "coder")
Task("Database Architect", "Design PostgreSQL
Detects listening dev servers on common ports
- `port-proxy.ts` - HTTP proxy for dev server preview
**Frontend (web/):**
- Vanilla JavaScript with xterm.js (CDN-loaded)
- `app.js` - Main client logic, WebSocket communication, terminal rendering
artifact both --install-deps --json
```
There is no separate lint/format config. Match surrounding style.
## Frontend
The dashboard source lives in `frontend/`. Vite builds into `kyoko/assets/web/`
so the Python package
stage afterwards. The `atomic serve` React app follows the same rule: `make -C atomic frontend` builds `atomic/internal/serve/frontend/dist/`, also gitignored, also a prerequisite of `build`/`test`/`vet`, also never staged.
**Failure
models while keeping data private. It's a desktop application (macOS/Linux) built with React frontend, FastAPI backend, and Tauri wrapper. Users can connect to databases (PostgreSQL, MongoDB, MySQL, SQLite), analyze
native Electron app. It uses a hybrid architecture: a **React 18 + Vite** frontend, an **Express.js** sidecar server, and an **Electron** desktop shell.
## Quick Commands
| Command | Purpose |
|---------|---------|
| `npm run dev:server
workspace with 4 crates, Ratatui (13-tab TUI), Axum (Web API backend), Leptos (WASM frontend), Arc + parking_lot for concurrency.
## Workspace Architecture
This is a Cargo workspace with a layered
Chinese locales (`zh*`) map to `zh-CN`; everything else maps to `en-US`.
- **Frontend**: `web/i18n.js` provides `t(key)`. HTML uses `data-i18n` / `data-i18n-placeholder`. Locale from `/api/status`, with browser
resume if still active.
**Crew grouping**: Config supports `crews` array to group teammates (e.g. frontend, backend). Use `--crew ` to filter commands.
Key rule: Only crew teammates use git worktrees. Regular
distributing Cursor AI rules, particularly focused on web development with strong emphasis on PHP/Drupal, frontend frameworks, and security best practices. The project provides an interactive PHP installer that allows developers
inline in `server.js`
- **CLI safety:** All commands use `execFile` (no shell) + `SafeSegment` input validation
- **Frontend:** Vanilla JS in `js/`, components render via innerHTML, global state in `js/state.js`
- **Real-time:** WebSocket
even for `.ts` sources.
- **Backend**: Express 5, better-sqlite3, run via `tsx` in dev.
- **Frontend**: vanilla TS + Vite. No framework, no CSS library. Keep it that way - the small dependency
should follow these guidelines.
## 🏗️ Project Structure
### Core Components
- **Backend** (`/backend/src/`) - Express.js server with TypeScript
- **Frontend** (`/frontend/src/`) - React.js with TypeScript
- **MCP Server** (`/mcp-server/src/`) - TypeScript MCP server for agent communication
- **CLI** (`/cli/src
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.