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.
Inspect the current project before choosing a framework. Reuse its components, assets, and build commands, then run its real build.
- Use the user's brief and real content. Infer optional design choices; ask only for information that blocks the requested result.
- 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.
- Build an accessible, responsive website with working links and useful interaction states.
- When team context includes a design system, read Design system in references.md, prepare its handoff, and verify the built components against it.
- Keep app capabilities honest. Static files do not provide a database or server; use a declared runtime when required.
- For data from a connected service, follow MCP calls in references.md. Use only data the user supplied or a connection they authorized.
- Follow Publish in references.md. After deployment, inspect the page and its main interaction before reporting success.