Creative Portfolio Design Prompts

Creative Studio Portfolio

Prompt preview

Present three projects with discipline, role, year and case-study links; use expressive type and an asymmetrical image grid.

View Prompt

Create a responsive HTML website using the existing project stack for [PROJECT] and [AUDIENCE]. The task is: Creative Studio Portfolio.

## Required content and structure

Present three projects with discipline, role, year and case-study links; use expressive type and an asymmetrical image grid.

Use [APPROVED_CONTENT] as the source of names, dates, figures, claims and destinations. List missing inputs before substituting anything. If a demonstration is needed, label its content as fictional. Do not invent customer quotes, rankings, partner logos or product capabilities.

## Design direction

Use [BRAND_RULES] and the design system already selected in the project. If no system is supplied, start with this direction: warm ivory, charcoal typography and one restrained acid-green accent; generous spacing and an asymmetric grid. Keep type, spacing and color roles consistent. Prioritize the task over decorative elements and avoid a generic collection of unrelated cards.

## Project content

For each of the three projects, include its title, one-sentence brief, discipline, year, studio role, collaborator credits, lead image and case-study destination. Lead with the strongest project; use the other two to show range. End with the supplied contact route. Do not invent case-study narratives for missing destinations.

## Layout and behavior

Use asymmetry through image scale and placement, with consistent caption alignment. Keep project names and credits outside images. Preserve supplied image proportions unless a crop is approved. On mobile, stack the introduction, lead project, supporting projects and contact in that order.

## Task-specific acceptance check

- Check a long title, a portrait image and multiple collaborators.
- Make every project destination reachable by keyboard and keep all credits visible without hover.

## Implementation and review

Keep text editable. Use semantic structure, descriptive controls, visible keyboard focus and appropriate empty/error states. Check narrow and wide layouts. Respect reduced-motion preferences. Preserve any existing project framework and dependencies; do not silently replace the stack. Return the editable files and explain any incomplete behavior or unsupported inputs. Review this specific task before proposing extra features.

## Reference attachment and reconstruction goal

Attach reference.webp from this prompt’s download bundle alongside this prompt in OpenDesign. Build an editable result with a similar composition and hierarchy; do not embed the whole reference image as the finished interface. Preserve approved project content and brand rules if they conflict with fictional sample labels. If the image is missing or unreadable, ask for it instead of claiming visual fidelity.

## Reference composition and content

Use the attached reference.webp as the visual reference for Creative Studio Portfolio. Before building, identify the major regions from top to bottom, their relative widths and heights, alignment, spacing, typography hierarchy, surface colors, borders, imagery and repeated components. Preserve those relationships rather than substituting a generic template. Required task content: Present three projects with discipline, role, year and case-study links; use expressive type and an asymmetrical image grid. Use the following task-specific layout guidance when translating the image into editable elements: Give one project the lead position and use the other two to establish range. The asymmetry should come from image scale and placement, while captions share a consistent alignment and type size. Keep the project name, discipline and credit outside the image so they remain readable over both light and dark photography. On a narrow screen, return to a deliberate vertical sequence: introduction, lead project, supporting projects, then contact. Keep the original image proportions unless you have approved a crop.

## Visual direction from the example brief

warm ivory canvas, oversized charcoal Swiss sans-serif typography, acid-green small accents, generous negative space, asymmetrical project grid with architectural sculptural photographs and a restrained cobalt panel. Exact hero text 'Good ideas. Carefully made.' Navigation 'Work', 'About', 'Contact'. Project captions 'Objects / 2026', 'Spaces / 2026', 'Identity / 2026'. Elegant professional editorial art direction.

## Interaction specification

The reference is a static concept: the behavior below is a requirement to implement, not proof that the picture already works. Copy the customized prompt into the project where you want to build the portfolio. Ask for the homepage first; case-study pages should use their own supplied content rather than invented project narratives. Make every project destination reachable by keyboard and keep all credits visible without hover. For each visible control, specify its trigger, affected state and feedback; implement local changes with consistent state across related views. Give search and filters real results, selection controls an explicit active state, and save actions visible pending/success/failure feedback where relevant. Do not add unrelated workflows. Use proper links for navigation, buttons for actions and accessible names for icon controls. Do not imply a backend operation succeeded when only a local demo changed.

## Visual comparison and delivery

