Render a reviewable response as an addressable Lucid artifact the user marks up in the browser, instead of returning prose. Use proactively and organically whenever the user asks to see, visualize, show, lay out, map out, sketch, or walk through something spatial, or whenever the answer is spatial or benefits from surgical, located feedback - a plan, roadmap, table, multi-step or multi-item explanation, comparison or option matrix, checklist, schema or data model, ranked list, spec or API walkthrough, or diagram - anything the user will likely want to correct at the element or phrase level. Invoking Lucid signals the response is an artifact; the user reviews in the browser and never touches the CLI. Triggers: visualize the plan, show me the plan, lay out the plan, map out the roadmap, walk me through, render this as a document, let me review this, let me mark this up, I want to annotate, review this plan, give feedback on each step, plan, roadmap, checklist, comparison table, schema, option matrix.
How to design a Lucid artifact - the HTML document a human reviews and marks up in the browser. Use when writing or restyling an artifact for `lucid open`, or any standalone HTML document meant to be read and annotated. Describes the characteristics of a good artifact: paper, not an app screen; self-contained; one accent; editorial voice. Optional - Lucid works without it, and a user's own brand always wins. Triggers: style a Lucid artifact, design the artifact, how should the artifact look, make the plan look good, artifact design.