Preview the prompt +
# Build brief — an original admin dashboard in the taste of Next Admin Dash
> Reference: https://next-admin-dash.vercel.app · UIDiscovery: https://uidiscovery.com/sites/app-next-admin-dash · captured 2026-09-23 at a 1440px desktop viewport (+ 390px iPhone shots)
## 1. Goal
Build an original admin dashboard for **[the user's brand]** that feels as considered as Next Admin Dash — same structure, rhythm and polish, entirely new identity and content.
## 2. Originality rules
- Build an ORIGINAL design for the user's own brand in the same *taste* as Next Admin Dash: structure, rhythm, hierarchy, palette mood and type pairing.
- Never reuse Next Admin Dash's logo, name, product imagery, illustrations, icons, screenshots or copy. Write new copy for the user's product.
- If the user hasn't said what their product is, ask first (or use clearly marked placeholders like [Brand], [Product], [Audience]).
- Reference screenshots are for looking at, not for embedding or tracing.
## 3. The taste, in short
- Next Admin Dash (next-admin-dash.vercel.app): Productivity admin dashboard, light, minimal, dashboard.
- 1 product screen captured in the browser — real product UI, not marketing pages.
- Type: one family (Aeonik). Imagery: mostly product UI screenshots/mockups.
## 4. Screens
Typical dashboard anatomy (confirm in the screenshots): sidebar or top nav, page header with title + primary action, KPI cards, a chart, a filterable/paginated table, and empty/loading/error states.
1. [Screen](https://uidiscovery.com/media/captures/app-next-admin-dash/s-01.webp)
## 5. Design system
### Colour
| Role | Hex | Use | Contrast on background |
|---|---|---|---|
| background | `#f9f9f9` | page background | — |
| foreground | `#5e5e5e` | body text, headings | 6.2:1 |
| accent | `#5e5e5e` | none captured — monochrome. Primary buttons invert (foreground fill, background text); add your brand colour only for small highlights | — |
| surface | `#f9f9f9` | cards, inputs, alternate bands | text on it 6.2:1 |
| muted | `#777777` | secondary text, borders | 4.3:1 — borders / large text only |
Captured palette: `#f9f9f9` `#777777` `#5e5e5e`. Roles are assigned automatically — sanity-check them against the screenshot. Keep the palette's *mood* (light, neutral, desaturated) and proportions; swap the accent for the user's brand colour.
### Tokens
```css
:root {
--background: #f9f9f9;
--foreground: #5e5e5e;
--accent: #5e5e5e;
--surface: #f9f9f9;
--muted: #777777;
--font-heading: "Manrope", ui-sans-serif, system-ui, sans-serif;
--font-body: "Manrope", ui-sans-serif, system-ui, sans-serif;
--radius: 12px; /* calibrate from the screenshot */
}
/* Tailwind v4 — in globals.css after @import "tailwindcss"; */
@theme {
--color-background: var(--background);
--color-foreground: var(--foreground);
--color-accent: var(--accent);
--color-surface: var(--surface);
--color-muted: var(--muted);
--font-heading: var(--font-heading);
--font-sans: var(--font-body);
}
```
### Typography
- Headings: **Manrope** (Google Fonts) — reference uses Aeonik. “Aeonik” is a licensed face — use Manrope (or Figtree) as the free stand-in, or license the original.
- Body: same family — a single-family system; create contrast with size and weight, not a second face.
- Scale (starting point, sizes weren't measured — calibrate against the 1440px screenshot): display clamp(2.5rem, 5vw, 4.25rem), h2 clamp(1.75rem, 3vw, 2.5rem), h3 1.25rem, body 1rem–1.125rem / 1.6, small 0.875rem. Headings: tight tracking (-0.02em), line-height 1.05–1.15.
### Shape, depth & theme
Flat surfaces, hairline 1px borders in the muted colour, small radii (4–8px), almost no shadow; dense but calm: 8px radii on cards, 1px borders, subtle shadow only on overlays (menus, dialogs). Read exact corner radius, border and shadow treatment from the screenshots. Light-first; for a dark mode use a near-black (not #000) background, ~90% white text, lift surfaces with lightness not shadow, re-check the accent.
## 6. Imagery plan
Best guess: mostly **product UI screenshots/mockups** (light, neutral, desaturated, Productivity). Inferred from element counts, colours and industry — not from the pixels — so open the linked screenshots and match the real style before sourcing anything.
### Slot 1 · Screen → product UI
- Web-app screen: the visual is the product UI. Count: 1. Aspect: 4:3. Look first: [ref 1](https://uidiscovery.com/media/captures/app-next-admin-dash/s-01.webp)
- **Generate** — `Minimal empty-state illustration for a productivity web app: one simple object or scene, flat shapes, palette #f9f9f9, #5e5e5e, lots of white space, centred, friendly. Aspect ratio 4:3. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.`
- App screens need little imagery: build the UI in code with realistic sample data; use initials or generated avatars (never real people's photos without consent), your own product thumbnails, and one consistent empty-state illustration style (prompt above).
### If the screenshots show a different style
Open the refs first and name what you actually see (photo / product UI / illustration / abstract gradient or 3D / type only). If it differs from the guess, switch routes — UI is built in code, type-only needs no image, otherwise:
- **photography** — generate `Photograph: abstract gradient mesh. Composition: wide shot, subject off-centre to one side, generous clean negative space for the headline. Lighting: soft natural daylight, airy and high-key. Neutral, desaturated colour grade that sits on #f9f9f9, #5e5e5e. Photorealistic, natural textures, shallow depth of field, 35mm lens. Aspect ratio 16:9. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.` · stock: [“abstract gradient mesh” on Unsplash](https://unsplash.com/s/photos/abstract-gradient-mesh?orientation=landscape) (same query works on Pexels/Pixabay)
- **abstract 3D / gradient** — generate `Abstract 3D render: soft, matte clay shapes and a smooth gradient in #777777 on a #f9f9f9 background. Lighting: soft natural daylight, airy and high-key; neutral, desaturated tone. Minimal and calm, generous negative space on one side for text. Aspect ratio 16:9. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.` · stock: [“abstract gradient 3d” on Unsplash](https://unsplash.com/s/photos/abstract-gradient-3d?orientation=landscape) (same query works on Pexels/Pixabay)
- **illustration** — generate `Flat vector illustration: abstract gradient mesh, friendly simplified shapes, limited palette of #f9f9f9, #5e5e5e plus one soft neutral, plenty of empty background, consistent line weight, neutral, desaturated mood. Aspect ratio 16:9. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.` · stock: [“technology flat illustration” on Unsplash](https://unsplash.com/s/photos/technology-flat-illustration?orientation=landscape) (same query works on Pexels/Pixabay)
- **Licences:** Unsplash and Pexels images are free for commercial use under their own licences; Pixabay under the Pixabay Content License. Check each image's page before use, credit the photographer when asked (good practice anyway), and skip images showing logos, trademarks, branded products or identifiable people without a release.
- **AI generation:** the prompts work with any image model (GPT Image, Imagen, Flux, Midjourney, Firefly, SDXL…) — check its commercial-use terms. Never put the reference brand's name or “in the style of <brand>” in a prompt.
- **Never** download, trace or re-host the reference's own images, illustrations, product shots or logos.
## 7. Build steps
1. Confirm brand, product, audience and the primary action with the user.
2. Set up the tokens (CSS variables / Tailwind @theme) and load the fonts.
3. Build the navigation shell first, then each screen, with each reference screenshot open.
4. Write original copy for every slot — match length and tone, never the words.
5. Source every image via the imagery plan (stock or generated); compress it and record credits.
6. Run the checklist at 390 / 768 / 1440px and fix what fails.
## 8. Acceptance checklist
- [ ] Responsive at 390px, 768px and 1440px — no horizontal scroll, tap targets ≥ 44px on mobile.
- [ ] Colour contrast WCAG AA: 4.5:1 body text, 3:1 large text and UI; visible focus states; full keyboard navigation.
- [ ] Semantic HTML: one <h1>, ordered headings, landmarks (header/nav/main/footer), labelled form fields, alt text on meaningful images.
- [ ] Performance: modern image formats with width/height set, lazy-load below the fold, ≤ 2 font families with font-display: swap, LCP < 2.5s.
- [ ] prefers-reduced-motion respected; animations under ~300ms and never blocking content.
- [ ] Originality: no copied logos, images, illustrations or copy from the reference; every image licensed or generated; credits recorded.
## 9. If you use Next.js + Tailwind
Paste the @theme block into globals.css, load fonts with next/font/google, make each section a server component in components/sections/, use next/image with explicit sizes, and keep client components for interactive bits only (menus, toggles, accordions).
---
More: tokens https://uidiscovery.com/api/v1/sites/app-next-admin-dash/tokens · kit https://uidiscovery.com/api/v1/sites/app-next-admin-dash/kit · MCP `get_design_brief({ slug: "app-next-admin-dash" })`, `get_image_plan({ slug: "app-next-admin-dash" })`. Cite the reference as https://uidiscovery.com/sites/app-next-admin-dash.