1. Compare the result with the attached image at matching proportions. Review major region placement, relative image sizes, line breaks, spacing, typography hierarchy, contrast, active states and content density before polishing decorative details.
2. Then test the narrow layout without squeezing desktop text into tiny labels.
3. Keep logos, photos and icons as separate assets and all meaningful labels editable. List any unavailable fonts/assets and any intentional departures. Return the working files plus a concise account of implemented behavior and remaining integrations; do not promise a pixel-identical result from the prompt alone.

Portfolio Case Study

WebsitesOrganic

Prompt preview

Show role, constraints, process, alternatives, outcome and lessons with annotated visuals.

View Prompt

Create a responsive HTML website using the existing project stack for [PROJECT] and [AUDIENCE]. The task is: Portfolio Case Study.

## Required content and structure

Show role, constraints, process, alternatives, outcome and lessons with annotated visuals.

Use [APPROVED_CONTENT] as the source of names, dates, figures, claims and destinations. List missing inputs before substituting anything. If a demonstration is needed, label its content as fictional. Do not invent customer quotes, rankings, partner logos or product capabilities.

## Design direction

Use [BRAND_RULES] and the design system already selected in the project. If no system is supplied, start with this direction: warm cream, muted olive and terracotta; tactile materials and a calm editorial rhythm. Keep type, spacing and color roles consistent. Prioritize the task over decorative elements and avoid a generic collection of unrelated cards.

## Content preparation

Prepare your role, team credits, brief, constraints, alternatives, process artifacts and evidence of outcomes. Separate shipped work from concepts and proposed changes.

## Layout and behavior

Tell the story through decisions, showing the problem each visual addresses. Use annotations to explain meaningful changes rather than making the reader infer process from a gallery.

## Task-specific acceptance check

- Do not imply sole ownership of collaborative work.
- Check whether the reader can identify your contribution and why the final direction was chosen.
- Keep team work credited and distinguish observed outcomes from expected benefits.

## Implementation and review

Keep text editable. Use semantic structure, descriptive controls, visible keyboard focus and appropriate empty/error states. Check narrow and wide layouts. Respect reduced-motion preferences. Preserve any existing project framework and dependencies; do not silently replace the stack. Return the editable files and explain any incomplete behavior or unsupported inputs. Review this specific task before proposing extra features.

## Reference attachment and reconstruction goal

Attach reference.webp from this prompt’s download bundle alongside this prompt in OpenDesign. Build an editable result with a similar composition and hierarchy; do not embed the whole reference image as the finished interface. Preserve approved project content and brand rules if they conflict with fictional sample labels. If the image is missing or unreadable, ask for it instead of claiming visual fidelity.

## Reference composition and content

Use the attached reference.webp as the visual reference for Portfolio Case Study. Before building, identify the major regions from top to bottom, their relative widths and heights, alignment, spacing, typography hierarchy, surface colors, borders, imagery and repeated components. Preserve those relationships rather than substituting a generic template. Required task content: Show role, constraints, process, alternatives, outcome and lessons with annotated visuals. Use the following task-specific layout guidance when translating the image into editable elements: Tell the story through decisions, showing the problem each visual addresses. Use annotations to explain meaningful changes rather than making the reader infer process from a gallery.

## Visual direction from the example brief

warm cream, muted olive and terracotta; tactile materials and a calm editorial rhythm.

## Interaction specification

The reference is a static concept: the behavior below is a requirement to implement, not proof that the picture already works. Copy the customized prompt into your working project. Start with the core task: Show role, constraints, process, alternatives, outcome and lessons with annotated visuals. Do not imply sole ownership of collaborative work. For each visible control, specify its trigger, affected state and feedback; implement local changes with consistent state across related views. Give search and filters real results, selection controls an explicit active state, and save actions visible pending/success/failure feedback where relevant. Do not add unrelated workflows. Use proper links for navigation, buttons for actions and accessible names for icon controls. Do not imply a backend operation succeeded when only a local demo changed.

## Visual comparison and delivery

1. Compare the result with the attached image at matching proportions. Review major region placement, relative image sizes, line breaks, spacing, typography hierarchy, contrast, active states and content density before polishing decorative details.
2. Then test the narrow layout without squeezing desktop text into tiny labels.
3. Keep logos, photos and icons as separate assets and all meaningful labels editable. List any unavailable fonts/assets and any intentional departures. Return the working files plus a concise account of implemented behavior and remaining integrations; do not promise a pixel-identical result from the prompt alone.

