01 · Lloyds Banking Group · Cancara Labs
Developer workflow
From design intent to governed delivery
I lead and own Cancara Labs within CancaraOS, turning recurring design and engineering needs into AI-assisted workflows, reusable patterns and MCP server offerings, with evaluation and human review built in.
Sanitised offering · Design-to-code evaluation
A governed evaluation path—not an autonomous shortcut.
- 01User + trigger
A design-system engineer selects an approved Figma node and target component
- 02MCP boundary
Approved Figma, documentation and repository capabilities only
- 03Candidate
The reusable workflow produces an implementation and evaluation record
- 04Evaluate
Structural comparison, visual diff and recorded failure modes
- 05Human gate
A named engineer accepts, rejects or iterates before delivery
Rejection loopRejected output returns to the workflow with its failure mode recorded.
- Status
- Owned MVP and evaluation foundations in active delivery
- Attributable result
- Moved evaluation from informal exploration into a repeatable, reviewable proof path
Representative current offering. Internal schemas, prompts, evaluation data and product code are intentionally omitted.
What I established
- Moved AI and platform exploration from side-of-desk activity into owned MVPs, delivery plans and measurable proof paths.
- Made evaluation, visual comparison and human approval part of the delivery architecture.