Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
oil-oil avatar

Gemini Designer

  • 203 installs
  • 51 repo stars
  • Updated July 10, 2026
  • oil-oil/gemini-designer

Generate UI layouts, component specs, and visual design directions with Gemini during frontend implementation for web or mobile products.

About

gemini-designer from oil-oil/gemini-designer uses Google Gemini to help agents produce UI layouts, component ideas, and visual design specs during frontend build work for SaaS, mobile, and content products.

  • Gemini-powered visual and layout ideation
  • UI component and screen design guidance
  • Branding-aligned design exploration
  • Accelerates frontend design iteration

Gemini Designer by the numbers

  • 203 all-time installs (skills.sh)
  • Ranked #938 of 1,880 Design & UI/UX skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/oil-oil/gemini-designer --skill gemini-designer

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs203
repo stars51
Last updatedJuly 10, 2026
Repositoryoil-oil/gemini-designer

What it does

Generate UI layouts, component specs, and visual design directions with Gemini during frontend implementation for web or mobile products.

Files

SKILL.mdMarkdownGitHub ↗

Gemini Designer — Visual Design Advisor

Use Gemini as an external visual design advisor for taste, direction, hierarchy, rhythm, and UI experience.

Critical rules

  • ONLY interact with Gemini through the global gemini-designer CLI. Do not call the API or provider-specific scripts directly.
  • When this skill is used, call gemini-designer before giving design imagery, art direction, critique, visual advice, HTML, or SVG output. Do not write those deliverables from the agent's own judgment.
  • Call gemini-designer directly in the normal path. If the command is missing, install it silently with the bundled scripts/install_cli script, then retry.
  • For existing UI files, use gemini-designer advise. Do not use gemini-designer html to refine an existing page.
  • For broad art direction, use gemini-designer direction. It may include files as background context.
  • For design imagery markdown, use gemini-designer direction and read the generated markdown before responding.
  • For new standalone HTML/SVG design drafts, use gemini-designer html or gemini-designer svg.
  • For a single handwritten SVG brand wordmark, lettering mark, signature mark, or logo-like text asset, use gemini-designer svg.
  • For a comparison sheet with multiple wordmark candidates, use gemini-designer html.
  • If the user provides screenshots, mockups, moodboards, or visual references, include relevant images with -i / --image when they help Gemini judge visual style, layout, hierarchy, mood, or fidelity.
  • Gemini is stateless. It does not know the current project, prior conversation, screenshots, local files, design rules, or previous Gemini outputs unless they are included in the current command.
  • Do not ask Gemini to review code quality, technical debt, CSS lint, or engineering consistency unless the user explicitly asks. Keep Gemini focused on visual effect, design intent, hierarchy, rhythm, taste, and UI experience.
  • Do not ask Gemini to output code patches or diffs for existing files. Use its design advice, then make the actual edits yourself.
  • After Gemini returns design advice, design imagery markdown, visual direction, or an HTML mockup, show the output or a concise summary to the user and wait for confirmation before implementing it in project code, unless the user explicitly asked to implement immediately.
  • After html or svg returns, do not start an extra AI review, visual critique, browser screenshot check, grep/tail completeness check, or refinement loop unless the user explicitly asked for checking or iteration. The CLI performs structural integrity checks before writing generated HTML/SVG. Read enough to know what Gemini returned, then present it to the user.
  • For ordinary HTML, SVG, or icon requests, run the script ONCE per task. Read the output file and proceed.
  • Pass the user's stated requirements and concrete project context. Do not add the agent's own style labels, layout choices, color choices, metaphor choices, or evaluation criteria unless the user explicitly said them.
  • Do not pre-design for Gemini. For creative generation, the agent should state the user goal, source material, output format, and hard constraints only. Do not name visual directions, metaphors, layouts, palettes, typography, materials, or animation concepts unless the user explicitly provided them.
  • For multiple alternatives, ask Gemini for independent, clearly different options. Do not assign the options names like "dashboard direction", "editorial direction", or "radar direction" unless the user gave those directions.
  • The CLI manages its own configuration and authorization. Do not pre-check authorization. If a call fails with error=not_authorized, report that Gemini Designer is not authorized.

Gemini CLI

Use gemini-designer for every Gemini task.

Normal path: call gemini-designer directly. Do not run install or auth checks before every use.

