Use the connected Spacefast tools. When working in a checkout, preserve unrelated files and changes.
If a task requires an existing Space and its identity is unclear, call choose_space. Use the selected Space as the target. A selection does not approve publishing or other changes.
Read the MCP calls, approval, and work mode rules in references.md before a management operation.
- Resolve the intended Space. A request to update the visible site includes deployment intent; a source-only edit does not.
- Before creating or editing, read Team Memories and Skills in references.md. Read the full context before preparing changes and apply relevant saved practices within the task.
- Before publishing or deploying new or changed source, run the verify-design-system skill against current saved standards and the exact source/build being deployed. Inspect affected pages and states at desktop and mobile widths, and report gaps. Reuse verification only while the source/build and design revision are unchanged. Report missing standards as unavailable, not a pass. Verify before a source-workspace commit when autoDeploy is enabled. Follow the user's existing publication intent and approval rules.
- Read Source edits in references.md before changing files. Read the work mode and exact source revision.
- Read complete source files. Preserve unrelated changes. Do not use served deployment files as editable source.
- When design standards are present, read Design system in references.md and verify affected components before deployment.
- For visual notes, read Visual review in references.md. Keep each note tied to its reviewed version.
- For saved comment threads and screenshots, read Comments in references.md.
- For a requested CMS or admin panel, read Content dashboard in references.md before building anything.
- Save the intended source changes, then follow the Space's build and promotion flow. Report saved source and live deployment separately.