Portfolio Presentation

SlidesEditorial

Prompt preview

Introduce the designer, select projects, explain roles and connect decisions to outcomes.

View Prompt

Create an editable HTML presentation with a 16:9 canvas, previous/next buttons, arrow-key navigation, a slide counter and a one-slide-per-page print layout for [PROJECT] and [AUDIENCE]. The task is: Portfolio Presentation.

## Required content and structure

Introduce the designer, select projects, explain roles and connect decisions to outcomes.

Use [APPROVED_CONTENT] as the source of names, dates, figures, claims and destinations. List missing inputs before substituting anything. If a demonstration is needed, label its content as fictional. Do not invent customer quotes, rankings, partner logos or product capabilities.

## Design direction

Use [BRAND_RULES] and the design system already selected in the project. If no system is supplied, start with this direction: ivory, charcoal and a single lime accent; oversized headlines, deliberate whitespace and clear information hierarchy. Keep type, spacing and color roles consistent. Prioritize the task over decorative elements and avoid a generic collection of unrelated cards.

## Content preparation

Choose projects that demonstrate the work relevant to the audience. Prepare your role, collaborators, constraints, decisions, artifacts and evidence of outcomes for each one.

## Layout and behavior

Give each project a short story rather than equal-sized image galleries. Use a consistent sequence for context, contribution and result while letting the work's strongest evidence lead.

## Task-specific acceptance check

- Preserve collaborators' credit and distinguish shipped work from concepts.
- Check that project credits remain visible and that shipped work is distinguishable from concepts.
- Remove claims of sole authorship where the result depended on a team.

## Implementation and review

Keep text editable. Use semantic structure, descriptive controls, visible keyboard focus and appropriate empty/error states. Check narrow and wide layouts. Respect reduced-motion preferences. Preserve any existing project framework and dependencies; do not silently replace the stack. Return the editable files and explain any incomplete behavior or unsupported inputs. Review this specific task before proposing extra features.

Keep one main idea per slide. Use charts only when actual comparable values are supplied; include units, source dates and limitations. Keep speaker notes separate from visible slide content.

## Reference attachment and reconstruction goal

Attach reference.webp from this prompt’s download bundle alongside this prompt in OpenDesign. Build an editable result with a similar composition and hierarchy; do not embed the whole reference image as the finished interface. Preserve approved project content and brand rules if they conflict with fictional sample labels. If the image is missing or unreadable, ask for it instead of claiming visual fidelity.

## Reference composition and content

Use the attached reference.webp as the visual reference for Portfolio Presentation. Before building, identify the major regions from top to bottom, their relative widths and heights, alignment, spacing, typography hierarchy, surface colors, borders, imagery and repeated components. Preserve those relationships rather than substituting a generic template. Required task content: Introduce the designer, select projects, explain roles and connect decisions to outcomes. Use the following task-specific layout guidance when translating the image into editable elements: Give each project a short story rather than equal-sized image galleries. Use a consistent sequence for context, contribution and result while letting the work's strongest evidence lead.

## Visual direction from the example brief

ivory, charcoal and a single lime accent; oversized headlines, deliberate whitespace and clear information hierarchy.

## Slide structure and presentation behavior

Recreate the slide composition as editable title, body, visual and annotation elements. A pictured slide is one view, not evidence of a complete deck. Use the supplied narrative to build any requested additional slides; preserve its typography, margins, color roles and alignment. Give each project a short story rather than equal-sized image galleries. Use a consistent sequence for context, contribution and result while letting the work's strongest evidence lead. Keep navigation outside exported slide content. Preserve collaborators' credit and distinguish shipped work from concepts.

## Visual comparison and delivery

1. Compare the result with the attached image at matching proportions. Review major region placement, relative image sizes, line breaks, spacing, typography hierarchy, contrast, active states and content density before polishing decorative details.
2. Then test the narrow layout without squeezing desktop text into tiny labels.
3. Keep logos, photos and icons as separate assets and all meaningful labels editable. List any unavailable fonts/assets and any intentional departures. Return the working files plus a concise account of implemented behavior and remaining integrations; do not promise a pixel-identical result from the prompt alone.

## Adapt the reference to the slide canvas

The attached reference image uses a 3:2 composition. Recompose its editable text, shapes and separate image assets onto the requested 16:9 slide canvas. Preserve hierarchy and readable spacing by adjusting the layout; do not stretch the reference or crop essential content to force it into 16:9. Treat this single concept as a visual direction, not as a completed multi-slide deck.

