Hmbown Silent Image
Create a static visual mockup — no interaction, no sound, just the picture.
Overview
Silent Image is interpreted here as a metaphorical spell with a shipping-now execution model.
Canonical source: Silent Image (spell)
Provider target: OpenClaw
When To Use
- The question is purely visual: what will it look like, how will it be laid out, what is the aesthetic?
- A static mockup or design comp is sufficient and interactivity would be over-investment.
- You need to communicate a visual design direction quickly without building a working prototype.
Workflow
- Clarify the visual question: layout, styling, content hierarchy, or aesthetic direction.
- Create a static visual artifact: design comp, rendered mockup, annotated screenshot, or diagram.
- Present it as a visual reference, not a functional prototype.
- Gather visual feedback and iterate on the design before investing in interactivity.
Deliverables
- A static visual artifact: design comp, mockup, or rendered preview.
- Annotations explaining any visual decisions that are not self-evident.
Guardrails
- Do not present static mockups as interactive prototypes. If stakeholders will try to click, use Major Image instead.
- Static visuals that represent real data must be clearly marked as illustrations, not live dashboards.
Default Invocation
Use $silent-image to create a static visual mockup or design comp that answers the question what will this look like without investing in interactivity.