Prompt 652 words Copy
# Design from Reference: Pivot AI Page
Create an original, high-fidelity visual design inspired by the reference. Prioritize composition, typography, colors, spacing, and component styling over technical implementation.
## Reference
- **Product:** Pivot
- **Category:** AI Page
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/v/bf7874bd0fce27ed30c5-1600.webp)
- **Source:** https://www.pivotapp.ai/platform/ai-studio
Analyze the attached screenshot first. If no image is attached, open the screenshot link; if neither is accessible, ask for it rather than guessing.
## Visual Design Context
### Overall aesthetic
- **Character:** Darker and more atmospheric than Pivot's other pages: deep teal and black gradients, a luminous orb, motion-blurred photography, with light off-white sections in between.
### Page composition
- **Capture:** 2880 × 18716 screenshot pixels; 2× CSS scale (1440px viewport).
- **Structure:** Full-height dark hero with centered copy, orb and faint UI logs; logo marquee; problem section with a light diagram and a dark prompt panel; photo band with agent builder UI; MCP button; sourcing row with prompt UI; three-card "record beneath it" grid; dark accountability band with run-log UI; FAQ; closing statement; gradient footer.
### Information hierarchy
- **Priority:** Bold promise, trust in data, then accountability. Product fragments are kept small and secondary to the statements.
### Typography
- **Families:** Roobert for headings, DM Sans for body.
- **CSS scale:** Hero 44px centered in white, section headings 32px, card titles 14px semibold, body 12–14px.
### Colors & surfaces
- **Palette:** Dark #011515 to #0B2A26, light sections #FAFAFA, text white or #060609.
- **Accents:** Glowing mint and cyan orb, acid lime highlights, gradient-filled cards in the middle of the three-card grid.
### Components
- **Elements:** Orb with label chip, prompt input bars, agent run logs with bar charts, three tall feature cards (photo, gradient, light), FAQ accordion, black pill CTAs.
- **Geometry:** Content about 1140px wide, card radius 12px, tall 220px cards.
### Responsive
- **Mobile capture:** Hero orb scales down, panels and cards stack, photo bands crop to portrait.
### Adaptation guidance
- **Transfer:** For an AI page, lead with a calm visual metaphor, argue data quality before features and answer accountability head-on. Keep AI visuals abstract and replace UI fragments with your own.
## Content
**Instructions:**
Generate realistic example content that fits the selected design reference.
Create appropriate headlines, descriptions, labels, buttons, and supporting copy based on the type of interface being designed.
If a product or business description is provided, use it to guide the content.
Otherwise, invent a plausible fictional SaaS product appropriate for the reference.
Keep the content concise, coherent, and visually balanced.
Do not present fictional statistics, customer names, or testimonials as verified facts.
## Design Direction
**Instructions:**
Use the reference screenshot as the main source of visual inspiration rather than a strict layout template.
Preserve its most distinctive design characteristics, such as typography, visual rhythm, color relationships, component treatments, and overall aesthetic.
Feel free to modify section arrangements, proportions, spacing, and individual components to better suit my content.
Introduce original design decisions where they improve usability, composition, or brand consistency.
The result should clearly reflect the reference's visual language without looking like a direct reproduction.
Follow the visual identity of the reference design.
Use its typography, color palette, component styling, and overall aesthetic as the primary design direction.
Do not introduce an unrelated visual identity.
## Output
**Instructions:**
Generate a high-fidelity visual mockup of the requested interface.
Present the design as a polished, realistic website or product UI screenshot.
Prioritize visual composition, typography, spacing, colors, alignment, and component details.
Use the available image-generation or visual-design capabilities.
Do not replace the mockup with source code, a written design specification, or a textual description.
If direct visual generation is unavailable, clearly explain the limitation.
## Constraints
- Use the actual screenshot as the primary visual reference.
- Preserve essential messaging and factual accuracy.
- Prioritize visual quality and consistency.
- Do not invent unsupported product claims.
- Adapt structure and copy length for visual balance. Reference image Attach it to your message: assistants can’t open image links. Open in ChatGPT ↗ Open in Claude ↗
Build it in Lovable ↗ v0 ↗ Figma Make ↗
Opening a tool copies the screenshot so you can paste it with your prompt.