← Previous10 / 21Next →

Formcarry Form Setup

FormcarryForm backend

Design with AI

Create a new design inspired by Formcarry Form Setup, with your own content.

1Content

2Fidelity to the reference

Keeps its visual language, rearranges freely around your content.

3Your brand Optional

Use the reference style

Brand nameColorsFontsGuidelines

4Output

Prompt 868 words

# Design from Reference: Formcarry Form Setup

Create an original, high-fidelity visual design inspired by the reference. Prioritize composition, typography, colors, spacing, and component styling over technical implementation.

## Reference

- **Product:** Formcarry
- **Category:** Add & Edit
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/v/ed1dc198ebeb66330f11-1600.webp)

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

- **Style:** Clean developer setup page with white surfaces, pale lavender code blocks, bright blue actions and compact instructional typography.
- **Scale:** Source 2880 × 2412px; measurements estimate a 1440px-wide CSS layout at 2× capture scale.

### Page composition

- **Header:** Team switcher and product mark sit left, application navigation center, Create Form and avatar right.
- **Form context:** Feedback form title and identifier precede a broad Submissions/Setup/Analytics/Settings tab strip, with Setup selected.
- **Setup content:** An endpoint-copy control leads to framework tabs and three vertically numbered instructions. Code samples occupy the first two steps; a demo action ends the third.

### Information hierarchy

- **Connection first:** Your Form Endpoint isolates the integration URL before implementation instructions.
- **Implementation sequence:** Step 1 explains adding the endpoint; Step 2 explains field names; Step 3 confirms readiness and offers Create a live demo.
- **Technology choice:** HTML is selected among HTML, jQuery, Formcarry.js and React; no alternate code panel is visible.

### Typography

- **Families:** Sans-serif UI and instructions, monospace syntax-highlighted examples; exact font identities are unverified.
- **Roles:** Estimated form title 20px medium, section/step headings 16px, helper copy 14px/20px, navigation 14px and code 15–16px/19px.
- **Emphasis:** Blue numbers and selected tab labels guide scanning; descriptive text is muted slate.

### Colors & surfaces

- **Sampled palette:** ICC-aware sRGB samples include white #FFFFFF, lavender #F9F8FF, pale gray #F8F9FB, action blue #005FFF and pale blue #F0F5FF.
- **Code:** Blue attributes/tags, green string values and teal italic comments distinguish syntax within the lavender surface.
- **Depth:** Selected tabs and copy controls use white fills with faint shadows; borders and dividers remain very light.

### Components

- **Endpoint:** A roughly 475 × 48px pale control contains the URL and a white Copy button with icon.
- **Tabs:** Broad pale rounded strips contain compact white selected pills; framework and form tabs repeat the same visual language.
- **Steps:** Light-blue numbered circles around 40px align left of titles and supporting content.
- **Code panels:** Approximately 965px-wide lavender rectangles with modest corners and 20px padding; white Copy controls sit at upper right.
- **Completion:** Compact blue Create a live demo action includes a form icon. A circular chat widget with unread badge floats lower right.

### Visual rhythm

- **Alignment:** Step titles and code blocks share an inset edge to the right of the numbered circles; the larger page sections share common outer margins.
- **Spacing:** Wide vertical gaps distinguish steps, while titles/helpers remain tightly paired. Code panel height expands to its visible content.

### Responsive

- **Recommended adaptation:** Only desktop is observed. Collapse top navigation, allow tabs to scroll and make code samples horizontally scrollable.
- **Controls:** Keep copy actions reachable, wrap long endpoint text appropriately and preserve the numbered sequence.

### Adaptation guidance

- **Preserve:** Keep endpoint discovery before implementation, technology-specific tabs, copyable examples and a final test action.
- **Adapt:** Use actual endpoint and valid product-specific examples. Do not reproduce customer identifiers or unsupported framework options as generic filler.

## 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 imageAttach it to your message: assistants can’t open image links.

Build it in

Opening a tool copies the screenshot so you can paste it with your prompt.