Use the Prompt
Add Your Brief
Add your context below. It will be included with the prompt when you copy or download.
Create an interactive frontend prototype using the existing project stack and explicitly labeled demo data for [PROJECT] and [AUDIENCE]. The task is: Learning Progress Dashboard.
Required content and structure
Present modules, completed lessons, upcoming tasks and resume points.
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 white, ink text and restrained mint selected states; generous spacing and simple controls. Keep type, spacing and color roles consistent. Prioritize the task over decorative elements and avoid a generic collection of unrelated cards.
Content preparation
Supply the course structure, lesson states, completion rules and the user's resume point. Clarify whether completion requires viewing, practice or assessment.
Layout and behavior
Show the next useful learning action before aggregate progress. Keep viewed lessons distinct from completed assessments and explain blocked modules through their prerequisites.
Task-specific acceptance check
- Distinguish viewed material from assessed completion.
- Test a new learner, a partially completed lesson and a failed assessment.
- A percentage should follow the declared completion rule rather than simply counting visited screens.
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 Learning Progress Dashboard. 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 modules, completed lessons, upcoming tasks and resume points. Use the following task-specific layout guidance when translating the image into editable elements: Show the next useful learning action before aggregate progress. Keep viewed lessons distinct from completed assessments and explain blocked modules through their prerequisites.
Visual direction from the example brief
warm white, ink text and restrained mint selected states; generous spacing and simple controls.
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: Present modules, completed lessons, upcoming tasks and resume points. Distinguish viewed material from assessed completion. 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 Learning Progress Dashboard Design Prompt
Use this learning progress dashboard design prompt to present modules, completed lessons, upcoming tasks and resume points.
The reference is an AI-generated concept. The instructions below describe what to build and test; the image does not demonstrate working behavior.
Define What Counts as Complete
A learning dashboard should distinguish opening a lesson from completing its requirements.
The resume point should help someone continue the actual unfinished task. Show the next useful learning action before aggregate progress. Keep viewed lessons distinct from completed assessments and explain blocked modules through their prerequisites.
From the Prompt
Show the next useful learning action before aggregate progress.
Make It Your Own
Show [MODULES] with viewed, in-progress and assessed-complete states. Link Resume to [LAST_UNFINISHED_ACTIVITY] and explain the supplied completion rule beside progress.
Prepare the Learning Progress Dashboard Content
The module cards pair course names with lesson counts and progress bars. Define completion criteria instead of equating opening a lesson with demonstrating understanding.
Supply the course structure, lesson states, completion rules and the user's resume point. Clarify whether completion requires viewing, practice or assessment.
From the Prompt
Present modules, completed lessons, upcoming tasks and resume points.
Make It Your Own
For [PROJECT], use [APPROVED_CONTENT] as the source for this learning progress dashboard. Supply the course structure, lesson states, completion rules and the user's resume point. Clarify whether completion requires viewing, practice or assessment. Identify missing inputs before replacing them with demonstration content.
Check a Viewed Lesson
The completed-lesson table differentiates Assessed and Viewed states. Keep that distinction consistent in the overall progress summary and resume behavior.
Open a lesson without finishing its assessment. Progress should reflect that distinction, and the next visit should return to the unfinished activity rather than the course homepage. Test a new learner, a partially completed lesson and a failed assessment. A percentage should follow the declared completion rule rather than simply counting visited screens.
From the Prompt
Distinguish viewed material from assessed completion.
Make It Your Own
Review the learning progress dashboard against this requirement: Distinguish viewed material from assessed completion. Test a new learner, a partially completed lesson and a failed assessment. A percentage should follow the declared completion rule rather than simply counting visited screens. Preserve approved content and revise only the parts that fail this check.
Review Your Learning Progress Dashboard Result
A convincing screen is not a working backend. Test validation, permissions, persistence and failure behavior separately before connecting real data.
- Test a new learner, a partially completed lesson and a failed assessment. A percentage should follow the declared completion rule rather than simply counting visited screens.
Follow-Up Prompt
Use this after the first result. It narrows the revision to the most important part of this task.
Refine the current learning progress dashboard. Test a new learner, a partially completed lesson and a failed assessment. A percentage should follow the declared completion rule rather than simply counting visited screens. Preserve the approved content and visual direction; change only the parts needed to resolve these issues.
