FREEZONEX

分析截图或设计稿中的颜色，将其映射到项目的两级 CSS 变量体系（--supos-t-* 主题级 / --supos-* 应用级）。用户提供截图还原需求、UI 色值匹配、颜色一致性修正时使用。

Guidelines for designing and validating Unified Namespace (UNS) namespace tree structures — node types, type folders, topic fields, and data type inference.

Validate UNS namespace JSON structures against node type rules, topicType hierarchy, field type constraints, and naming conventions.

Tier0 platform operations entry point: CLI setup, authentication, routing to UNS, Flow, service info, and API key diagnostics skills.

Tier0 UNS operations: browse, read, write, history, search, create, update, delete, and restore namespace nodes and topics.

Tier0 Flow management for Node-RED: list, create, update, delete, export, and deploy SourceFlow and EventFlow canvas JSON.

Multi-surface design system for Tier0 (product UI, company website, PPT). Route to the correct surface before generating UI.

Diagnose and fix managed preview startup failures for TanStack Start or Vite apps in UNS-SWE executor sandboxes. Use when the user reports "Failed to load preview", "Preview loading timed out", "dev server exited: exit status 1", `{"status":500,"unhandled":true,"message":"HTTPError"}`, Tier0 SDK SSR/noExternal issues, preview_start, preview/status, live preview, Vite dev server, port 5173, /api/health, stale npm/node processes, sandbox preview process cleanup problems, missing node_modules or uninstalled dependencies, npm install/npm ci dependency restore (e.g. uploaded projects shipped without node_modules), or frequent full page reloads / broken HMR / React Fast Refresh / Vite optimizeDeps re-optimization during development.

Tier0 SDK for TypeScript/JavaScript. Use when building apps or scripts with @tier0/sdk (React, Vue3, Vite, Node): read/write/history/subscribe UNS (Unified Namespace) as a backend data source, manage Flow (Node-RED) resources, publish/subscribe Tier0 MQTT/MQ over WebSocket, or integrate external data through Tier0 OpenAPI. UNS is a data source, not a UI — do not build a UNS tree viewer, topic explorer, or namespace browser. Every topic path must have a Metric/Action/State type folder immediately before the leaf. Not for non-Tier0 brokers/APIs, another named SDK/client, or implementing an MQTT broker.