Review the following code for bugs, performance issues, and readability. For each issue found, explain why it matters and suggest a concrete fix. Prioritize correctness over style.
Take the following function and refactor it for clarity. Break it into smaller, well-named functions. Preserve the exact behavior and return type. Add brief inline comments only where the logic is non-obvious.
Write comprehensive unit tests for the following function. Cover the happy path, edge cases (empty input, null, boundary values), and expected error conditions. Use descriptive test names that explain the scenario and expected outcome.
Draft a concise professional email for the following situation. Use a neutral, confident tone. Keep it under 150 words. Include a clear subject line, one concrete ask or next step, and a polite closing.
Summarize the following meeting notes into a structured format with these sections: Key Decisions (bullet list), Action Items (who, what, deadline), Open Questions, and Next Meeting Agenda. Keep each bullet to one sentence.
Write constructive feedback for the following situation. Start with what is working well, then address what needs improvement with specific examples. End with a clear, actionable suggestion. Keep the tone supportive and direct.
A high-end product photograph of the item on a clean white marble surface. Soft directional lighting from the upper left, shallow depth of field with a gentle bokeh background. Subtle shadow underneath for grounding. Shot with a 90mm macro lens, color-accurate, editorial style suitable for a luxury e-commerce listing.
A wide establishing shot of a solitary research station on the edge of a massive ice shelf at twilight. Warm amber light spills from the windows onto blue-tinted snow. Aurora borealis arcs across the sky in green and violet. Cinematic composition, matte painting style, highly detailed environment art, 16:9 aspect ratio.
Create a detailed outline for a blog post on the following topic. Include a working title, a hook opening paragraph, 4-6 section headings with 2-3 bullet points each describing the key argument or content, and a conclusion that ties back to the opening. Target audience is technical professionals.
Explain the following technical concept in plain language that a non-technical stakeholder could understand. Use one concrete analogy, avoid jargon, and keep it under 200 words. End with why it matters for the business.
Write a documentation section for the following feature. Include a brief overview (2-3 sentences), a usage example with code, a table of parameters or options, and a "Common Pitfalls" note. Use clear, imperative language.
Provide a structured overview of the following topic. Cover: definition and core concepts, current state of the field, key debates or open questions, 3-5 notable papers or resources, and practical implications. Distinguish established consensus from active areas of research.
Analyze the competitive landscape for the following product or market. For each major competitor, list: name, core value proposition, target audience, pricing model, key strengths, and key weaknesses. Conclude with gaps and opportunities in the market.
Summarize the key findings from the following set of papers or articles. For each source, provide: main thesis, methodology, key findings, and limitations. Then synthesize common themes and contradictions across the sources. Highlight areas where further research is needed.