agentsclimarketplace

Gemini prompting

Skill markbrutx/gemini-plugin-cc/skills/gemini-prompting

Internal guidance for composing effective Gemini prompts for visual analysis, design review, and coding tasksFrom its SKILL.md

Install
npx -y skills add markbrutx/gemini-plugin-cc --skill gemini-prompting

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.5 KB, as published. Nobody here has run it

Gemini Prompting Guide

Gemini excels at two things that Claude does not:

  1. Visual analysis — screenshots, mockups, UI layouts, design comparison
  2. Design/styling — color palettes, modern frontend aesthetics, creative UI

Prompt Structure

Good Gemini prompts follow this pattern:

<context>
Brief project context and what the user is working on.
</context>

<task>
Clear, specific instruction. One task per prompt.
</task>

<constraints>
Output format, style guidelines, framework requirements.
</constraints>

Visual Analysis Prompts

When the task involves visual input:

  • Describe what the screenshot/mockup shows
  • Be specific about what to look for (spacing, color, alignment, hierarchy)
  • Ask for structured observations, not free-form descriptions

Design/Styling Prompts

When the task involves UI aesthetics:

  • Reference the existing design system or framework (Tailwind, CSS vars, etc.)
  • Ask for specific CSS/component code, not just suggestions
  • Include the current state so Gemini can compare

Anti-Patterns

  • Do not dump entire codebases into the prompt — Gemini works best with focused context
  • Do not ask Gemini to reason about complex logic — that's Claude's strength
  • Do not ask Gemini to write backend/infrastructure code — delegate only visual/design tasks
  • Do not include prompts longer than ~4000 words — keep it focused

Keep looking

Skills are one crate of 608,475. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.