If the shell reports command not found, resolve /path/to/this-skill to the directory containing this SKILL.md, run /path/to/this-skill/scripts/install_cli silently, then retry the original gemini-designer command. If the installer reports a path_warning, use the printed installed_path for this turn and tell the user that the CLI directory is not on PATH.

If the CLI returns error=not_authorized, stop and tell the user Gemini Designer is not authorized. Do not read, copy, print, or manage API keys.

Each command has its own built-in prompt. Choose the right command and pass the user's task plainly; do not add a cross-command prompt framework, design direction, or extra output rules unless the user explicitly gave them.

Commands:

  • gemini-designer advise — Use for visual design advice. It may include -f and -i as reference context, and requires a readable markdown file name with -o. Gemini gives concrete implementation-oriented visual suggestions, reuse reminders, and pseudo-code snippets when useful. Use this for small refinements and project-style consistency.
  • gemini-designer direction — Use before implementation when the task needs a stronger idea, art direction, visual metaphor, design imagery markdown, or high-level design direction. Files are optional. Always provide a readable markdown file name with -o.
  • gemini-designer html — Use for a new standalone HTML mockup or concept page. It may include -f and -i as reference context, but do not use it to directly revise an existing project file.
  • gemini-designer svg — Use for a new SVG icon, simple illustration, or single handwritten SVG wordmark. It may include -f and -i as reference context.

When advise needs to judge existing UI, pass complete relevant files by default. Do not summarize, slice, or annotate the file unless the file is too large for the CLI limit or the user asks for a scoped review. Prompt-only advise is fine for general design questions.

For advise and direction, always name the markdown file at call time with -o. Prefer a bare readable filename, such as accounts-filter-advice.md, museon-home-art-direction.md, or pricing-page-design-imagery.md; the CLI saves bare names under .gemini-designer/. Use an explicit path only when a specific directory is required.

For html and svg, pass files with -f when Gemini should reference existing content, design rules, previous mockups, theme tokens, example components, or brand references. Treat those files as context for a new design draft, not as files Gemini will patch in place.

For html, describe the design goal only. Do not ask Gemini to save a file, return a file:// URL, provide a download link, or explain where the file is. The CLI writes the output file; Gemini must return raw complete HTML source only.

For html, do not mention asset or dependency policy by default. Let Gemini decide whether images, fonts, scripts, stylesheets, icon libraries, audio, or video help the design. Only add asset constraints when the user explicitly asks for them, such as fully self-contained, offline-safe, no external resources, or use realistic public images.

For handwritten wordmarks, use svg when the user wants one asset, and use html when the user wants several candidates to compare. Describe the word or words, mood, and any explicit material preference from the user. Do not prescribe neon, metal, sci-fi, or other effect-heavy styles unless the user asked for them. The default direction is readable paper-and-ink SVG lettering with subtle writing animation and tasteful finishing marks when useful.

The built-in direction, html, and svg prompts lightly remind Gemini to avoid generic AI templates and default category stereotypes, keep the subject immediately recognizable through concrete sensory anchors, ground design choices in the product subject and real content, use purposeful contrast when it improves visual communication, spend visual boldness in one important place, and keep surrounding UI quiet.

Context Rules

Gemini receives only the command text, files passed with -f, and images passed with -i. It has no memory across calls.

The CLI places the final user goal after reference files and image manifests so Gemini sees the concrete task last. Agents should keep the task text close to the user's wording instead of repeating constraints in several places.

When asking about an existing UI, pass the smallest complete set of files needed for the visual judgment:

  • The target file or component being judged
  • The project design guide or style reference, if one exists in the workspace
  • Related CSS/theme/token files when they materially affect the visual result
  • Nearby component files only when they define visible structure or reused UI patterns
  • Screenshots, mockups, moodboards, reference images, or exported previews when the user's visual question depends on what the UI looks like

Prefer complete files over excerpts. Use multiple -f flags:

gemini-designer advise "判断这个页面是否符合项目现有视觉风格,并给出具体优化建议" \
  -f ./design.html \
  -f ./src/styles/tokens.css \
  -f ./src/components/Button.tsx \
  -o design-page-advice.md

Use -i for image context:

