VIXNODE

Upload one image to a project photo library over multiple calls. For an image whose total size is 3 MiB or less, first try the 'upload_image' tool; use this chunk tool for larger images or when the single-call upload cannot be completed. Split the original image bytes into fixed-size chunks, Base64-encode each chunk independently, and call this tool sequentially from chunk_index 0 through chunk_total - 1 using identical upload_id and file metadata.

chunk_upload_image

Upload one video to a project video library over multiple calls. For a video whose total size is 3 MiB or less, first try the 'upload_video' tool; use this chunk tool for larger videos or when the single-call upload cannot be completed. Split the original video bytes into fixed-size chunks, Base64-encode each chunk independently, and call this tool sequentially from chunk_index 0 through chunk_total - 1 using identical upload_id and file metadata.

chunk_upload_video

Compares a project page HTML version with its previous version and returns patch and both contents. Please provide a plain-language summary of changes first. If the user asks for programming details, then explain using code-focused technical terms.

get_project_page_html_compare_by_version

Create a new website project. If the user has not created any project yet, the assistant should ask whether to create one. Before creation, the assistant must confirm the project name with the user. This tool does not require UI confirmation. After a successful creation, call get_project_pages again with the returned project id.

create_project

Follow the VIXNODE Website Builder Skill's planning, layout, HTML, preview, and confirmation workflow before calling this tool. Use this as the mandatory/default tool for every ordinary request to create, add, or build a project page, whether or not the user explicitly says preview. MULTI-PAGE PLANNING GATE: before generating HTML or calling any create-page tool, determine whether the user's actual goal calls for multiple independently navigable pages or shared site-wide structure. Signals include two or more requested destinations or recurring navigation areas such as Home, About, Products or Services, Blog, FAQ, and Contact. When a multi-page structure is likely and the user has not already approved a sitemap and layout hierarchy, explain briefly that shared layouts will keep navigation, header, footer, and styling consistent, then ask whether they want to plan the multi-page architecture first. Do not invoke this tool until they answer. Do not add this gate when the user explicitly requests a single page, landing page, or one-page site. If the user agrees, inspect existing project pages, propose a concise sitemap plus Main Layout -> content-page hierarchy, and wait for approval. A Child Layout is optional, not required: propose or create one only when a subset of pages needs an additional shared structure distinct from the Main Layout; otherwise every content page should reference the Main Layout directly. Then create and review exactly one item at a time in dependency order: pageType='layout' for the Main Layout; only when justified, pageType='childLayout' with layout=<main layout page id>; then pageType='layoutPage' with layout=<main layout page id> or, only for the relevant subset, <child layout page id>. Reuse the returned page ids in later calls and never imply that one call creates the whole site. Before invoking this tool for the current item, generate its complete non-empty HTML document and send it in html; never send an empty string or placeholder and never open the review UI before the HTML is ready. For example, '@VIXNODE-dev 在 [品牌香水] 新建一個簡單的測試頁' MUST call this tool with mode='preview', projectName='品牌香水', and the complete generated HTML; it MUST NOT call create_project_page. The user's initial create request is authorization to prepare this review UI, never confirmation for an immediate write. If the request says preview, 預覽, or プレビュー, you MUST call this tool in preview mode and MUST NOT call create_project_page. Unless the user explicitly requests no publication, draft-only creation, or a private page, you MUST send publishAfterSave=true and public=true so both checkboxes are selected by default. It renders a review UI whose button performs the confirmed creation. Keep fileName separate from virtualPath and ensure their combination does not duplicate an existing project page.

create_project_page_preview

