asset-aware-web-design
Asset-aware web design
Give the agent three capabilities while it designs:
- Asset Awareness — notice where meaningful assets could improve the interface.
- Asset Intelligence — identify what should be expressed and choose the right semantic type, medium, visual style, placement, and source route.
- Asset Orchestration — inspect, source, generate, curate, art-direct, transform, save, integrate, and document the selected asset.
This skill is not a blanket instruction to use more images. Use the best visual strategy for each communication goal. CSS, SVG, Canvas, WebGL, gradients, and code-rendered visuals remain valid when they are genuinely the strongest medium.
Design-placeholder premise
For design drafts, prototypes, mockups, and visual exploration, treat externally sourced or generated imagery as design placeholders by default unless the user explicitly requests production-ready assets.
Before the first external search or generation, tell the user once, in their language:
I’ll use sourced or generated images as design placeholders for visual review. They are not cleared for commercial or production use and must be replaced or licensed before launch.
This is a disclosure, not a permission request. Continue unless the user changes the sourcing or generation direction.