gemini-designer advise "结合截图给这个页面提视觉设计建议" \
  -f ./design.html \
  -i ./screenshots/current.png \
  -o current-page-screenshot-advice.md

gemini-designer direction "参考这张图,生成设计意象 markdown" \
  -i ./references/moodboard.png \
  -o product-design-imagery.md

When images are passed with -i, the CLI may internally send an optimized WebP version to Gemini to reduce request size while preserving readable UI detail. Agents should still pass the original screenshot or reference image path.

Do not pass unrelated source files, build output, dependency folders, logs, or implementation details that do not affect the visual result. If the needed context is too large, choose representative design-system files and say in the task text what is missing.

If Gemini's advise output says it needs more context, do not treat that as final advice. Gather the requested files or information when available, then run gemini-designer advise again with the added -f inputs. If the requested context cannot be found, tell the user exactly what is missing and ask for it.

The built-in advise prompt asks Gemini to:

  • stay independent and avoid flattery
  • focus on visual effect, design intent, information hierarchy, reading rhythm, atmosphere, UI finish, and user feeling
  • avoid turning the response into code review
  • keep the answer concrete and actionable enough for implementation
  • explain exactly where to change, how to change it, and why the visual result improves
  • include pseudo-code, CSS, or JSX snippets when useful, with enough length to explain the change, without outputting a full file
  • remind the implementing agent to prefer existing components, selectors, classes, tokens, variables, layout patterns, and interaction patterns
  • name reusable components or tokens only when they are visible in the provided files; otherwise do not invent project-specific names
  • include a short "do not change" section when there are concrete areas, tokens, components, visual traits, copy, or states that should be preserved
  • avoid suggesting a new design system, unrelated components, or decorative additions when existing patterns can be reused
  • avoid outputting full HTML
  • ask for missing context instead of guessing when a reliable visual judgment is not possible

Useful commands:

gemini-designer advise "给这个页面提视觉设计建议" -f ./design.html -o design-page-advice.md
gemini-designer advise "结合截图给这个页面提视觉设计建议" -f ./design.html -i ./screenshots/current.png -o page-screenshot-advice.md
gemini-designer direction "给这个产品生成设计意象 markdown" -o product-design-imagery.md
gemini-designer direction "基于这个页面生成设计意象 markdown" -f ./design.html -o page-design-imagery.md
gemini-designer html "基于这个页面生成一个完整、全新的落地页方案。保留产品信息,由你独立判断视觉方向,不要复刻原稿。" -f ./design.html -o ./designs/page.html
gemini-designer html "基于这个页面生成第 1 个完整落地页方案。保留产品信息,由你独立判断视觉方向。后续方案需要彼此明显不同。" -f ./design.html -o ./designs/page-option-1.html
gemini-designer svg "为 Museon 生成一个手写 SVG 字标,气质像策展笔记标题" -o museon-wordmark.svg
gemini-designer html "展示 Museon、Mel、Signal 三个手写 SVG 字标候选,默认偏纸面墨迹和真实笔触" -o wordmark-candidates.html
gemini-designer svg "生成一个设置图标" -f ./brand.md -o ./icons/settings.svg

Read the output file before acting. Apply only the suggestions that fit the project.

advise and direction outputs include a final 原始提示词 section. It records the task text and readable paths for referenced files or images, without copying the full file contents into the appendix.

For advisory outputs (advise and direction) and HTML mockups from Gemini, do not immediately edit project files. Present Gemini's output or a concise summary, ask the user to choose or confirm the direction, then implement only the confirmed parts. SVG icon output can be saved directly when the user's request is only to create the asset. Do not run a self-review pass just because an HTML or SVG file was created.

The script prints on success:

output_path=<path to output file>

For html and svg, the script also prints:

integrity=passed

Read the file at output_path to get Gemini's response.

On failure, the CLI prints stable fields:

error=<code>
message=<short explanation>
hint=<next step>

Follow the hint when it is actionable. If error=not_authorized, stop and tell the user Gemini Designer is not authorized.

For generated HTML/SVG, treat output_path plus integrity=passed as the normal completeness signal. Do not duplicate CLI checks in the agent unless the user asks for additional browser or visual verification.

