nexu-io/open-design:README 來源編輯指南
根據 README、倉庫資料與授權整理 nexu-io/open-design 的安裝與核驗路徑。
專案定位
nexu-io/open-design 的 README 將專案描述為「🎨 The open-source Claude Design alternative. 🖥️ Local-first desktop app. 🖼️ Your coding agent becomes the design engine: prototypes, landing pages, dashboards, slides, images & video , real files, HTML/PDF/PPTX/MP4 export.」。本文只整理倉庫可直接核對的內容,不把 star、Fork 或宣傳語當成品質證明。README 在「README」下寫到:> ⚡ Open Design Cloud , the official model service. One recharge to use GPT, Claude, Gemini, and DeepSeek inside Open Design: 20+ flagship models, zero config, billed by real token usage. Try Open Design Cloud.。這說明的是專案邊界,不是已完成的生產驗證。
適用場景
從 README 的「Why Open Design」與相關條目,可以先判斷它是否處理你的實際問題:🧠 Brand-grade by default. Every render reads the active package's DESIGN.md as the core brand contract. 151 design-system packages ship with the repo;。若需求不同,不應只因專案熱度就採用。本文保留原始專案名、命令與元件名,方便回到一手來源核對。 README 另外列出一項可核對的資訊:🤖 Agent-native, model-agnostic. We don't ship an agent. The claude / codex / cursor-agent / copilot / hermes / kimi already on your PATH are the design engine. Swap with one click.。這類原文條目可用來設計試跑步驟,但不能取代實際環境測試。
運作方式
README 將運作方式分散在「What is Open Design」等段落。可確認的線索包括:Open Design is what you get when the agent-native loop Anthropic shipped with Claude Design , discover the brief, lock the direction, stream the artifact, critique, deliver , stops being closed and becomes a filesystem of functional。本文不把未寫出的架構、效能或安全邊界補成結論;真正的執行鏈仍要配合目錄、設定檔與版本標籤檢查。
安裝與第一次執行
第一次安裝應從 README 指出的入口開始。目前可核對的命令是: # One-line install into the agent you're using: od mcp install <agent> # <agent> = claude | codex | reasonix | raven | cursor | copilot | openclaw # | antigravity | pi | vibe | hermes | cline | kimi | kiro # | trae | opencode # Hosted equivalent for curl-based setup: curl -fsSL https://open-design.ai/install.sh | sh -s <agent> 如果倉庫沒有命令,本文不會自行編造步驟,而是建議先閱讀「Product tour」,確認系統依賴、預設埠與首次初始化。