Gemini CLI

Overview

Use the Gemini CLI as a fast second-opinion engine for UI critique and code review. Keep prompts focused, include only the relevant context, and validate suggestions before applying.

Quick start

1. •

   Confirm the CLI binary and input mode:

   • •Use gemini as the default command name.
   • •Run gemini --help to identify supported flags and input modes.
   • •Prefer the positional prompt for one-shot runs (the --prompt flag is deprecated).
   • •If stdin is supported, prefer piping a structured prompt or a file.
2. •

   Run with full context once the CLI invocation is working; avoid test prompts to save tokens.

   • •Prefer --output-format text for readability or --output-format json for structured parsing.

Workflow

1. •

   Classify the request:

   • •UI/UX critique: layout, hierarchy, visual design, accessibility, interaction flow.
   • •UI alternative generation: new layout concepts or copy variations.
   • •Code second opinion: review logic, edge cases, performance, correctness.
   • •Architecture check: tradeoffs, risks, suggested alternatives.
2. •

   Gather context (keep it minimal):

   • •Goal, constraints, target platform, and success criteria.
   • •Relevant code, diffs, or snippets only (avoid entire repos).
   • •Any non-negotiables (design system, performance limits, deadlines).
3. •

   Run the CLI with a structured prompt.

4. •

   Validate the response:

   • •Check for incorrect assumptions or hallucinated APIs.
   • •Cross-check suggestions against project constraints.
   • •Apply only improvements that you can justify.

Prompt patterns

UI critique

Use when asking for layout and visual feedback.

You are a senior product designer.
Critique this UI for hierarchy, clarity, and accessibility.
Return: (1) top 3 issues, (2) quick wins, (3) risky changes.

Context:
- Platform: <web | iOS | Android | desktop>
- Audience: <persona>
- Constraints: <design system, brand, perf>

UI description or markup:
<brief description, screenshot notes, or key UI code>

UI alternatives

Use when you want multiple layout or copy options.

You are a UX lead.
Propose 3 alternative layouts with pros/cons and when to use each.

Context:
- Goal: <what must improve>
- Constraints: <grid, components, tokens>

Current UI summary:
<short summary>

Code second opinion

Use for review and risk spotting.

You are a staff engineer.
Review the code below for correctness, edge cases, and maintainability.
Return: (1) risks, (2) suggested fixes, (3) quick refactors.

Context:
- Language/stack: <...>
- Constraints: <perf, security, compatibility>

Code:
<snippet or diff>

Architecture tradeoffs

Use for system design or refactor choices.

You are a pragmatic architect.
Evaluate these options and recommend one. Include tradeoffs and failure modes.

Context:
- Goal: <...>
- Constraints: <cost, latency, team skills>

Options:
1) <option A>
2) <option B>

Notes

• •Avoid sending secrets or proprietary data unless explicitly approved.
• •Prefer short, specific prompts over broad requests.
• •If the CLI supports file inputs, prefer file paths over large inline text.