SKETCH.
Wireframe + prototype designer.
Sketch is the VZU Sketch agent. Mid-level design pod. Wireframes, prototypes, Figma handoff. The agent that turns the brief into a clickable design before any code is written.
-
Capability
VZU Sketch
-
Category
design
-
Runtime
NetWit OS
-
Tools
3
The role
What SKETCH does
SKETCH is the dedicated agent behind VZU Sketch. It runs every time the operator briefs the vzu sketch capability. It owns the goal, the toolset, the memory, the audit trail.
The goal
What SKETCH is trying to achieve
"Take the brief and produce wireframes, a clickable prototype, and a Figma handoff package that any developer can pick up."
The capability
What it powers
SKETCH powers the VZU Sketch capability in the VZU family.
Visit sketch.vzu.ca →The toolset
3 MCP actions SKETCH can call.
Every action is exposed as an MCP server (Model Context Protocol). The agent receives the action manifest, decides which action to call, calls it, and continues reasoning. The audit trail records every call.
-
mcp.figma.wireframe
Draw the low-fi wireframes
-
mcp.figma.prototype
Build the hi-fi prototype
-
mcp.figma.handoff
Generate the dev handoff package
The memory schema
What SKETCH remembers between calls.
- → The wireframes
- → The prototype
- → The design tokens
- → The handoff annotations
The brief
A real demo brief.
"Wireframe the new onboarding flow for a SaaS product. 5 screens, mobile + desktop, 3 personas."
Below is SKETCH's actual execution trace for this brief — every step, every MCP call, every observation, every audit trail entry.
The execution trace
What SKETCH did.
Live execution trace from a recent SKETCH run. The agent was briefed: Wireframe the new onboarding flow for a SaaS product. 5 screens, mobile + desktop, 3 personas.. Each line is a step. Particles flow on the rail. The audit trail streams at the bottom.
- 01sketch › read brief
read brief
- 02sketch › thinking: onboarding flow. 5 screens. mobile + desktop. 3 personas.
thinking: onboarding flow. 5 screens. mobile + desktop. 3 personas. : onboarding flow. 5 screens. mobile + desktop. 3 personas.
- 03sketch › mcp.figma.wireframe
screens: Welcome, Signup, Profile, Tour, Done : Welcome, Signup, Profile, Tour, Done
- 04sketch › thinking: persona 1 wants minimal friction. persona 2 wants power features. persona 3 wants social proof.
thinking: persona 1 wants minimal friction. persona 2 wants power features. persona 3 wants social proof. : persona 1 wants minimal friction. persona 2 wants power features. persona 3 wants social proof.
- 05sketch › mcp.figma.prototype
clickable flow with 3 branches
- 06sketch › mcp.figma.handoff
components: Button, Input, Card, Modal : Button, Input, Card, Modal
- 07sketch › ship. 2 weeks. 5 screens. 3 branches. 1 clickable prototype. done
ship. 2 weeks. 5 screens. 3 branches. 1 clickable prototype.
Audit trail · 5 entries
- T+00:00:00 brief.received 01
- T+00:01:00 wireframes.drafted 02
- T+00:08:00 prototype.built 03
- T+00:14:00 handoff.packaged 04
- T+02:00:00 brief.completed 05
The numbers
SKETCH, by the numbers.
Four KPIs. Animated count-up on scroll. Sparkline shows the recent trend. Delta indicator shows the trajectory.
- KPI · 01 now
2 weeks
Median brief duration
37% - KPI · 02 now
5
Screens shipped
75% - KPI · 03 now
12
Components documented
27% - KPI · 04 now
3
Persona coverage
63%
The other 11
Every agent in the family.
- engineering
ATLAS
Full-stack app builder.
- engineering
VEGA
React/Next.js engineer.
- engineering
KAI
Backend + infra engineer.
- design
NOVA
Editorial UI designer.
- design
PIXEL
Motion + WebGL designer.
- design
ECHO
WCAG accessibility auditor.
- design
LAUNCH
Landing page composer.
- review
SENTINEL
Code reviewer + security auditor.
- review
ORACLE
Production prompt engineer.
- data
QUILL
Spreadsheet engineer.
- automation
HUNTER
Resilient web scraper.
Get in touch
Brief SKETCH.
The orchestrator handles the routing, the audit trail, and the enforcement. SKETCH handles the work. The operator owns the goal.