All prompts
Portfolio Editor’s pick

Distinctive developer portfolio

Create a portfolio that communicates engineering judgment through case studies rather than skill-logo wallpaper.

Build prompt

Copy as-is, then replace the variables

Build a distinctive developer portfolio for [NAME], a [SPECIALTY] developer seeking [GOAL].

The portfolio should feel like a thoughtful product, not a résumé pasted into cards. Lead with evidence of judgment and shipped work.

Content and structure:
- Hero: one precise positioning statement, current availability, and links to selected work and contact.
- Selected work: [NUMBER] case studies. Each must show the problem, constraints, key technical decision, personal contribution, measurable result, and one lesson learned.
- Experience: a compact timeline emphasizing scope and outcomes rather than job descriptions.
- Capabilities: organize technologies by what they enable; do not create a logo cloud.
- About: a short, specific personal note that supports the professional story.
- Contact: email, GitHub, [OTHER NETWORK], and a copy-email interaction.

Design direction:
- Inspiration: [DESIGN INSPIRATION], interpreted rather than copied.
- Typography: [TYPOGRAPHY DIRECTION].
- Color: [COLOR DIRECTION].
- Add one signature interaction that reinforces the developer’s specialty, while respecting reduced-motion preferences.
- Use project-specific visual placeholders with meaningful captions.

Implementation requirements:
- Fully responsive, semantic, keyboard accessible, and fast.
- Add useful metadata, social sharing metadata, and print-friendly résumé styling.
- Use realistic editable content objects for projects and experience.
- No fake testimonials, fake client logos, skill percentages, or generic claims such as “passionate developer.”

Expected outcome

A memorable, accessible portfolio focused on evidence, decisions, and project impact.

Why it works

  • Replaces generic skill claims with structured evidence and measurable outcomes.
  • Explicitly blocks common low-trust portfolio patterns such as fake testimonials.
  • Adds a single purposeful interaction instead of decorative motion everywhere.
Variables to customize
[NAME]Example: Maya Chen
[SPECIALTY]Example: frontend systems
[GOAL]Example: senior product engineering roles
[NUMBER]Example: 3
[OTHER NETWORK]Example: LinkedIn
[DESIGN INSPIRATION]Example: independent editorial magazine
[TYPOGRAPHY / COLOR DIRECTION]Example: expressive serif headlines; warm paper and cobalt

Method sources

Traceable, not copied blindly

This prompt is an original editorial adaptation. The references below informed its structure and review criteria; their text is not presented as our own.

Prompt Engineering Interactive Tutorial

Anthropic · 37k+ GitHub stars · Reference only

Used as methodology guidance for clarity, context separation, examples, and multi-step prompting. No tutorial content is reproduced.

prompts.chat

Community · 160k+ GitHub stars · Prompt data: CC0

Used to review common community prompt patterns and discoverability conventions.

v0 Text Prompting Guide

Vercel · Official product documentation · Reference only

Used for the component-first, specific, incremental workflow behind these build prompts.

Keep building

Launch

High-converting SaaS landing page

Turn a product idea into a focused landing page with clear hierarchy, credible proof, and a deliberate conversion path.

Open prompt

App

Product analytics dashboard

Generate an information-dense dashboard that still feels calm, legible, and useful on smaller screens.

Open prompt

App

Habit tracker with useful motivation

Build a habit tracker around reflection and recovery—not streak anxiety or decorative charts.

Open prompt