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.