visual-design-system
Skill1 starsChanged 58 days agoMITView on GitHub
This skill provides visual design guidance using Google Gemini's AI capabilities. Use this skill when the user asks to "generate an image", "create a mockup", "design a UI", "make a logo", "create game assets", "generate a video", "review a design", "create icons", "design a landing page", or any visual design/generation task. Also use when writing UI code that could benefit from visual asset generation.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- KinwiseNZ-DevOps/ui-ux-designertheir own version, first seen Nov 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- KinwiseNZ-DevOps/ui-ux-designer★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repositoryOne other file it gives its agents.
- CLAUDE.mdCLAUDE.md
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 4 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill when working on visual design tasks — image generation, UI mockups, game assets, video creation, or design analysis.
- Distinctive: line 12
Never jump straight to expensive generation: Follow this workflow:
- Distinctive: line 37
Use negative prompts ("no X", "don't include Y")
- Very specific: line 40
Use the pro tier for drafts or iterative exploration (it costs 2x fast)
- Very specific: line 55
Every image tier accepts a reference_image, so asking for style consistency never forces a tier change.
- Very specific: line 60
Use get_prompt_templates to browse these:
- Very specific: line 70
Use analyze_design with the appropriate focus and project_type
- Distinctive: line 84
All generation tools automatically apply this profile to prompts.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Visual Design System with Gemini
Use this skill when working on visual design tasks — image generation, UI mockups, game assets, video creation, or design analysis.
Core Workflow: Draft → Edit → Finalize
Never jump straight to expensive generation. Follow this workflow:
- Set up style profile first — Use
init_style_profileto create a.gemini-design-profile.jsonif one doesn't exist. This ensures visual consistency across all generations. - Start with a template — Use
get_prompt_templatesto find a relevant template. Templates provide proven prompt structures that produce consistent results. - Generate a draft — Use
generate_imagewith model="gemini" (or "auto"). This is fast and cheap. - Review and iterate — Use
edit_imageto refine the draft. Always prefer editing over regenerating from scratch. - Finalize if needed — Only use model="pro" when the user approves a draft and needs production quality.
- Save to project — Use
save_assetto move from preview to project directory.
Prompt Engineering Rules
DO:
- Describe scenes narratively — "A warrior standing in a moonlit forest" not "warrior, moon, forest"
- Use positive framing — "An empty street at dawn" not "A street with no cars"
- Include composition — Mention shot type, layout, visual hierarchy
- Specify style explicitly — "Pixel art, 16-bit aesthetic" or "Clean vector illustration"
- Reference the style profile — Let the profile inject colors, typography, framework context
DON'T:
- Send raw keyword lists to the API
- Use negative prompts ("no X", "don't include Y")
- Skip the style profile when one exists
- Regenerate from scratch when an edit would work
- Use the
protier for drafts or iterative exploration (it costs 2xfast)
Model Selection Guide
| Task | model= | Cost | Why |
| Throwaway iteration | draft | ~$0.034/image | Cheapest; fine for composition checks |
| Draft mockups, editing | fast (default) | ~$0.067/image | Good quality, multi-turn editing |
| Final production assets | pro | ~$0.134/image | Legible text, highest fidelity |
| Unsure | auto | varies | Picks pro for finals, else fast |
| Design analysis | (text model) | ~$0.001 | Runs on Gemini Flash text, not an image model |
| Short video clips | veo-3.1-lite | ~$0.05/sec | Cheapest video |
| Balanced video | veo-3.1-fast | ~$0.10/sec | Default |
| High-quality video | veo-3.1 | ~$0.40/sec | Best quality |
Every image tier accepts a reference_image, so asking for style consistency
never forces a tier change.
Template Categories
Use get_prompt_templates to browse these:
- ui-mockups: Dashboard, settings, login, e-commerce, mobile app
- game-assets: Characters, textures, icons, backgrounds, UI elements
- landing-pages: Hero, features, pricing, CTA, testimonials
- web-components: Navigation, cards, modals, tables, forms
- icons: App icons, feature sets, illustrations, patterns, logos
Design Analysis Workflow
When reviewing designs:
- Use
analyze_designwith the appropriate focus and project_type - The analysis returns scored categories and specific issues
- Each issue includes an
edit_instruction— feed it directly toedit_image - Iterate: analyze → edit → analyze again
Style Profile
The .gemini-design-profile.json stores:
- Color palette (primary, secondary, background, surface, text)
- Typography preferences (font family, style)
- Framework context (React, Vue, Tailwind, etc.)
- Design system (Material, custom, etc.)
- Visual style keywords
All generation tools automatically apply this profile to prompts.
References
See the reference files for detailed guidance:
references/prompt-guide.md— Detailed prompt engineering techniquesreferences/project-types.md— Game, landing page, and web app specific guidancereferences/prompt-templates.md— Complete template library with examples
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