Stacking Project Cards

WebsitesMotion

Prompt preview

Let project cards overlap progressively while preserving captions and case-study links.

View Prompt

Create an HTML/CSS/JavaScript interaction study with explicit start, active and completed states and a readable prefers-reduced-motion fallback for [PROJECT] and [AUDIENCE]. The task is: Stacking Project Cards.

## Required content and structure

Let project cards overlap progressively while preserving captions and case-study links.

Use [APPROVED_CONTENT] as the source of names, dates, figures, claims and destinations. List missing inputs before substituting anything. If a demonstration is needed, label its content as fictional. Do not invent customer quotes, rankings, partner logos or product capabilities.

## Design direction

Use [BRAND_RULES] and the design system already selected in the project. If no system is supplied, start with this direction: white, charcoal and vivid green highlights; clearly labeled start, transition and end states. Keep type, spacing and color roles consistent. Prioritize the task over decorative elements and avoid a generic collection of unrelated cards.

## Content preparation

Prepare a short sequence of projects with images, captions and working destinations. Define the desktop overlap behavior and a normal document order.

## Layout and behavior

Use progressive overlap to emphasize the sequence without covering project identity or links. Keep a simple vertical list for mobile and reduced-motion settings.

## Task-specific acceptance check

- Provide a normal vertical list on mobile and with reduced motion.
- Scroll forward and back, then navigate by keyboard.
- Every project must remain reachable, and the last card should release naturally into the next section.

## Implementation and review

Keep text editable. Use semantic structure, descriptive controls, visible keyboard focus and appropriate empty/error states. Check narrow and wide layouts. Respect reduced-motion preferences. Preserve any existing project framework and dependencies; do not silently replace the stack. Return the editable files and explain any incomplete behavior or unsupported inputs. Review this specific task before proposing extra features.

Make the complete information and action available without animation. Provide pause or dismissal where relevant. Document triggers and transitions; do not replace actual progress with a decorative timer.

## Reference attachment and reconstruction goal

Attach reference.webp from this prompt’s download bundle alongside this prompt in OpenDesign. Build an editable result with a similar composition and hierarchy; do not embed the whole reference image as the finished interface. Preserve approved project content and brand rules if they conflict with fictional sample labels. If the image is missing or unreadable, ask for it instead of claiming visual fidelity.

## Reference composition and content

Use the attached reference.webp as the visual reference for Stacking Project Cards. Before building, identify the major regions from top to bottom, their relative widths and heights, alignment, spacing, typography hierarchy, surface colors, borders, imagery and repeated components. Preserve those relationships rather than substituting a generic template. Required task content: Let project cards overlap progressively while preserving captions and case-study links. Use the following task-specific layout guidance when translating the image into editable elements: Use progressive overlap to emphasize the sequence without covering project identity or links. Keep a simple vertical list for mobile and reduced-motion settings.

## Visual direction from the example brief

white, charcoal and vivid green highlights; clearly labeled start, transition and end states.

## Interaction specification

The reference is a static concept: the behavior below is a requirement to implement, not proof that the picture already works. Copy the customized prompt into your working project. Start with the core task: Let project cards overlap progressively while preserving captions and case-study links. Provide a normal vertical list on mobile and with reduced motion. For each visible control, specify its trigger, affected state and feedback; implement local changes with consistent state across related views. Give search and filters real results, selection controls an explicit active state, and save actions visible pending/success/failure feedback where relevant. Do not add unrelated workflows. Use proper links for navigation, buttons for actions and accessible names for icon controls. Do not imply a backend operation succeeded when only a local demo changed.

## Visual comparison and delivery

1. Compare the result with the attached image at matching proportions. Review major region placement, relative image sizes, line breaks, spacing, typography hierarchy, contrast, active states and content density before polishing decorative details.
2. Then test the narrow layout without squeezing desktop text into tiny labels.
3. Keep logos, photos and icons as separate assets and all meaningful labels editable. List any unavailable fonts/assets and any intentional departures. Return the working files plus a concise account of implemented behavior and remaining integrations; do not promise a pixel-identical result from the prompt alone.

Build a Creative Portfolio

A Suggested Sequence

Creative Studio Portfolio

Portfolio Case Study

Portfolio Presentation

Stacking Project Cards

No Prompts Match Yet.

Turn Your Prompt into a Design.