Output types

  • gemini-designer html — Self-contained complete HTML source with inline CSS. Ready to open in browser. The CLI rejects incomplete HTML, missing head/body, file URLs, markdown fences, lorem ipsum, and non-HTML wrapper output.
  • gemini-designer svg — Clean SVG code for icons, simple illustrations, or single handwritten wordmarks. The CLI rejects invalid XML, wrapper text, markdown fences, and local file URLs. Can be saved directly or embedded in HTML/React.
  • gemini-designer advise and gemini-designer direction — Markdown output.

Configuration

  • The global CLI reads ~/.config/gemini-designer/config.toml.
  • Image optimization defaults to WebP when supported by the local CLI environment.
  • Agents should not read, copy, or manage API keys.
  • Do not check authorization in the normal path. Use gemini-designer auth status only when explicitly debugging authorization.

When to use

  • Need Gemini to inspect existing HTML/CSS/TSX and give visual design advice
  • Need a concise visual optimization plan based on one or more local files
  • Need a visual reference or HTML mockup for a UI component or page
  • Need handwritten SVG wordmark, lettering, signature mark, or logo-like text candidates
  • Need SVG icons or simple illustrations
  • Need color palette, typography, or layout suggestions
  • Need design feedback or critique on an existing design
  • Want a quick single-page HTML prototype to show a concept

Workflow

1. Choose the smallest useful Gemini task: advise, direction, html, or svg. 2. Run gemini-designer with a readable -o path and get an output_path before writing the final answer or file. 3. Use the user's wording as the task text whenever possible. Add only factual context needed to identify files, product scope, or constraints the user actually gave. 4. For design imagery markdown or visual direction, call gemini-designer direction. 5. For new HTML/SVG design drafts, call gemini-designer html or gemini-designer svg; include -f or -i when reference context matters. 6. For a single handwritten SVG wordmark, call gemini-designer svg; for several wordmark candidates in one comparison sheet, call gemini-designer html. 7. Read Gemini's output. 8. If advise says more context is needed, gather the requested context and rerun gemini-designer advise once before presenting advice to the user. If the context is unavailable, ask the user for it. 9. When implementing advise output, first look for existing project components, selectors, classes, tokens, variables, and layout patterns to reuse. If Gemini suggests replacing a broad system or inventing unrelated UI, narrow it to existing patterns before editing. 10. If Gemini drifts into code review when the task is visual, rerun with a visual-only goal such as: "只从视觉设计角度判断,不要评论代码规范或工程债。" 11. Present advisory outputs or HTML mockups to the user for confirmation before editing project code, unless the user explicitly asked to implement immediately. 12. Base the final response on Gemini's output. You may summarize, select, or implement useful parts, but do not replace Gemini's design judgment with your own generated design direction.

Tips

  • Keep the task prompt close to the user's request.
  • If the user did not specify a style, color, font, layout, metaphor, or visual direction, do not invent one in the prompt.
  • Do not split multiple Gemini generations by agent-authored themes. Use neutral wording such as "第 1 个独立方案 / 第 2 个独立方案 / 第 3 个独立方案" and ask Gemini to make them clearly different through its own judgment.
  • When passing a reference design, say whether Gemini may preserve or should avoid copying it. Do not replace that with your own alternate concepts.
  • For HTML mockups, do not mention asset or dependency rules unless the user asks. Unnecessary constraints can weaken Gemini's design judgment.
  • Only pass explicit user preferences (e.g. "dark mode", "use blue") when the user actually said so.
  • When the task asks for design insight, direction, or an HTML mockup, do not ask Gemini for long explanatory copy. Let Gemini express ideas through visible UI structure, states, examples, hierarchy, and interaction when possible.
  • Do not translate "more designed" into visual noise. Strong visual treatment should support key actions, brand memory, and key content entry points; supporting areas should stay quiet, stable, and easy to scan.
  • Let Gemini decide how to avoid cliches. Do not add your own list of banned styles, but pass explicit user constraints such as "避免俗套科技感、赛博朋克感" when the user says them.
  • Let Gemini actively consider motion, inline SVG, material, and micro-interaction opportunities, but do not prescribe a specific animation or material style unless the user asked for it.
  • Do not add your own anti-template checklist to the task prompt. The CLI already gives Gemini light reminders about generic AI aesthetics, memorable visual ideas, restraint, real content, and UI copy.
  • Chinese prompts work well — Gemini responds in the same language.

Related skills

Design & UI/UXuiuxbranding

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.