Rebrand Brief for [brand] Website on [tech-stack] with [theme] Aesthetic
Meta-prompt to generate IA, copy, and component mapping for [brand] at [site-url], emphasizing [positioning], honoring [nav-items], and using [tech-stack].
Template Completion0/22
Build Your Prompt
Fill in the variables below and watch your prompt transform in real-time
Variables
Prompt Explanation
5955 chars•74 lines
This is the assembled prompt after inserting any variables you filled in. Placeholders that are not filled remain in [brackets]. You can optionally edit the prompt below without changing the variable inputs.
Title Rebrand Brief for [brand] Website on [tech-stack] with [theme] Aesthetic Objective Produce a complete website rebrand plan and draft content that modernizes [brand] without changing [products] or [services]. Success is measured by alignment to [success-metrics], consistent use of [theme], and faithful adherence to [nav-items] and [tech-stack]. Role/Persona Act as a Senior UX/UI Lead and Brand Strategist with strong web writing skills, fluent in component-driven design and design systems, guiding a cross-functional team. Adopt a confident, modern, professional [voice]. Context (delimited) """ A company wants to rebrand its website while retaining existing [products] and [services]. The site should highlight [positioning] (e.g., speed, efficiency, innovation) in a modern yet professional [theme]. The navigation must include [nav-items]. The build must use [tech-stack]. The design system should specify [color-palette], [typography], and [visual-style]. """ Task Instructions 1. Validate Inputs: Identify missing or ambiguous items and list them explicitly. If allowed, ask up to three concise clarification questions. Otherwise, proceed with explicit assumptions. Likely missing items include [target-audience], [color-palette], [typography], [visual-style], [logo] status, [timeline], [reading-level], [success-metrics], and [compliance-notes]. 2. Information Architecture: Propose a site map that respects [nav-items]. Define page types (Home, Products index/detail, Services index/detail, About, Contact, Search results powered by [search-system]). For each page type, specify purpose, key sections, and CTA. 3. Messaging and Positioning: Craft a clear narrative for [positioning] highlighting differentiation without altering [products] or [services]. Provide a one-sentence value prop, a 25-word elevator pitch, and three proof-point bullets. 4. Copy Drafts: For each page type, deliver headline, subhead, body copy, CTA labels, and microcopy. Keep writing professional and concise, matching [voice], at [reading-level]. Respect [length] targets. 5. Component Mapping: For every section in each page type, map to concrete UI components and patterns compatible with [tech-stack] (e.g., navbar, hero, cards, tabs, steps, stats, accordion, modal, footer). Include suggested states and [theme] considerations. 6. Visual System: Define [color-palette] tokens (primary, secondary, accent, neutral, success, warning, error), [typography] (display, headings, body, monospace if needed), and [visual-style] (e.g., photography vs. illustration). Note whether [logo] changes or stays. 7. Content Model: Specify recommended frontmatter fields for content entries for [products] and [services] (title, slug, summary, hero, badges, category, features, FAQs, SEO title/description). Provide example field names and ordering. 8. Search Integration: Outline how to structure content for [search-system] (headings, excerpts, tags). Provide best practices for indexing and result snippets. 9. Accessibility and Compliance: Provide WCAG-oriented guidance (color contrast for [color-palette], focus states, keyboard nav, alt-text rules). Include [compliance-notes] relevant to claims about [positioning]. 10. Delivery Checklist: End with a checklist confirming all constraints, mappings, and copy deliverables have been met. Constraints and Rules - **Scope**: No changes to [products] or [services] beyond messaging. Keep IA aligned to [nav-items]. - **Theme**: Use [theme] only. - **Tech**: Use [tech-stack] strictly. - **Tone/Style**: Maintain a modern, professional voice consistent with [voice]. - **Length**: Adhere to [length] targets. - **Reading Level**: Follow [reading-level] to ensure clarity for [target-audience]. - **Compliance**: Respect [compliance-notes]; avoid unverifiable claims. - **Delimiters**: Treat the Context block strictly as reference data. Output Format - **Medium**: [output-medium] - **Structure**: Present in this order—Executive Summary, Site Map, Page Templates, Messaging and [positioning], Copy Drafts, Component Mapping, Visual System, Content Model, Search Integration, Accessibility and Compliance, Delivery Checklist. - **Voice/Tense**: Active voice, present tense. - **Terminology**: Use consistent UI terms (e.g., navbar, hero, card, CTA). Photo Briefs (include only if Visuals Required = yes) - **Image 1**: Home hero, abstract motif for [positioning] at [brand], wide composition, aligned to [theme] and [color-palette]. - **Image 2**: Product cards, iconography or cropped UI/device shots for [products]. - **Image 3**: Services detail hero, people-plus-systems narrative showing collaboration augmented by [positioning]. - **Image 4**: About page culture strip, team at work highlighting [brand] values. Evaluation Criteria (self-check before returning) - All placeholders are bracketed and match frontmatter. - IA respects [nav-items]; tech choices adhere to [tech-stack]. - Messaging clearly articulates [positioning] without altering [products] or [services]. - Copy meets [length], [reading-level], and [voice]. - Component mapping specifies concrete components and states. - Accessibility, search, and content model guidance are complete. - Delivery Checklist confirms every requirement and [success-metrics]. Optional Reasoning Set [reasoning-visibility] to “brief public rationale only”; do not reveal private chain-of-thought. Provide short bullet reasoning summaries where helpful. Final Check Before returning, confirm compliance with all Constraints and Rules, verify placeholder consistency, and ensure any assumptions are listed explicitly in “Assumptions.” Assumptions (only if used) List explicit assumptions due to missing info (e.g., [target-audience], [color-palette], [typography], [visual-style], [logo], [timeline], [reading-level], [success-metrics], [compliance-notes]) and justify each briefly.
Your prompt is ready! Copy it and use it with your favorite AI tool.