vibeyour website Hire us
All prompts
WordPress Creative Portfolio 14.2k chars

Vibe Code a Portfolio Website

Free vibe coding prompt to build a WordPress designer portfolio. Case studies, services, blog, project inquiry form, and CreativeWork schema. Full professional architecture.

Tested with: ChatGPT, Claude · Updated 2026-08-11 · License: do whatever you want, it's yours
wp-portfolio.prompt · 14.2k chars
Plan and produce a complete WordPress portfolio site architecture for a
solo designer / developer or small studio, focused on case studies and
client inquiries. Output should be production-ready.

═══════════════════════════════════════════════════════════════
BUSINESS DETAILS
═══════════════════════════════════════════════════════════════
- Name: [DESIGNER / STUDIO NAME]
- Discipline: [Branding / Web design / Product design / Full-stack dev]
- City: [CITY]
- Services offered: [3-5 services with starting prices]
- Engagement models: project-based, retainer, advisory
- Goals: 1-2 new high-quality clients per quarter
- Existing assets: logo, ~5-10 case-study projects

═══════════════════════════════════════════════════════════════
BRAND
═══════════════════════════════════════════════════════════════
- Brand colors: pure white (#ffffff) + near-black ink (#0a0a0a) + ONE
 accent (let user pick: ochre / electric green / muted slate). Override
 if user provides; AA-contrast for body.
- Type: high-contrast display serif for headings (PP Editorial New
 alternative, Cormorant Garamond) + Inter Tight for body + monospace
 for code (JetBrains Mono).

═══════════════════════════════════════════════════════════════
WORDPRESS STACK
═══════════════════════════════════════════════════════════════
- Theme: Bricks Builder + a lightweight starter theme OR a custom block
 theme. Bricks is recommended for portfolio sites because of the design
 freedom and performance. Justify briefly.
- Plugins (WP-CLI):
 wp plugin install --activate 
 bricks 
 advanced-custom-fields 
 wpforms-lite 
 wp-rocket 
 shortpixel-image-optimiser 
 wordpress-seo 
 better-search-replace
- Forms: WPForms or Fluent Forms for inquiry routing

═══════════════════════════════════════════════════════════════
DATA MODEL
═══════════════════════════════════════════════════════════════
- CPT `project` (case studies)
- ACF fields on `project`:
 - client (text)
 - year (number)
 - role (text, e.g., "Brand strategy & visual identity")
 - services_rendered (taxonomy: service_type)
 - hero_image (image)
 - cover_video (file/url optional)
 - problem_statement (wysiwyg)
 - approach (wysiwyg with image gallery)
 - outcome (wysiwyg)
 - metrics (repeater: label + value, e.g., "3x conversion" / "12 weeks
 to launch")
 - testimonial (group: quote + author + role)
 - live_url (url)
 - gallery (image gallery)
 - next_project (post object, for navigation)
- Taxonomies:
 - `service_type` (Brand identity / Web design / Product design / Dev)
 - `industry` (SaaS / Hospitality / Healthcare / etc.)

═══════════════════════════════════════════════════════════════
SITE MAP
═══════════════════════════════════════════════════════════════
1. Home
2. Work (case studies index)
3. Work > Project detail
4. Services
5. About
6. Process
7. Notes / Blog (optional, for SEO)
8. Contact / Inquire
9. Privacy

═══════════════════════════════════════════════════════════════
HOMEPAGE, BLOCK MARKUP
═══════════════════════════════════════════════════════════════
1. Sticky nav (minimal): wordmark left, anchor nav center, "Inquire"
 ink-outline pill right
2. Bold hero: eyebrow with line marker, large two-line headline ("I
 design things you can *trust*"), 1-line subhead, single CTA ("View
 work"), no decoration
3. 3-5 selected projects in big editorial cards (alternate left/right
 image-text on desktop, stack mobile)
 - Each: full-bleed cover image, project title (display serif), brief
 1-line description, "View case study →" link
4. About strip: small portrait + 3-paragraph bio
5. Services preview: 3-4 cards (no icons, just typography), each with
 starting price
6. Process: 4 steps in horizontal row (Discovery → Design → Build →
 Deliver)
7. Clients worked with (typeset names in a quiet row, no logos)
8. Selected testimonial (long pull-quote, large italic serif)
9. Contact CTA band: large headline ("Have a project in mind?") +
 "Inquire" CTA

═══════════════════════════════════════════════════════════════
PROJECT DETAIL TEMPLATE
═══════════════════════════════════════════════════════════════
- Cover image full-bleed (max 1600px)
- Project meta sidebar (sticky on desktop): client, year, role, services
 (chip list), live link
- Problem / Approach / Outcome sections, each with hero + body, optional
 inline imagery
- Process imagery / sketches grid
- Metrics callouts (3-4 large numbers with labels)
- Testimonial pull-quote (large italic serif, attribution small)
- Next / Previous project navigation at bottom

═══════════════════════════════════════════════════════════════
SERVICES PAGE
═══════════════════════════════════════════════════════════════
- 3-5 service offerings (e.g., Brand Identity / Web Design / Webflow
 Dev), each with:
 - Service name (display serif)
 - 2-paragraph description
 - Deliverables list (in prose with check icons)
 - Starting price ("From $X,XXX")
 - Engagement model (project / retainer / hourly)
 - 1-2 case studies linked
- Engagement models section: project vs retainer vs advisory
- FAQ specific to working with you (8-10 items)
- Contact CTA at bottom

═══════════════════════════════════════════════════════════════
INQUIRY FORM
═══════════════════════════════════════════════════════════════
- Multi-step (3 steps):
 Step 1: name, email, company (optional)
 Step 2: project type (select), budget range (select), timeline (select)
 Step 3: where you found me, brief project description
- Anti-spam: Cloudflare Turnstile + honeypot field
- Routing: email to you + optional Slack webhook
- Success state: "I'll reply within 2 business days" + suggested reading
 (link to a recent case study)

═══════════════════════════════════════════════════════════════
SEO & SCHEMA
═══════════════════════════════════════════════════════════════
- Schema: Person, CreativeWork (project), Organization (if studio)
- Image SEO: descriptive alt text, file naming
- Internal linking: project → services → related projects
- Open Graph image per project (project hero)

ADDITIONAL SEO REQUIREMENTS (implement all of these):

On-Page SEO for Every Page:
- Yoast/RankMath meta title template: "[Page Title] | [Site Name]" (under 60 chars)
- Meta description per page: 150-160 chars, include primary keyword + CTA
- Exactly ONE H1 per page — use the real, human headline; keep keywords in the title and meta, not the visible H1
- Logical H2 > H3 heading hierarchy, never skip a level
- Headings should include secondary keywords naturally,
  keep the section's real, human label (keywords in title and meta, not stuffed headings)
- Every image must have a descriptive alt attribute with keywords
- Internal links between related content using descriptive anchor text

Structured Data (JSON-LD via Yoast/RankMath + manual where needed):
- Primary schema types: ProfessionalService, Person, CreativeWork
- BreadcrumbList on all pages
- FAQPage schema on any page with an FAQ/accordion section
- Article schema on all blog posts (auto via Yoast)
- Validate schema with Google Rich Results Test before launch

Open Graph & Social Sharing:
- og:title, og:description, og:image, og:url on every page
- twitter:card=summary_large_image on every page
- Default OG image set in Yoast; per-page overrides for key landing pages
- OG images should be 1200x630px, branded, with clear text

Content SEO:
- Write real, useful body copy for every page (not just headings and CTAs).
  Every major section needs at least 2-3 sentences of descriptive text
  that search engines can index.
- Blog content strategy: 10 seed articles targeting long-tail keywords
  related to "designer / developer portfolio". List the titles and target keywords.
- Use the primary keyword once or twice where it reads naturally; keep the rest in titles and meta, never stuffed.
- Every CTA should use descriptive anchor text with the service keyword.

Technical SEO:
- XML sitemap split by post type (auto via Yoast)
- Canonical tags on all pages (auto via Yoast)
- robots.txt: allow all, point to sitemap
- 301 redirects plan for any renamed/moved content
- Breadcrumbs enabled via Yoast + schema
- Clean permalinks: pick one post-permalink base that fits the site (do not force /blog/ on a post-centric site); /%postname%/ is fine for pages
- Lazy load all images below the fold, eager load hero/LCP image
- Core Web Vitals targets: LCP < 2.5s, CLS < 0.1, INP < 200ms

SECURITY, ACCESSIBILITY & HONESTY (required):
- Escape all output (esc_html/esc_url/esc_attr), sanitize all input (sanitize_text_field + wp_unslash), and use a nonce + current_user_can() on every form handler and custom action. Emit JSON-LD with wp_json_encode().
- Target WCAG 2.2 AA: visible :focus-visible states, <label for> on every field, full keyboard operability, and @media (prefers-reduced-motion: reduce) around all motion.
- Never fabricate business data, testimonials, ratings, credentials, or stats; leave labeled {{TODO}} placeholders for anything the user has not supplied.
- PLUGIN INSTALL: some listed plugins are premium or not in the wordpress.org directory, so a single `wp plugin install` will error out. Split the list into free (wp.org) vs premium (upload/license), verify each slug, and note that gallery/group ACF fields and ACF Blocks need ACF Pro.
- Commit to ONE paradigm: a block theme (theme.json + block templates) OR a classic theme/builder — never mix them. If a plugin already owns a post type or feed (inventory, sermons, courses, job listings, podcast feeds), extend it — do not re-declare that CPT or emit a second, conflicting schema block.

═══════════════════════════════════════════════════════════════
PERFORMANCE
═══════════════════════════════════════════════════════════════
- LCP < 1.5s, portfolio sites need to feel snappy
- WP Rocket + Critical CSS + lazy loading
- ShortPixel WebP at 3 sizes per image
- Self-host Google Fonts
- Bricks output is light by default, keep it that way (audit unused
 modules)

═══════════════════════════════════════════════════════════════
ANTI-PATTERNS TO AVOID
═══════════════════════════════════════════════════════════════
- No "I'm passionate about design" filler, show, don't tell
- No emojis anywhere
- No fake stock photos of "designers at desks"
- No script/handwritten fonts
- No animated cursor effects or floating particles
- No real client logos without permission, use typeset names if
 unsure
- No "as featured in Forbes!" without proof
- No bouncing scroll-cue arrows
- No "Hire me" hero CTA without inquiry context, be specific about
 what you do

═══════════════════════════════════════════════════════════════
DELIVERABLE
═══════════════════════════════════════════════════════════════
1. Site map
2. WP-CLI install commands
3. Project CPT register PHP + ACF JSON
4. theme.json (if block theme) OR Bricks templates
5. Block markup or Bricks template for homepage
6. Project detail template
7. Services page block markup
8. Inquiry form schema + routing
9. Performance audit checklist
10. Launch checklist (15 items)

This prompt gives ChatGPT or Claude a full WordPress build plan for a designer or developer portfolio — a site built to win client work, with real case studies that show the problem, the process, and the measurable result, plus a project inquiry form that qualifies leads. It specifies a case-study post type, a filterable work gallery, a services page, and an inquiry form with budget and timeline fields as Gutenberg block markup. You get a plan for a portfolio that books projects, not a gallery of pretty thumbnails.

What does the portfolio website prompt build?

The plan covers a homepage featuring your best work, individual case-study pages with a challenge, approach, and results structure, a filterable project gallery, a services page with clear positioning, and an about page. It specifies a project inquiry form with budget and timeline fields, client testimonials, and a blog for thought leadership. CreativeWork and Person structured data is built in so your projects and your professional identity are legible to search engines and to the AI answer engines that summarize who you are. If you would rather ship faster, our WordPress build service delivers this architecture for a flat fee.

Who is this portfolio prompt for?

It is written for freelance web designers and developers, UX and product designers, photographers and art directors, and small studios that pitch for project work. It assumes you want to attract clients, not just archive past jobs.

What’s inside the prompt?

  • A business details block for your discipline, ideal client, services, and positioning
  • A plugin stack: a block theme, ACF Pro for structured case studies, and a forms plugin for inquiries
  • A data model with a case-study post type and project-type and industry taxonomies
  • Gutenberg block markup for the homepage, case-study template, services page, and gallery
  • A project inquiry form with budget and timeline fields, plus a testimonials section
  • CreativeWork and Person structured data, Open Graph cards, and a keyword plan around your services
  • Core Web Vitals targets for image-rich work pages and a launch checklist

Frequently asked questions

How are the case studies structured?

Each case study uses a challenge, approach, and results layout backed by an ACF field group, so every project reads the same way and always ends on an outcome. That structure is what separates a portfolio that wins work from a grid of screenshots, and it is the core of the spec.

Does the inquiry form qualify leads before they reach me?

Yes. The project inquiry form includes budget-range and timeline fields alongside the project description, so you can triage serious inquiries from tire-kickers before you spend time replying. The fields are yours to edit if you would rather ask about scope or referral source.

Can I filter my work by project type or industry?

The project gallery is filterable by project type and industry using the taxonomies in the data model, so a prospect looking for, say, e-commerce work can see only that. It helps visitors self-select and signals the range you actually cover.

Will search engines and AI tools understand who I am?

The SEO section adds Person structured data tying the site to you — your name, role, and profiles — and CreativeWork data on each project. That is what lets search engines and AI answer engines describe your work accurately when someone looks you up by name.

Which AI tools work with this prompt?

ChatGPT and Claude both return the full build. If you are a developer weighing whether to hand-code the portfolio or run it on WordPress, what a WordPress build costs and our library of free AI website prompts lay out both paths.

How to actually run this.

01

Copy the whole thing

All of it. Do not trim it down, every line is in there for a reason.

02

Swap in your details

Find the BUSINESS DETAILS part and drop in the real business. Name, what they do, all of it.

03

Paste and wait

Drop it into Claude for the first pass, or v0 if it is a landing page. Give it a minute.

04

Clean it up

Tweak the boring 10 percent. Spacing, mobile, that one cringe line. Ship it.

What’s next: from generated code to a website that works

The prompt did the hard 90 percent. What’s left is the boring 10 percent that turns a folder of code into a site people can actually find and trust. Here’s the whole checklist, in order.

1. Buy a domain

Grab your name at a registrar like Namecheap, Cloudflare, or Porkbun — about $10 to $15 a year for a .com. Skip the ten-year prepay and the upsells; you just need the domain and, ideally, the free WHOIS privacy most registrars now include.

2. Put it online

If the AI built you a static site (HTML, CSS, and JavaScript), you can host it for free: drag the folder into Netlify or Vercel, or connect a GitHub repo, then point your domain at it. If it built a WordPress theme, you need WordPress hosting — pick a managed host, install WordPress, upload the theme, and connect the domain. Either way, turn on HTTPS; it’s free and automatic on every modern host.

3. Wire up the parts AI skips

Generated sites almost always ship with a contact form that goes nowhere and a fake “success” message. Connect it to a real endpoint (Formspree, Web3Forms, or a plain mailto link) so leads actually reach you. While you’re in there: add a favicon, swap the placeholder images for your own compressed photos, and open the site on your phone to catch whatever breaks on a small screen.

4. Do the basic SEO and AI-search setup

This is what gets you found on Google and cited by ChatGPT, Perplexity, and AI Overviews. The essentials: a unique title tag and meta description on every page, one clear topic per page, an XML sitemap submitted to Google Search Console, basic structured data (Organization and FAQ schema), and an llms.txt file so AI crawlers can read you. If that reads like a foreign language, our SEO optimization service does it as a flat-fee pass, and our free SEO checklist walks the DIY route step by step.

5. Make it fast

AI builders love shipping four-megabyte images and render-blocking scripts. Compress your images, lazy-load anything below the fold, and run the page through PageSpeed Insights until Core Web Vitals turn green — speed lifts both rankings and conversions, so it’s the rare fix that pays twice. Our speed optimization service handles it if you’d rather not.

6. Get found locally, and measure it

Add analytics (GA4, or a lighter option like Plausible) so you can see what’s working instead of guessing. If you serve a local area, set up a Google Business Profile and use the exact same business name, address, and phone number everywhere — that consistency is what lands you in the map pack and in local AI answers.

7. Keep it alive

A website isn’t set-and-forget, especially on WordPress. Budget for backups, security, and updates so a routine plugin update doesn’t take the site down six months from now. Our care plans cover all of it from $290 a month, or you can do it yourself — you own all the code either way.

When it’s worth handing off

If any of these steps stall you — and hosting, DNS, and SEO stall a lot of people — that’s exactly what we’re for. We build the whole thing at a flat fee, ship it live, and hand you the code on GitHub, having read every line the AI wrote. Or take the free prompts and run with it yourself. Both outcomes are genuinely fine with us.

More from the stash.

You read. We build.

No free weekend? We will build it for you.

This is the exact prompt we would use. Flat fee, real deadline, code is yours.

Have us build this one Fixed fee · Fixed timeline