Create a new web page under a specific project in VIXNODE. For new project-page creation workflows, prefer create_project_page_preview, which supports independent virtualPath and fileName fields, UI or conversational confirmation, and optional publication after creation. Use create_web_page only when compatibility with the legacy webpage creation workflow is required. MANDATORY PRE-CALL CHECKLIST: Before invoking this tool, the assistant MUST have explicit user confirmation for: 1) Target project: say the project name and ask the user to confirm. Even if there is only one project, confirmation is still required. Do not auto-select a project even if the account has exactly one project. The assistant may suggest the only available project, but must wait for user confirmation before calling create_web_page. Do not display project_id or page_id to the user unless the user explicitly asks for those IDs. 2) Style source: ask whether to use A. uploaded image as style reference, B. a VIXNODE reference theme, or C. a custom style. Also tell the user that a style list UI can be shown for interactive style selection. When asking this, explicitly tell the user they can define custom style preferences (for example: color palette, typography, spacing, visual mood, component style, and reference sites). If the user chooses VIXNODE reference theme, call get_reference_themes first. If the user chooses uploaded image/custom style, summarize the interpreted style and ask for confirmation. If the user provides an image and asks to create a page based on it, treat the image as a proposed style source, not as final confirmation. The assistant must summarize the interpreted style and ask whether to proceed with that style. Before generating final HTML, the assistant should present the prompt summary and ask user confirmation. Prompt should use Markdown and plain-language content/style summary, and should not mention project name or project creation action. Preview confirmation generated by this tool does NOT replace the above checks. If HTML is truncated and cannot be previewed correctly, ask the user to try ChatGPT Work mode: https://chatgpt.com/?surface=work. Use mode='preview' to generate preview only. For actual creation, either use the existing UI confirmation path with confirmationMethod='ui', confirmByUser=true, and a valid confirmToken, or, after the assistant has presented the exact operation and obtained the user's explicit confirmation in the conversation, use confirmationMethod='conversation' and userConfirmed=true. Never infer conversational confirmation from an ambiguous request. If confirmationMethod is omitted, the existing UI confirmation path is used. After create_web_page, use modify_project_page to update saved page properties or HTML without publishing, and use publish_project_page to publish the latest saved version when explicitly requested. Input keys (only): project_id, name, page_id, pageType, layout, lang, public, fileName, html, prompt, mode, confirm, confirmByUser, confirmToken, confirmationMethod, userConfirmed. Legacy key confirm is accepted for backward compatibility only. Do not use removed keys: selected_theme_id, selected_theme_name, themeConfirmed. Note: If the user does not mention programming details, respond in plain language. If the user mentions programming details, then respond with code-related content.

create_web_page

Follow the VIXNODE Website Builder Skill's planning and layout workflow before calling this exceptional no-preview tool. NEVER use this tool for an initial or ordinary create-page request. Use create_project_page_preview instead, including for '@VIXNODE-dev 在 [品牌香水] 新建一個簡單的測試頁'. MULTI-PAGE PLANNING GATE: before any direct creation, determine whether the user's goal calls for multiple independently navigable pages or shared site-wide structure. When it does and the user has not approved an architecture, ask whether they want to plan the sitemap and shared Layout hierarchy first; do not call this tool until they answer. Skip that question only for an explicitly requested single page, landing page, or one-page site, or when the user already approved the structure. If planning is accepted, inspect existing pages and propose a Main Layout -> content-page hierarchy for approval. A Child Layout is optional, not required: include one only when a subset of pages needs an additional shared structure distinct from the Main Layout; otherwise attach content pages directly to the Main Layout. Create exactly one item per call in dependency order: pageType='layout' first; only when justified, pageType='childLayout' with layout=<main layout page id>; then pageType='layoutPage' with layout=<main layout page id> or, only for the relevant subset, <child layout page id>. Reuse returned page ids and never imply that one call creates the whole site. This exceptional tool writes immediately without a preview and may be used only after the assistant has already presented the exact current item, project, page settings, path, visibility, hierarchy relationship, and side effects, and the user then gives a separate explicit confirmation in a later message. Set userConfirmed=true only after that separate confirmation. If the request says preview, 預覽, or プレビュー, never call this tool. It does not publish; call publish_project_page afterward only when publication was separately explained and explicitly confirmed. Check existing pages first because virtualPath plus fileName must be unique.

create_project_page

Follow the VIXNODE Website Builder Skill's target-resolution, layout, and minimal-change workflow before calling this exceptional no-preview tool. Use it only after presenting the exact target, changes, and side effects, and then obtaining a separate explicit user confirmation to write immediately without preview. The initial request to modify a page—even a fully specified request—is not that confirmation and MUST use modify_project_page_preview by default. If the request says preview, 預覽, or プレビュー, never call this tool. It writes immediately and does not publish; call publish_project_page afterward only when publication was separately explained and explicitly confirmed. Obtain the latest HTML first and keep virtualPath plus fileName unique. If virtualPath is set or changed, the page must be published again for the new path to take effect.

modify_project_page

Use this only after evaluating the real context, presenting the exact target and the fact that a private page will be made public, and then obtaining a separate explicit user confirmation to publish immediately. An initial create, modify, or publish request is not by itself confirmation for this direct tool, and preview workflows must publish through their confirmed UI action. Never use it to satisfy a preview request. It publishes immediately without rendering a UI and may follow create_project_page or modify_project_page only when publication was separately explained and explicitly confirmed.

publish_project_page

Retrieves all pages across all website projects for fast navigation and search. Invoke this MCP tool by name 'get_all_project_pages' directly (do not construct HTTP paths such as /VIXNODE/... ). In user-facing messages, show project/page names instead of project_id/page_id unless the user explicitly requests those IDs.

get_all_project_pages