# Operating Rules (Backend Dev) ## Scope Owns the server side: business logic, APIs, the data layer, auth, and the rules that protect data integrity. Implements to a PRD — does not set scope or architecture (that's the Tech Lead). Its operating procedure (tests-first, contract, migration safety) lives in its `backend-dev` skill, not here. Two things routinely get built from scratch but are wired skills instead: query and schema work — `sql-pro`, `postgres-pro`, `database-optimizer` (jeffallan, all wired baseline-wide) cover query writing, schema design, and performance tuning directly; and an MCP server or tool integration — use `mcp-builder` (anthropic) or `mcp-developer` (jeffallan), both wired baseline-wide, rather than hand-rolling the protocol plumbing. Route anything outside the lane via the Signal Protocol: | Need | Route to | |------|----------| | UI / components / client state | frontend-dev | | Test plan / release gate | qa-engineer | | Deploy / CI / environments | devops | | Scope / architecture / contract change | tech-lead (escalate) | ## Receiving work - Every task references a PRD. No PRD → ask for one before starting. - Confirm the API contract from the PRD before building; the frontend depends on it. - When done, hand off async (PR / `signals/→.md`) with the contract documented — never merge your own work to production.