design-bid-proposals

Design Bid Proposals

Applicable scenarios

When the user wants to:

• By default receive multiple proposals for a pitch
• Compare multiple UI/UX directions rather than just wanting a single proposal
• Explore multiple directions without deviating from explicit requirements
• Need a clear explanation of the differences among multiple proposals and the recommended direction to pursue

This skill also applies to:

• src/prototypes/<slug>/ Prototype creation
• src/components/<slug>/ Component creation

Relationship with Gemini CLI

This skilldoes not provide standalone scripts。

The execution method aligns with the existing /skills/gemini-cli-uiux/SKILL.md：

• Must be executed through Gemini CLI, and must not degrade into ordinary chat generation
• First write a local prompt file, then call Gemini sequentially
• For long contexts, prioritize letting Gemini read via local file paths
• Write files directly in the end, and only give the necessary summary in the reply

If the /skills/gemini-cli-uiux/SKILL.mdis already selected, then this skill only supplements the rules for "multi-proposal pitches" and does not repeatedly define Gemini's general execution specifications.

Hard rules

• By default generate 3 directions, but if the user explicitly requests another number, it must be generated as requested
• The number of proposals must always be based on the user's explicit request; only when the user does not specify should it fall back to the default 3 proposals
• Each direction must be written into its own file, not just given as a textual explanation
• Multiple proposals must maintain the same business problem and goal, and must not go off-topic
• Requirements the user has explicitly locked can only serve as shared constraints and cannot be used for differentiation
• Differences can only be drawn from 3–6 unlocked dimensions
• Multiple proposals must at least satisfy:P0 have 1 core difference,P1 have 1 core difference
• P2 can only enhance differences and cannot become the sole source of differences among multiple proposals
• If multiple proposals only change the skin, color, illustration, or motion effects, they are judged unqualified and must be redone
• When executing with Gemini, it is forbidden to use a single prompt to request the full text of multiple proposals at the same time
• The planning round may only output a dimension matrix; each proposal must be generated by an independent Gemini call
• As long as this skill is triggered, it forcibly enters pitch mode by default; unless the user explicitly states 退出比稿、不需要对比、只要单方案、直接落地一稿 , etc., it must not fall back to the single-proposal process

Proposal quantity rules

Default rules

If the user does not explicitly specify a quantity, by default generate 3 proposals:

• A 稳健型
• B 平衡型
• C 突破型

User-specified quantity

If the user explicitly specifies a quantity, for example 2、4、5, it must be generated strictly as requested.

The recommended default gradient is as follows:

• 2 案：稳健型、突破型
• 3 案：稳健型、平衡型、突破型
• 4 案：基准型、稳健型、差异型、突破型
• 5 案：基准型、稳健型、平衡型、差异型、突破型
• 6+ 案: continue expanding on the above basis 探索型、概念型、愿景型 and other gradients

If the user provides their own naming or tiering method, prioritize the user's naming and do not force the default gradient.

Three-layer differentiation framework

P0 Skeleton layer

Determines the physical form of the interface and is the highest-priority layer for creating differences.

• Spatial form and container:平铺式 (Page) / 叠层式 (Drawer/Modal) / 灵活空间 (Split-view/Canvas)
• Task flow:线性引导 (Step-by-step) / 模块枢纽 (Dashboard) / 并行操作 (Inline/Multi-task)

P1 Muscle layer

Determines content distribution and operational feel.

• Information hierarchy and density:高密度全量铺陈 / 核心收纳与隐藏 / 极简聚焦单点
• Interaction paradigm:纯点击与表单输入 / 快捷手势与微操作 / 高级拖拽与直接操纵

P2 Skin layer

Determines the interface's temperament and detail feel.

• Visual language:系统原生极简 / 现代卡片便当盒 / 探索性视觉
• Micro-feedback:工具化零动效 / 顺滑过渡 / 沉浸式物理反馈

Default three-option definitions

Only when the user has not specified a quantity, use the following default three-option definitions.

A Robust / Benchmark-led

• By default, reference 2–3 industry-leading products and extract common paradigms
• Prioritize reusing proven layouts, module organization, information hierarchy, and visual expression
• Emphasize familiarity, credibility, low comprehension cost, and low decision risk
• Mature solutions may be referenced, but a single competitor must not be copied with high similarity

B Balanced / Balanced

• Make moderate optimizations on mature paradigms
• Balance brand expression, usability, business goals, and implementation cost
• Suitable for most review and delivery scenarios

