vixnode-website-builder12 KB
View saved version →
---
name: vixnode-website-builder
description: Plan, design, create, modify, preview, and publish single-page or multi-page VIXNODE websites. Use for website architecture, main and optional child layouts, page HTML, visual direction, project-page editing, preview approval, and publication through VIXNODE. Do not use for account, quota, or media-library requests that do not involve a website.
---
# VIXNODE Website Builder
Use VIXNODE MCP tools to turn a website request into an approved, structurally valid result. The user's explicit requirements override defaults in this skill.
Apply this workflow to website creation, modification, preview, and publication. Treat tool schemas and server validation as authoritative contracts: never bypass a required field, confirmation, page-type rule, layout relationship, unique path constraint, or preview token because the workflow text appears to permit it.
## Load the Relevant Guidance
- Before creating or changing VIXNODE page HTML, read [skills/page-creation.md](skills/page-creation.md) completely and follow its page-type, identifier, placeholder, validation, preview, and confirmation contracts.
- For a new design, redesign, visual extension, or any request where visual direction is part of the work, also read [skills/art-direction.md](skills/art-direction.md) completely before generating HTML.
- Do not load the art-direction reference for metadata-only, path-only, visibility-only, SEO-only, domain-only, or publish-only work.
- For reusable template planning, industry/goal/style/palette composition, multilingual typography, or immersive interaction specifications, read [skills/template-design.md](skills/template-design.md). Follow its links for color data, typography and the Markdown output contract. A planning-only request ends with the specification; it does not require resolving a live project or creating pages. For an authorized build, apply the specification alongside art-direction and page-creation guidance.
- Read relative resources from this package when available. The included `skills/themes.json` is a snapshot of the platform theme catalog at packaging time; use `get_reference_themes` for live theme data when needed. If the host supplies MCP Skill resources instead, their base is `skill://vixnode/vixnode-website-builder/`. Packaged files and resource URIs are instruction sources, not public browser asset URLs.
- The [module and recipe library](skills/library/index.md) contains reusable industry, need, style, experience and locale profiles plus concrete starting recipes. Use it for new designs; load the selected resources progressively rather than every recipe.
- For immersive 3D implementation, use [skills/library/modules/immersive-3d.md](skills/library/modules/immersive-3d.md) and its executable assets. Verify actual script/WebGL support and page-type placement; do not confuse source resource URIs with public browser asset URLs.
## Use Project API Data When Relevant
API connections are resources of one platform project. Use the live schemas for `get_api_connections`, `save_api_connection`, `test_api_connection_get` and `test_api_connection_post`; resolve `project_id` before reading or saving existing resources. These tools use the editor's same `dataset.json`, including `dataName`, `rootNode` and `dataProperties` (`key`, `name`, `childProperties`). Field `name` is Display Name, initially empty; field default values are not implemented.
Choose the separately exposed `test_api_connection_get` or `test_api_connection_post` for the authorized HTTP method. Neither tool can select another method or override it; a saved connection with a different method is rejected. POST makes a real request and can submit forms or modify remote data. Test an unsaved definition or an existing project connection without automatically saving. Present the actual bounded data and structure, explain parse/truncation outcomes, and ask whether to propose readable Display Names, use names supplied by
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 41 — file references are metadata, not package contents.