Use the Prompt
Add Your Brief
Add your context below. It will be included with the prompt when you copy or download.
Create a responsive HTML website using the existing project stack for [PROJECT] and [AUDIENCE]. The task is: Design Agency Services.
Required content and structure
Connect each service to a client problem, deliverables, process and relevant work.
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
List the client problems the agency handles, actual deliverables, process stages and relevant project examples. Choose a clear inquiry route for each service or one shared intake.
Layout and behavior
Explain each service through a concrete engagement rather than a string of broad capabilities. Use related work to demonstrate the type of output, with honest role and scope descriptions.
Task-specific acceptance check
- Use specific capabilities rather than generic unverified success claims.
- Ask whether a prospective client can tell what they would receive.
- Remove unsupported performance promises and check that case studies match the service they are used to illustrate.
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 Design Agency Services. 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: Connect each service to a client problem, deliverables, process and relevant work. Use the following task-specific layout guidance when translating the image into editable elements: Explain each service through a concrete engagement rather than a string of broad capabilities. Use related work to demonstrate the type of output, with honest role and scope descriptions.
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: Connect each service to a client problem, deliverables, process and relevant work. Use specific capabilities rather than generic unverified success claims. 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
- 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.
- Then test the narrow layout without squeezing desktop text into tiny labels.
- 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.
Download Prompt + Image
Includes the complete prompt and full-size reference image. Attach both in OpenDesign to guide the layout.
How to Write a Design Agency Services Design Prompt
Use this design agency services design prompt to connect each service to a client problem, deliverables, process and relevant work.
The reference is an AI-generated concept. The instructions below describe what to build and test; the image does not demonstrate working behavior.
Describe What the Client Receives
An agency services page needs more than broad discipline names.
A client should connect a problem to a concrete deliverable, understand the process and see relevant work. Explain each service through a concrete engagement rather than a string of broad capabilities. Use related work to demonstrate the type of output, with honest role and scope descriptions.
From the Prompt
Explain each service through a concrete engagement rather than a string of broad capabilities.
Make It Your Own
For each [SERVICE], specify [CLIENT_PROBLEM], [DELIVERABLES], [PROCESS] and a relevant case-study link. Separate included work from optional extensions and end with a scoped inquiry action.
Prepare the Design Agency Services Content
Each service card pairs a problem and deliverables with a short process. Prepare concrete scopes and exclusions rather than substituting broad capability slogans.
List the client problems the agency handles, actual deliverables, process stages and relevant project examples. Choose a clear inquiry route for each service or one shared intake.
From the Prompt
Connect each service to a client problem, deliverables, process and relevant work.
Make It Your Own
For [PROJECT], use [APPROVED_CONTENT] as the source for this design agency services. List the client problems the agency handles, actual deliverables, process stages and relevant project examples. Choose a clear inquiry route for each service or one shared intake. Identify missing inputs before replacing them with demonstration content.
Compare Two Adjacent Services
The work strip places project examples beneath the services. Check that each example supports the claimed service and links to a relevant case study.
Check whether their outcomes and boundaries are distinct. If the descriptions could be swapped without changing meaning, make the deliverables more specific. Ask whether a prospective client can tell what they would receive. Remove unsupported performance promises and check that case studies match the service they are used to illustrate.
From the Prompt
Use specific capabilities rather than generic unverified success claims.
Make It Your Own
Review the design agency services against this requirement: Use specific capabilities rather than generic unverified success claims. Ask whether a prospective client can tell what they would receive. Remove unsupported performance promises and check that case studies match the service they are used to illustrate. Preserve approved content and revise only the parts that fail this check.
Review Your Design Agency Services Result
Generated copy, routes and visual structure require review. Do not connect real forms, payments or external services without implementing and testing those flows.
- Ask whether a prospective client can tell what they would receive. Remove unsupported performance promises and check that case studies match the service they are used to illustrate.
Follow-Up Prompt
Use this after the first result. It narrows the revision to the most important part of this task.
Refine the current design agency services. Ask whether a prospective client can tell what they would receive. Remove unsupported performance promises and check that case studies match the service they are used to illustrate. Preserve the approved content and visual direction; change only the parts needed to resolve these issues.
