How do I install the Agent Whiteboard Dev skill?

Run npx skillmds@latest add tomevault-io/agent-whiteboard-dev in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Agent Whiteboard Dev safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Agent Whiteboard Dev?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Agent Whiteboard Dev free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Agent Whiteboard Dev?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Agent Whiteboard Dev by tomevault-io

Name: Agent Whiteboard Dev
Author: tomevault-io

File contents

Agent Whiteboard Development Workflow

Project Structure

mcp-client/ - Browser UI (TypeScript + Vite)
mcp-server-go/ - Go MCP server with embedded UI
src/ - Core drawing library (TypeScript)
npm-platforms/ - Platform-specific binaries

Development Cycle

Making Changes to Browser UI

Edit files in mcp-client/
Run make build in the workspace root (automatically stops old server)
Reconnect MCP in Claude Code (server will auto-restart)
Test with whiteboard draw tool

Key Commands

Build: make build (in workspace root) - Automatically stops old server

Why Only `make build`

The Go MCP server embeds the HTML/CSS/JS files at compile time. Running make build does everything:

Stops any running MCP server
Builds the TypeScript client
Rebuilds the Go server with embedded files

Don't use npm run build:mcp-client or other partial build commands - always use make build.

Important Notes

CRITICAL: Always use make build - it's the only build command you need
make build automatically stops any running MCP server
The Go server embeds static files at compile time
Must reconnect MCP after building for changes to take effect
Server uses lazy startup - HTTP starts on first draw call

Testing Workflow

Make changes to mcp-client/mcp-client.ts or CSS/HTML
Run make build (automatically stops old server)
Reconnect MCP server in Claude Code
Use mcp_whiteboard_draw tool to test changes

Common Files

mcp-client/mcp-client.ts - Main browser application logic
mcp-client/mcp-client.css - UI styling
mcp-client/index.html - HTML structure
mcp-server-go/main.go - Go server orchestration
mcp-server-go/tools.go - MCP tool definitions

Architecture

2-canvas rendering - Persist + Display canvases
Progressive animation - Arc-length based smooth drawing
Event bus - Pub/sub for WebSocket communication
Session recording - Automatic slide history

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: agent-whiteboard-devdescription: Development workflow for agent-whiteboard project Use when this capability is needed.---# Agent Whiteboard Development Workflow## Project Structure- **mcp-client/** - Browser UI (TypeScript + Vite)- **mcp-server-go/** - Go MCP server with embedded UI- **src/** - Core drawing library (TypeScript)- **npm-platforms/** - Platform-specific binaries## Development Cycle### Making Changes to Browser UI1. Edit files in `mcp-client/`2. Run `make build` in the workspace root (automatically stops old server)3. Reconnect MCP in Claude Code (server will auto-restart)4. Test with whiteboard draw tool### Key Commands- **Build**: `make build` (in workspace root) - Automatically stops old server### Why Only `make build`The Go MCP server embeds the HTML/CSS/JS files at compile time. Running `make build` does everything:1. Stops any running MCP server2. Builds the TypeScript client 3. Rebuilds the Go server with embedded filesDon't use `npm run build:mcp-client` or other partial build commands - always use `make build`.### Important Notes- **CRITICAL**: Always use `make build` - it's the only build command you need- `make build` automatically stops any running MCP server- The Go server embeds static files at compile time- Must reconnect MCP after building for changes to take effect- Server uses **lazy startup** - HTTP starts on first draw call## Testing Workflow1. Make changes to `mcp-client/mcp-client.ts` or CSS/HTML2. Run `make build` (automatically stops old server)3. Reconnect MCP server in Claude Code4. Use `mcp_whiteboard_draw` tool to test changes## Common Files- `mcp-client/mcp-client.ts` - Main browser application logic- `mcp-client/mcp-client.css` - UI styling- `mcp-client/index.html` - HTML structure- `mcp-server-go/main.go` - Go server orchestration- `mcp-server-go/tools.go` - MCP tool definitions## Architecture- **2-canvas rendering** - Persist + Display canvases- **Progressive animation** - Arc-length based smooth drawing- **Event bus** - Pub/sub for WebSocket communication- **Session recording** - Automatic slide history---> Converted and distributed by [TomeVault](https://tomevault.io/claim/choonkeat) — claim your Tome and manage your conversions.

Frequently asked questions

Agent Whiteboard Dev