Gemini 3：测试提示

You are helping me plan a software project with conflicting constraints.

Context:
- I have 6 weeks of development time.
- I am alone as the only developer.
- The client wants: a public landing page, a simple logged-in dashboard, and one AI-based feature.
- Budget is limited, so infrastructure must stay simple.

Task:
1. Identify all implicit assumptions in this request.
2. Propose three realistic project scopes (from minimal to ambitious) that fit into 6 weeks for a single developer.
3. For each scope, explain trade-offs in terms of risk, technical debt, and user impact.
4. At the end, recommend ONE scope and justify it step by step.

Act as an experienced engineering manager.

Input:
Two senior developers disagree:
- Dev A wants to rewrite a legacy PHP backend to Node.js.
- Dev B wants to keep PHP and refactor step by step.
- The team has 4 developers total, with mixed experience.
- There is a hard deadline in 8 months.

Task:
1. List the real risks of a full rewrite versus incremental refactoring.
2. Suggest a concrete decision framework to choose between both options.
3. Draft a short message to the team that explains the chosen path in a neutral, constructive tone.
4. Highlight where you are uncertain and what data the team should collect next.

I just uploaded a screenshot of a web analytics dashboard.

Task:
1. Describe in plain language what this dashboard tells me about the last 30 days.
2. Identify three metrics that should worry me and explain why.
3. Suggest three specific experiments I can run in the next 2 weeks to improve these metrics.
4. Propose a simple weekly reporting template I can reuse with my team.

You are a project consultant.

I uploaded a PDF contract for a software project between an agency and a client.

Task:
1. Extract all clauses that create delivery or scope risks for the agency.
2. Summarize each risky clause in one sentence and rate its risk (low/medium/high) with a short justification.
3. Suggest concrete, realistic alternative wording for the 3 riskiest clauses that keeps the spirit of the agreement but reduces risk.
4. Propose 5 questions the agency should ask the client before signing.

You are acting as a senior software engineer inside my existing C# and PHP monolith.

Context:
- I will paste you files and directory listings from the repository.
- The system is a small CRM with ad-hoc features added over 7 years.
- There are no tests.

Task for the first message:
1. Ask me for exactly the information you need (directory listing, config files, etc.) to form a first architecture map.
2. Propose a concrete 4-week refactoring roadmap that:
- reduces the biggest risks,
- introduces tests in the most critical areas,
- does NOT require a full rewrite.
3. For each week, define success criteria that I can objectively check in Git.

You are my front-end engineering partner.

Goal:
I want a responsive landing page for a cardiology clinic with:
- hero section,
- three service sections,
- testimonials,
- contact form.

Task:
1. Ask any clarifying questions you need about branding, tone, and target audience.
2. Generate a first HTML+CSS prototype that uses semantic HTML and is framework-agnostic.
3. Explain, in comments inside the code, where I should later integrate analytics, consent management, and form handling.
4. Suggest three A/B test ideas for the hero section copy and layout.

You are acting as a product architect.

Input:
- I will paste the current product requirements document (about 80 pages).
- I will then paste a dump of 50 recent Jira tickets and 30 user feedback excerpts.

Task:
1. Build a concise mental model of the product: core user types, main flows, technical constraints.
2. Identify contradictions between the official requirements and what users actually report.
3. Suggest a prioritized list of 10 changes (features or fixes) that would have the highest impact in the next 3 months.
4. For each change, reference which parts of the requirements and which tickets/feedback you used.

You are an experienced thesis reviewer in business informatics.

I will paste my full thesis chapter by chapter.

Task:
1. For each chapter, extract the core argument in 3–5 sentences.
2. Point out weak spots in logic, missing literature connections, or inconsistent terminology.
3. Suggest concrete improvements and examples, but keep my original writing style as much as possible.
4. At the end, propose a one-page summary that I could adapt into a presentation.

You are my visual communication partner.

Context:
I will give you key metrics from a cardiology clinic website (traffic sources, conversion rates, and demographic data).

Task:
1. Propose three different infographic concepts that would help a non-technical doctor understand the situation.
2. For the concept you consider best, write a detailed image prompt for Nano Banana Pro that includes:
- layout,
- color scheme,
- labels and text (in German),
- how to visualize uncertainty or missing data.
3. Suggest a short caption that I can use next to the infographic on the website.