argent-lens

Propose visual design variants for on-screen elements and capture human selections in the Argent Lens window.

Updated Aug 29, 2026
One-click install
npx skills add https://github.com/Seyamalam/pstu_final --skill argent-lens-seyamalam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: argent-lens
Source: https://github.com/Seyamalam/pstu_final/tree/main/.agents/skills/argent-lens
Command: npx skills add https://github.com/Seyamalam/pstu_final --skill argent-lens-seyamalam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing between multiple UI design options requires human judgment, but manually building, screenshotting, and presenting each candidate look is slow and error-prone. This Skill automates staging real, device-rendered design variants so a human can compare them side by side and pick winners before any code is committed. ## Core Features & Use Cases - Variant Staging: Stage one or more candidate designs per element with propose_variant, each backed by a real screenshot captured on the running simulator or emulator. - Anchored Preview Cards: Match elements by identifier, label, text, or role so each floating card in the Argent Lens window connects to the correct on-screen element. - Blocking Human Decision: Call await_user_selection once to receive chosen variants, skipped elements, pinned annotations, and global comments, then apply the outcome. - Use Case: You have three candidate styles for a search field (Filled, Outlined, Pill) in a React Native app. Build each one, screenshot it on the device, propose all three, and let the human pick the winner in the Argent Lens window. ## Quick Start Enable the argent-lens feature flag, then ask the agent to propose two or more design variants for a screen element and wait for my selection.

Frequently Asked Questions about argent-lens

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I propose design variants for a UI element?

Build each variant in code, apply it on the running simulator or emulator, navigate to the screen, take a screenshot, then call propose_variant with the element name, a matcher, and the screenshot path as previewImage. Repeat for every variant, then call await_user_selection once.

How do I get a human decision on proposed design options?

Call await_user_selection once after all variants are staged. It blocks until the human finishes in the Argent Lens window and returns chosen variants, skipped elements, pinned annotations, and any global comment.

Why does propose_variant return not-found?

The argent-lens feature flag is off by default. Run argent enable argent-lens once before using the workflow, then retry propose_variant or await_user_selection.

Why do my variant previews show identical thumbnails?

Identical thumbnails mean the screenshots are byte-identical, so the variant was not actually applied on screen before capture. Verify the change rendered, diff captures with shasum, and never reuse one screenshot path across two variants.

Can I crop or edit screenshots before proposing them?

No. Pass the screenshot path returned by the screenshot tool directly as previewImage. The preview window crops using the element frame, and manual cropping or copying breaks serving and causes missing previews.

What does a pending status from await_user_selection mean?

A pending status means the timeout elapsed before the human finished; it is not an error. Proposals remain live, so simply call await_user_selection again to keep waiting.