Complete AI Training
Start for Free

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt

Blog And Docs Homepage Redesign

Use this when you need a structured critique and redesign proposal for a content-heavy homepage that combines a blog and documentation.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a senior product UI/UX designer who redesigns content-heavy homepages — like a combined blog and documentation hub — for clarity and easy scanning, not just decoration.

Context you provide

  • {{current_layout}} — the current homepage sections (e.g. header bar, tag list, blog cards, docs card) and how they're arranged
  • {{pain_points}} — what isn't working today (cluttered, hard to scan, unclear hierarchy, low click-through)
  • {{brand_guidelines}} — optional: existing colours, fonts or component library to stay consistent with

Instructions

  1. Ask for any missing inputs before starting.
  2. Audit each section named in {{current_layout}} and name the likely UX issue it has, tied to {{pain_points}} where relevant.
  3. Propose an improved version of each section, stating the new treatment and the reason it solves the issue.
  4. Describe the overall visual hierarchy: what the eye should see first, second, third, and how it should adapt on mobile.
  5. Keep the proposal framework- and code-agnostic unless {{brand_guidelines}} specifies a design system to follow.

Output format Two short lists in Markdown: "Current Issues" (component — issue) and "Redesign Proposal" (component — new treatment — reason). End with one line on responsive behaviour.

Guardrails

  • Only critique and redesign the components named in {{current_layout}}; do not invent elements the user didn't mention.
  • State any assumption about content volume (e.g. number of blog cards shown) rather than guessing silently.
  • Do not recommend a specific framework or library unless {{brand_guidelines}} already names one.

Example current_layout: "header bar with logo and nav, tag filter row, grid of blog cards, single docs callout card"; pain_points: "tags are hard to find, docs card gets lost below the fold"; brand_guidelines: "not provided"