v0.11.2

figlens 0.11.2 changes how figlens tells an agent to build a screen. It ships no new commands or flags.

The problem

An agent asked to implement a whole design with /figlens yolo did not write frontend code. It converted the design's node JSON into per-screen data files and shipped a generic renderer that replayed the layer tree with inline coordinates. A rerun on a single screen was closer, but it still put every component in one file, ignored the requested styling system, used plain JavaScript with no lint or format, and baked text into images. It matched the reference image reasonably well, yet no frontend reviewer would merge the code.

The guidance treated building as matching pixels, and its only structural advice was to follow the project's conventions, which an empty project does not have.

What changes

figlens reads the design; the agent builds the frontend. Every path that asks an agent to implement a design now says so: the build, plan, yolo and audit workflows, the MCP server instructions, a bundle's context.md and the viewer's copied prompt.

• Structure before markup. Component sets become components, with appearance variants and component properties as props and hover, focus or disabled variants as CSS and ARIA states. Repeated instances render from data. Sections use semantic elements, layout follows auto-layout intent, and shared headers and menus become one layout.
• Project conventions, or a baseline. In an existing project, its conventions decide the language, file layout, styling and tooling. A new project first gets a professional baseline: strict TypeScript, a linter and formatter, code organized by responsibility, and styling through the requested system with the design's tokens.
• Code review before pixels. Before compare-image, the agent checks that each design component maps to a component or data array, that markup and layout follow the design, that images, fonts and code are delivered efficiently, and that the project's type check, lint and format pass.
• yolo builds in order, one screen at a time. Setup, tokens, components, the shared shell, then screens. It reports a design-component-to-code map, and a scope larger than one run stops at its last finished screen instead of generating the rest in bulk.
• An instruction to keep code minimal cuts scope and features, not this bar.

The skill is also lighter. Index, watch, semantic and image search guidance moved from SKILL.md into references/search.md (78 KB to 54 KB), so an agent that loads the whole skill reads it only when it needs an index. figlens workflow search and the MCP workflow tool serve the same content as before.

Update

figlens update
# or
brew upgrade runkids/tap/figlens
npx @runkids/figlens@0.11.2 --version

Pi, OpenCode and OMP pick up the new guidance after pi update or a reinstall of @runkids/figlens. Claude Code, Codex, Cursor, Antigravity and Kimi plugins pin @runkids/figlens@0.11.2.

Verification and limits

The full Rust, npm, packaging and documentation checks pass. This release changes guidance, not decoding or rendering, so output files are unchanged. Whether a given model follows the new guidance has not been measured on a full agent run yet; a host or user instruction that strongly prefers minimal code can still compete with it.