# Project AGENTS Router

Root `AGENTS.md` is a navigation and global-constraint layer only.
Do not place backend/frontend implementation details here.

## Rule Order

Apply rules in this order:

1. System/developer/platform safety instructions
2. Workspace global runtime rules (`AGENTS.md` and `rules/*` in workspace runtime config)
3. This file (routing + project-wide constraints)
4. Domain sub-rules:
   - `backend/AGENTS.md`
   - `apps/AGENTS.md`

If two rules conflict, use the stricter one.

## Mandatory Routing

- Any change under `backend/**` MUST follow `backend/AGENTS.md`.
- Any change under `apps/**` MUST follow `apps/AGENTS.md`.
- Cross-domain changes MUST satisfy all relevant sub-AGENTS together.
- Infrastructure-only changes under `infra/**` follow this file plus `infra/` conventions.

## Development Context Mapping

| Context | Required Rule Set |
|---|---|
| Backend Python/FastAPI | `backend/AGENTS.md` |
| Flutter mobile app | `apps/AGENTS.md` |
| Backend + Flutter in one task | `backend/AGENTS.md` + `apps/AGENTS.md` |
| Infra/ops scripts | This file + `infra/` conventions |
| API contract/doc updates | Also sync `docs/runtime/runtime-route.md` |

## Project-Wide Constraints

- Default branch is `dev`; never develop directly on `main`.
- Preferred feature workflow: `git worktree add -b feature/xxx ../feature-xxx dev`.
- Never push remote changes unless the user explicitly requests it.
- Keep AGENTS chain lean: put domain details in sub-AGENTS, avoid duplicate rules across layers.

## Skills Index

- `ag-ui`: AG-UI protocol implementation guidance.
- `agentscope-skill`: AgentScope framework guidance.

Skill invocation and process routing are governed by workspace runtime rules.