Documentation

To navigate project documentation safely, use a guided workflow that reads supplemental docs for architecture orientation, then confirms the concrete contract in the owning AGENTS.md file before you edit code.

AGENTS.md contract verification treats the repo README as the public quick-start source of truth, then requires confirming the concrete ownership contract in AGENTS.md before altering frontend UI primitive components.

To safely verify module extensions and server request flow, you must follow SKILL.md helper rules using single focused documentation reads, and enforce explicit permission prompts before attempting backend modifications.

No, architecture overview documentation alone is insufficient; the workflow enforces change-safety guardrails requiring explicit permission prompts and AGENTS.md contract confirmation before any backend modifications occur.

Confirming AGENTS.md contracts when starting dashboard panel work prevents unintended edits by ensuring doc-code alignment, validating that the module extension docs reflect the true source-of-truth ownership boundaries.