Turn website feedback into a useful editing prompt.
A useful website improvement prompt names the page, describes an observed issue, states the intended outcome, and explains what must keep working. Ask for a focused change and a concrete verification step. SlopFix can generate a starting prompt from the findings in your website report.
Start with evidence from the actual page
“Make this website look better” leaves the assistant to invent a direction. Give it the exact section, current copy, or repeated pattern you want to fix. Include the audience and the action the visitor needs to complete. A screenshot helps with visual context; code access is needed to implement the change.
After a SlopFix scan, use the report’s copy action for either the combined improvement prompt or an individual fix. Those prompts are based on the report’s findings. Review them before using them; a matched pattern is a suggestion to investigate.
A prompt for a focused design review
Review this page for [audience] trying to [task].
Identify the three most consequential clarity or visual-hierarchy issues.
For each issue, quote the relevant copy or identify the exact section.
Explain how it affects the task and propose a specific correction.
Preserve working interactions and product facts.
Do not invent testimonials, user counts, or performance claims.
Give me the findings before editing the code.A prompt to fix a vague headline
On [page], the current headline is [exact headline].
The product takes [input] and provides [real output] for [audience].
Write three concise headline and supporting-copy options using those facts.
Keep the primary action [label] and preserve its behavior.
After I choose, implement the copy and check the mobile line breaks.A prompt to improve layout and hierarchy
In [section], [observed repeated layout or competing element] makes
[important information or action] hard to find.
Propose a layout that reflects the relationship between these items.
Reuse the existing type, spacing, and color tokens where they fit.
Keep all content, links, accessible labels, and functional states.
Verify at desktop and narrow mobile widths, including keyboard focus.
Explain the changes and any unresolved issues.A prompt for removing generic visual defaults
Use these observed findings from my website review:
[paste confirmed findings and suggested fixes]
For each finding, decide whether it conflicts with the product’s purpose.
Keep intentional choices and explain why they work.
Implement the highest-impact confirmed change first.
Avoid adding decorative effects or rewriting unrelated sections.
Check the primary user journey after the edit.Using the prompts with your existing tools
In Cursor, Claude Code, or Codex, provide the relevant project and page files. In Lovable, Bolt, or v0, paste the brief into the project conversation and inspect its proposed changes. These are suggested workflows with independent tools; SlopFix does not claim a native integration with them.
If the assistant cannot inspect a published page, provide a screenshot and the relevant source. If it lacks the code, ask it for a review instead of pretending it can apply the fix. Keep a recoverable version before a broad visual change.
Verify the result
Compare the revised page against the original issue. Can someone understand the offer or find the action more easily? Do forms, navigation, mobile layouts, and keyboard use still work? Use the UI and UX checklist for verification beyond appearance.
Read how to remove AI slop for the reasoning behind the edits, or explore the clearly labeled example report to see the prompt feature.
Get website design feedback ↗
BAGS