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: Feature Detail Page.
Required content and structure
Explain one capability through a task, required inputs, result and limitations.
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: paper white, deep navy and quiet pale-blue panels; precise grid and spacious typography. Keep type, spacing and color roles consistent. Prioritize the task over decorative elements and avoid a generic collection of unrelated cards.
Content preparation
Select one user task, its required inputs, the supported result and any prerequisites. Gather a real workflow example that demonstrates the capability being described.
Layout and behavior
Build the page around input, action and result. Keep boundaries next to the relevant step, with a clear next action for someone whose task fits the feature.
Task-specific acceptance check
- Avoid implying the feature replaces unrelated product capabilities.
- Check each statement against the supplied capability description.
- Remove claims that silently extend the feature to unrelated tasks, unsupported formats or unavailable integrations.
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 Feature Detail Page. 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: Explain one capability through a task, required inputs, result and limitations. Use the following task-specific layout guidance when translating the image into editable elements: Build the page around input, action and result. Keep boundaries next to the relevant step, with a clear next action for someone whose task fits the feature.
Visual direction from the example brief
paper white, deep navy and quiet pale-blue panels; precise grid and spacious typography.
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: Explain one capability through a task, required inputs, result and limitations. Avoid implying the feature replaces unrelated product capabilities. 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 Feature Detail Page Design Prompt
Use this feature detail page design prompt to explain one capability through a task, required inputs, result and limitations.
The reference is an AI-generated concept. The instructions below describe what to build and test; the image does not demonstrate working behavior.
Explain One Capability Through Input and Result
A feature page should make a bounded product promise understandable.
Without required inputs and limitations, a polished result image can imply capabilities the product does not support. Build the page around input, action and result. Keep boundaries next to the relevant step, with a clear next action for someone whose task fits the feature.
From the Prompt
Build the page around input, action and result.
Make It Your Own
Describe [USER_TASK], [REQUIRED_INPUTS] and [EXPECTED_RESULT] in sequence. Pair the result with its constraints and provide the next action relevant to that specific capability.
Prepare the Feature Detail Page Content
The lower strip connects the task to required inputs and the expected result. Explain the feature through this concrete sequence instead of relying solely on the hero slogan.
Select one user task, its required inputs, the supported result and any prerequisites. Gather a real workflow example that demonstrates the capability being described.
From the Prompt
Explain one capability through a task, required inputs, result and limitations.
Make It Your Own
For [PROJECT], use [APPROVED_CONTENT] as the source for this feature detail page. Select one user task, its required inputs, the supported result and any prerequisites. Gather a real workflow example that demonstrates the capability being described. Identify missing inputs before replacing them with demonstration content.
Test the Boundary Case
A distinct limitations column qualifies suggested timing and the role of user-provided detail. Keep these conditions visible and test that the product behavior matches them.
Choose an unsupported input from the documented limitations. The page should help the visitor recognize that boundary before they attempt the workflow. Check each statement against the supplied capability description. Remove claims that silently extend the feature to unrelated tasks, unsupported formats or unavailable integrations.
From the Prompt
Avoid implying the feature replaces unrelated product capabilities.
Make It Your Own
Review the feature detail page against this requirement: Avoid implying the feature replaces unrelated product capabilities. Check each statement against the supplied capability description. Remove claims that silently extend the feature to unrelated tasks, unsupported formats or unavailable integrations. Preserve approved content and revise only the parts that fail this check.
Review Your Feature Detail Page Result
Generated copy, routes and visual structure require review. Do not connect real forms, payments or external services without implementing and testing those flows.
- Check each statement against the supplied capability description. Remove claims that silently extend the feature to unrelated tasks, unsupported formats or unavailable integrations.
Follow-Up Prompt
Use this after the first result. It narrows the revision to the most important part of this task.
Refine the current feature detail page. Check each statement against the supplied capability description. Remove claims that silently extend the feature to unrelated tasks, unsupported formats or unavailable integrations. Preserve the approved content and visual direction; change only the parts needed to resolve these issues.
