ALWAYS follow this design guide for any front-end work
Design principles:
#path?key=value. Sharing the URL reproduces the view, with tabs, filters, slider positions, etc. captured. Prefer replaceState()Prefer creative, distinctive frontends that surprise and delight, not generic, "on distribution" outputs. A good way is to copy the design of a niche site highly related to the topic. If you do so, mention the site, reason, and what's copied.
Focus on:
Use tooltips and popups as informative and engaging aids.
Use icon libraries rather than unicode/emoji icons.
Use SVG favicons e.g.
<link rel="icon" type="image/svg+xml" href="data:image/svg+xml,%3Csvg%20xmlns ... %3C%2Fsvg%3E"/>
You can use Unicode and rich typography in the SVG.
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 64 64" width="128">
<rect fill="#2563eb" width="64" height="64" rx="10"/>
<text x="32" y="35" text-anchor="middle" dominant-baseline="middle" font-size="40">🌈</text>
</svg>
Search for places (restaurants, cafes, etc.) via Google Places API proxy on localhost.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Start voice calls via the OpenClaw voice-call plugin.
Notion API for creating and managing pages, databases, and blocks.
Gemini CLI for one-shot Q&A, summaries, and generation.
Category:developer