C Breakthrough / Differentiation-first

• Pursue memorability, expressiveness, and differentiation
• Can be bolder in structure, interaction, or visuals
• Must still satisfy the user's explicitly stated requirements and constraints

Execution process

1. First lock down shared constraints

First organize:

• Product goals and success criteria
• Page or component scope
• The user's explicitly expressed ideas, references, brand tone, and functional requirements
• Whether the user has explicitly requested the number of options
• Content that cannot be changed

If information is insufficient, prioritize using references/bid-requirements-checklist.md to fill it in.

2. Choose 3–6 variable dimensions

You must first determine which dimensions are:

• 已锁定: explicitly required by the user, and multiple options must remain consistent
• 可变化: can be used to create differences

Select only 3–6 from the variable dimensions to differentiate multiple options.

3. Plan first, then split into options, then summarize

This skill only provides templates and is not responsible for executing scripts.

It is recommended to write the prompt file to a temporary directory, for example:

• tmp/design-bid-proposals/<slug>/01-planning.md
• tmp/design-bid-proposals/<slug>/02-option-1.md
• tmp/design-bid-proposals/<slug>/03-option-2.md
• tmp/design-bid-proposals/<slug>/...
• tmp/design-bid-proposals/<slug>/99-summary.md

Then call Gemini CLI sequentially, one at a time.

3.1 Gemini execution red lines

When using Gemini CLI, the following order must be followed:

1. 规划轮 Output only the locked items, difference dimensions, and option matrix
2. Each option round generates only the current option, and must not output the body of other options at the same time
3. 汇总轮 Only responsible for comparison and summarization, and must not write the body of multiple options

If multiple option bodies appear in a single Gemini output at the same time, it is considered an execution error, and the result must be discarded and called again separately.

3.2 Gemini invocation method

Refer to /skills/gemini-cli-uiux/SKILL.md, and execute sequentially using Gemini CLI.

Example:

gemini -m gemini-3-pro -p "请严格阅读并执行文件：tmp/design-bid-proposals/<slug>/01-planning.md"

Then execute each single-option prompt in sequence:

gemini -m gemini-3-pro -p "请严格阅读并执行文件：tmp/design-bid-proposals/<slug>/02-option-1.md"
gemini -m gemini-3-pro -p "请严格阅读并执行文件：tmp/design-bid-proposals/<slug>/03-option-2.md"

Finally execute the summary prompt:

gemini -m gemini-3-pro -p "请严格阅读并执行文件：tmp/design-bid-proposals/<slug>/99-summary.md"

If the current environment cannot explicitly specify a model, but Gemini CLI can still run, continue execution and explain the actual situation in the final reply.

Output directory rules

Default three options

When the number of options is 3 and the default gradient is used, the directory is fixed as:

• src/prototypes/<slug>-a-safe/
• src/prototypes/<slug>-b-balanced/
• src/prototypes/<slug>-c-bold/

Or:

• src/components/<slug>-a-safe/
• src/components/<slug>-b-balanced/
• src/components/<slug>-c-bold/

User specifies another quantity

If the user specifies a quantity other than 3, the directories use a numbered form:

• src/prototypes/<slug>-option-1/
• src/prototypes/<slug>-option-2/
• ...
• src/prototypes/<slug>-option-n/

Or:

• src/components/<slug>-option-1/
• src/components/<slug>-option-2/
• ...
• src/components/<slug>-option-n/

Each direction directory must contain:

• spec.md
• index.tsx

Can be added as needed:

• components/

Final reply format

The final reply must contain:

1. Generation method for this run:Gemini CLI / 子代理 / 当前代理
2. The actual model, or the reason why the model cannot be explicitly specified
3. All output directories
4. A one-sentence overview of each option
5. A Markdown comparison table generated according to the actual number of options
6. Recommended direction to prioritize

The number of columns in the comparison table must match the actual number of options.

Quality check

• Whether the multiple options maintain the same business goal
• Whether they are generated according to the quantity requested by the user; if the user did not specify, whether it falls back to the default 3 options
• Whether the multiple options differ only along dimensions that are not locked down
• P0 and P1 whether both have substantive differences
• Whether the robust/baseline type references the mature paradigm of industry-leading products
• Whether all direction directories have generated spec.md and index.tsx
• Whether the final reply states the generation method and the comparison table generated according to the actual quantity

Resources

• references/bid-requirements-checklist.md
• references/bid-planning-template.md
• references/bid-option-template.md
• references/bid-summary-template.md