Ask naturally
Learn the visual language of this project before we make the report.
Or, where slash commands are supported, ask for /visualize teach.
What happens
The agent inspects existing product code, tokens, live pages, and prior artifacts. It asks about gaps and conflicts rather than inventing certainty. Then it proposes three plain files:
DESIGN.mdrecords the visual direction and component behavior.PRODUCT.mdrecords audience, voice, and product context.tokens.cssmakes the visual choices usable in HTML.
Review the full proposed files and approve writing them before they become project guidance. Existing context should not be overwritten silently.
Use artifact themes to apply a reference to one document without changing project files. Use Artifact Explore to compare document structures or visual treatments. Neither requires you to run teach just because a profile file is missing. System Explore, for comparing complete project-system candidates, remains planned.
See representative file excerpts
From PRODUCT.md:
The user asks in natural language. The agent creates or refines a local HTML
file using the project context it already has.
From DESIGN.md:
Warm paper, coral actions, and dark denim anchors give the site character.
The overhead painting and glass prism form one composition. Examples retain
their own visual direction rather than inheriting the website's palette.
From tokens.css:
--signal: #ffa38c;
--ink: #362a27;