Development rules

This repository contains a reusable skill, a coordination service and a bundled dashboard template. Keep project and cluster configuration outside the repository.
The UI uses the shipped React / shadcn/ui / Tailwind template and fixed design tokens. Reuse its components and five pages; do not replace it with a new ad hoc interface for each project.
SKILL.md is the agent entry point. README.md is the human entry point. Maintain runtime mechanics in references/operations.md and design rules in references/design-system.md; avoid duplicated current instructions.
Use only supported host/CLI interfaces to read or send session messages. Do not inspect or modify private application databases, bypass a live writer lock, or equate a placeholder with a running agent.
Preserve message identity, session boundaries, idempotency and uncertainty after possible external side effects. A model reply is not business acceptance.
Verify meaningful behavior with python3 -m unittest discover -s tests -v and npm ci && npm run build in assets/dashboard/. UI changes also need browser checks. Use only task-owned instances and synthetic tests.
Before public commits, inspect the exact staged files for credentials, internal addresses, private project names, production state, personal paths, real session IDs and copied customer material. Never copy another repository's Git history.