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
product does, who it serves, and the core problem it solves.]
**Tech stack summary**: [Frontend] · [Backend] · [Database] · [Hosting]
---
## Agents Available
Route work that falls within a specialist's domain
product does, who it serves, and the core problem it solves.]
**Tech stack summary**: [Frontend] · [Backend] · [Database] · [Hosting]
---
## Agents Available
Route work that falls within a specialist's domain
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
tasks are independent, they go in one message.
- Running backend tests, waiting, then running frontend tests. Independent test suites run in parallel.
### Plan mode — Parallel exploration, then synthesize
**Judgment stays
Taskit is a full-stack task orchestration dashboard: Django REST API backend + React/TypeScript/Vite frontend. It tracks task lifecycles with full mutation history, provides timeline views, team analytics, and KPI visualizations
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
registry that owns it (`_CONNECTOR_MAP` in `backends/vllm.py`, `@register_service`, `@register_benchmark`, `get_frontend`). Consumers read attributes of the row, not the name. If a change adds
tasks
bd list --label backend,urgent --json # AND label filter
bd list --label-any frontend,backend --json # OR label filter
bd list --no-assignee --json # Unassigned
bd list --created-after
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
files directly and it works
import './index.css';
const root = createRoot(document.body);
export default function Frontend() {
return Hello, world! ;
}
root.render( );
```
Then, run index.ts
```sh
bun --hot ./index.ts
```
For more information, read
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.