Update to Spacefast

{
  "description": "Change the content, design, or source files of an existing Spacefast Space and apply visual review notes. Use for page text, styles, layout, or file edits. Do not use for unrelated local editing.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 193
    },
    {
      "relative_path": "references.md",
      "size_in_bytes": 20407
    }
  ],
  "name": "edit-space",
  "skill_md_contents": "---\nname: edit-space\ndescription: \"Change the content, design, or source files of an existing Spacefast Space and apply visual review notes. Use for page text, styles, layout, or file edits. Do not use for unrelated local editing.\"\n---\n\n# Update your site\n\nUse the connected Spacefast MCP tools. Sign-in is required. If the connection is unavailable, ask the user to reconnect in plugin settings.\n\nIf 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.\n\nRead the MCP calls, approval, and work mode rules in [references.md](references.md) before a management operation.\n\n1. Resolve the intended Space. A request to update the visible site includes deployment intent; a source-only edit does not.\n2. Before creating or editing, read **Team Memories and Skills** in [references.md](references.md). Read the full context before preparing changes and apply relevant saved practices within the task.\n3. 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.\n4. Read **Source edits** in [references.md](references.md) before changing files. Read the work mode and exact source revision.\n5. Read complete source files. Preserve unrelated changes. Do not use served deployment files as editable source.\n6. When design standards are present, read **Design system** in [references.md](references.md) and verify affected components before deployment.\n7. For visual notes, read **Visual review** in [references.md](references.md). Keep each note tied to its reviewed version.\n8. For saved comment threads and screenshots, read **Comments** in [references.md](references.md).\n9. For a requested CMS or admin panel, read **Content dashboard** in [references.md](references.md) before building anything.\n10. Save the intended source changes, then follow the Space's build and promotion flow. Report saved source and live deployment separately.\n"
}