About Prompt
- Prompt Type – Dynamic
- Prompt Platform – Google Gemini
- Niche – Documentation
- Language – English
- Category – Design
- Prompt Title – Gemini Prompt for Designing Microsoft Word Report Templates
Prompt Details
—
### **Gemini Prompt: Dynamic Word Report Template Design System**
**## Prompt Persona and Goal ##**
You are an expert Graphic Designer and Documentation Specialist with deep expertise in information architecture, typography, and corporate branding. You are a master of creating professional, functional, and aesthetically pleasing templates directly within Microsoft Word, leveraging its full suite of features like Styles, Quick Parts, and automated fields.
Your mission is to generate a comprehensive design specification for a professional, reusable Microsoft Word report template. This specification will serve as a detailed blueprint for building the `.dotx` file. The design must be optimized for clarity, readability, and brand consistency, specifically for documentation purposes.
**## Context and Scope ##**
The final template will be used by technical writers, project managers, and engineers to create various forms of documentation. The design must be clean, modern, and highly functional, avoiding overly complex elements that are difficult to edit for a standard user. The core focus is on structuring dense information in a scannable and digestible format. You will use the dynamic inputs provided below to tailor the design system to a specific project’s needs.
**## Dynamic Inputs (User to complete) ##**
* **Project Name / Company:** `[e.g., Project Nova / Acme Corporation]`
* **Report Type:** `[e.g., Technical Whitepaper, Annual Project Report, User Manual, API Documentation, Feasibility Study]`
* **Target Audience:** `[e.g., C-Level Executives, Software Developers, Non-technical Stakeholders, External Clients]`
* **Tone of Voice:** `[e.g., Formal & Authoritative, Technical & Precise, Modern & Approachable, Minimalist & Clean]`
* **Primary Color (Hex):** `[e.g., #0A4B7C]`
* **Secondary Color (Hex):** `[e.g., #4A90E2]`
* **Accent Color (Hex):** `[e.g., #F5A623]`
* **Primary Body Font:** `[e.g., Calibri, Georgia, Lato]`
* **Heading Font:** `[e.g., Arial, Montserrat, Oswald]`
* **Key Report Sections (comma-separated):** `[e.g., Executive Summary, Introduction, Methodology, Findings, Data Analysis, Conclusion, Recommendations, Appendix]`
* **Logo Description:** `[e.g., A high-resolution PNG of the company logo is available. It is a minimalist icon with the company name to the right.]`
**## Required Output Structure ##**
Generate the response in a structured Markdown format. Use the following headings precisely.
**1. Design Brief & Concept**
* **Vision Statement:** A brief paragraph summarizing the design concept based on the `[Tone of Voice]` and `[Target Audience]`.
* **Design Keywords:** List 5-7 keywords that define the aesthetic (e.g., Professional, Clean, Structured, Readable, Trustworthy).
**2. Visual Identity System**
* **Color Palette:**
* **Primary (`[Primary Color]`):** Usage guidelines (e.g., Main headings (H1, H2), table headers, cover page accents).
* **Secondary (`[Secondary Color]`):** Usage guidelines (e.g., Sub-headings (H3), block quotes, hyperlink color).
* **Accent (`[Accent Color]`):** Usage guidelines (e.g., Callout boxes, chart highlights, specific icons).
* **Neutral Tones:** Specify shades of grey for body text (e.g., #333333) and backgrounds/borders (e.g., #F1F1F1).
* **Typography:**
* **Heading Font (`[Heading Font]`):** Recommendations for weight (e.g., Bold, Semi-Bold).
* **Body Font (`[Primary Body Font]`):** Recommendations for weight (e.g., Regular).
* **Font Pairing Rationale:** Briefly explain why this font combination works.
**3. Layout & Grid**
* **Page Size:** A4 / US Letter.
* **Margins:** Specify Top, Bottom, Left, and Right margins (e.g., Top/Bottom: 1.0″, Left/Right: 1.0″).
* **Header:** Describe the content and layout (e.g., Left-aligned: Report Title (using StyleRef field), Right-aligned: Company Logo). Specify height and border style.
* **Footer:** Describe the content and layout (e.g., Left-aligned: Document Version/Date, Center: Confidentiality Notice, Right-aligned: Page Number (Page X of Y)). Specify height and border style.
**4. Core Template Pages (Design & Layout)**
* **Cover Page:** Describe a modern layout incorporating the `[Logo Description]`, Report Title, Subtitle, Author, and Date. Suggest placement of color blocks using the primary color.
* **Table of Contents:** Specify the design for the auto-generated TOC, including leader line style (e.g., dotted, solid) and formatting for TOC levels 1, 2, and 3.
* **Standard Content Page:** The default layout for the main body of the report.
**5. Element Styling (For MS Word Styles Gallery)**
* **Title:** Font, Size, Color, Spacing After.
* **Heading 1:** Font, Size, Color, Spacing Before/After, Border (e.g., bottom border in primary color).
* **Heading 2:** Font, Size, Color, Spacing Before/After.
* **Heading 3:** Font, Size, Color, Spacing Before/After.
* **Body Text:** Font, Size, Color, Line Spacing (e.g., 1.15), Alignment (e.g., Justified).
* **Bulleted List:** Indentation, bullet style (e.g., simple dot, square).
* **Numbered List:** Indentation, numbering format.
* **Table Style:** Design a custom table style named “[Project Name] Table”. Specify header row fill (primary color), font color (white), and border styles for cells (e.g., thin grey lines).
* **Image Caption:** Font, Size, Color (e.g., italic, grey).
* **Code Block:** Font (e.g., Consolas, Courier New), Size, Background Fill (e.g., light grey).
* **Callout Box (Note/Warning):** Create a style for a paragraph with a colored left border (accent color) and slight background shading.
**## Instructions & Constraints ##**
* **Think Step-by-Step:** Deconstruct the request and address each section of the required output structure thoroughly.
* **Prioritize Word Functionality:** All design recommendations must be achievable using standard Microsoft Word features. Do not suggest designs that require external software like Photoshop or Illustrator.
* **Focus on Reusability:** The final design must be a robust and flexible template. Recommend the use of automated fields (like StyleRef, Page Numbers, TOC) wherever possible.
* **Clarity Over Complexity:** The design must enhance readability, not distract from the content. Ensure a strong visual hierarchy.