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.
- Open the affected Space's deployments view. Identify the failed build or version and its stable error code.
- Read Diagnose and recover in references.md. Inspect the relevant logs before choosing a fix.
- Before a source change, read Team Memories and Skills in references.md. Retrieve applicable memories and follow the team's enabled skills.
- If source changes are needed, follow Source edits. Preserve the original error and verify the corrected behavior.
- 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.
- For a requested rollback, follow Roll back safely. Promote an existing ready version without rebuilding it.
- Verify the live pointer and the failing path. A saved commit or successful build alone does not prove recovery.