Add the 1024px OpenPencil brand icon, bump to 0.8.3, fill in categories / keywords / homepage / bugs / license / galleryBanner, and replace the internal-path dev stub README with a real feature listing grounded in what the extension does (custom .op editor, MCP config, AI skills, code generation, chat participant). |
||
|---|---|---|
| .. | ||
| .vscode | ||
| src | ||
| test | ||
| .gitignore | ||
| .oxlintrc.json | ||
| .vscodeignore | ||
| build.mjs | ||
| icon.png | ||
| package.json | ||
| README.md | ||
| tsconfig.json | ||
OpenPencil for VS Code
Design-as-code inside your editor — open, view, and edit OpenPencil .op files, wire your AI tools to the OpenPencil MCP server, and generate framework code from a design.
Features
- Custom
.opeditor —.opdesign files open in a live OpenPencil canvas hosted in a VS Code webview, backed by a local OpenPencil daemon. Edits are tracked as document changes, so save, save-as, revert, and hot-exit backup all work like a native editor. .figimport — opening a.figfile converts it into design content on the fly; saves land on the sibling.opfile (for exampledesign.fig→design.op) rather than writing back to the.fig.- MCP configuration — the extension runs a local MCP proxy and can write the connection into your IDE's MCP config, so an AI assistant can drive OpenPencil through the Model Context Protocol. Commands: Configure MCP and Remove MCP.
- AI skill install — install (or remove) the bundled OpenPencil design skill into your IDE's rules directory (Cursor / Trae / Windsurf); VS Code itself drives OpenPencil through MCP and needs no rules file. Commands: Install Skill and Remove Skill.
- Code generation — generate React or Vue code from the active design. When VS Code's language-model API is available it runs directly; otherwise it hands off a pre-filled prompt to your IDE's chat. Command: Generate Code. The target framework is configurable (
reactorvue). @openpencilchat participant — an OpenPencil design assistant registered in VS Code chat.- Workspace-trust aware — in an untrusted workspace
.opfiles show a read-only placeholder and no local daemon or MCP config is started; granting trust assembles the full stack and reopens the files.
Requirements
- VS Code
^1.90.0or newer. - An OpenPencil
op-host-web-serverdaemon binary. The extension probes<workspace>/target/debug/op-host-web-serverby default; setopenpencil.dev.daemonPathto point at another build. A trusted workspace is required to start the daemon and write MCP config.
Getting Started
- Trust the workspace when prompted (required for the live editor and MCP).
- Open any
.opfile — it opens in the OpenPencil canvas editor. Opening a.figfile imports it and edits are saved to the sibling.op. - Run OpenPencil: Configure MCP from the Command Palette to register the local MCP proxy with your AI tooling.
- Run OpenPencil: Generate Code to produce React or Vue code from the current design, or chat with @openpencil in the VS Code chat view.
Settings
openpencil.dev.daemonPath— path to theop-host-web-serverdaemon binary (empty probestarget/debug).openpencil.proxy.port— port for the local MCP proxy (0auto-selects).openpencil.codegen.framework— target framework for generated code (reactorvue).
Learn More
Part of the OpenPencil project — an open-source, AI-native, design-as-code vector tool.
License
MIT