storytold/figcraft

选用指南

AI 根据 README 整理 · 2026/10/21 06:05:41

使用方式

可通过桌面应用、命令行、JSON 控制通道或 MCP 服务器使用，所有操作都基于同一命令引擎。

查看 README 依据

Every menu item, tool and drag is a command, so the same engine runs from the UI, the CLI, a JSON control channel or an MCP server. </td> </tr> </table> <br> ## A look around <table> <tr> <td width="50%" valign="top">

figcraft-cli render landing.figcraft -o landing.png --scale 2 figcraft-cli export landing.figcraft -o out/ --format svg # Run a script of commands without a window figcraft-cli run build-card.json --out card.figcraft # Every command, with its parameters figcraft-cli commands --filter autoLayout # Let an agent drive it over MCP (headless, or attached to the running app) figcraft-cli mcp figcraft-cli mcp --attach 47800 ```

部署要求

需要 Rust 环境编译运行，桌面应用支持 macOS、Windows、Linux、FreeBSD 和 Web，可从源码构建或下载安装包。

查看 README 依据

- **Never crashes:** no `unwrap`, `expect` or `panic` in shipped code, enforced by clippy; commands run behind a guard so a bug fails one action, not your session. - **Clean-room:** implemented from public documentation and observed behaviour only. No proprietary code, file formats, icons or images. ## Get started ```sh git clone https://github.com/storytold/figcraft cd figcraft cargo run --release -p figcraft # the desktop app cargo run --release -p figcraft-server # the collaboration server (docs/server.md) cargo test --workspace # the test suite

New contributors and AI agents: start with [`AGENTS.md`](AGENTS.md), then [`docs/`](docs/). Installers for macOS (universal, signed and notarized), Windows (x64, x86 and arm64), Linux (AppImage, `.deb`, `.rpm`, Flatpak and tarball), FreeBSD and the web are attached to each [GitHub release](https://github.com/storytold/figcraft/releases). Maintainers: [`docs/releasing.md`](docs/releasing.md) explains how releases are built, signed and published. > [!IMPORTANT]

已知限制

处于早期 alpha 状态，对 .fig 文件的支持尽力而为，多人协作仅有预览版，尚未与真实设计文档进行过全面校验。

查看 README 依据

> **Status:** FigCraft is in **alpha**: about 49% of the way to replacing proprietary tools for real work, by our own estimate. Nearly all tracked interface design actions in the menu checklist are wired ([`docs/parity-checklist.md`](docs/parity-checklist.md)) and the core editor works end to end, but FigCraft opens `.fig` files only best effort, has only a first preview of multiplayer (live sessions hosted from the app or a self-hosted server, with per-person undo and share links to edit or to view; no accounts, teams or cloud yet), runs its own WebAssembly plugins, and hasn't been checked

against real design documents. The honest, area-by-area picture is in the [roadmap](ROADMAP.md) and [`docs/target-app-parity.md`](docs/target-app-parity.md). Expect rough edges and please file issues, or tell us what broke on [Discord](https://discord.gg/artcraft). ## Privacy and online sharing FigCraft works offline: it has no account and no telemetry, and it contacts no server until you share or join a file. Live sessions are a **preview**. Before you share anything that matters, know what sharing does: