I Asked AI to Fix My UI 20+ Times. The Problem Wasn't My Prompts.

May 26, 2026 · 2:30 PM UTC ·9 min read · 0 reactions · 0 comments · 33 views

TL;DR · WeSearch summary

The author explores the challenges of using AI for UI design feedback, revealing that the AI struggled to understand vague instructions. Despite attempts to provide specific prompts, the AI still produced inconsistent results due to a lack of defined design parameters. Ultimately, the author concludes that the issue lies not with the AI's capabilities but with the complexity of design decisions across different layers.

Key facts

▪The author experienced difficulties when asking AI for UI feedback, as it often misinterpreted vague instructions.
▪Specific prompts improved the AI's responses but highlighted issues with global design decisions not being consistently defined.
▪The author realized that the AI's inability to remember design context contributed to inconsistent styling across different pages.

About this source

DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.

All DEV.to (Top) coverage →

Original article

DEV.to (Top)

Read full at DEV.to (Top) →

Story provenance

Source · retrieval · rights · ranking — open for full record

inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisher	DEV.to (Top)
Canonical URL	https://dev.to/yuki-uix/i-asked-ai-to-fix-my-ui-20-times-the-problem-wasnt-my-prompts-527j
Publication time	Tue, 26 May 2026 14:30:06 +0000
Retrieval time	2026-05-26T14:37:49.954Z
Last seen	2026-05-26T14:37:49.954Z
Headline source	Publisher (no WeSearch rewrite)
Excerpt source	publisher body
Excerpt method	First ~120 words (~800 chars) of extracted publisher body, fair-use limited.
Summary	WeSearch · cerebras-chat (WeSearch summarizer)
Summary source text	contentText
Citation coverage	Summary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster	YAMlS5cKKAHS
Cluster logic	Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reason	Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visit	Yes — open original
Substitutes article?	No — link-out required for full text

Rights status (four layers)

Publisher-declared

No publisher-confirmed rights record for this source yet.

Machine-readable

No source-specific machine-readable restriction detected beyond the public feed.

WeSearch interpretation

WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.

Unknown

Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing	May the item be indexed (stored, ranked, made findable)?	Allowed
Snippet	May a short excerpt of the publisher's text be shown?	Allowed
AI summary	May WeSearch generate its own short summary of the article?	Limited
Retrieval / RAG	May the content be exposed for third-party retrieval-augmented generation?	Not asserted
Model training	May the content be used to train AI models?	Not asserted
Commercial reuse	May the content be reused commercially?	Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

Opening excerpt (first ~120 words) tap to expand

try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 2904651) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } yuki uix Posted on May 26 I Asked AI to Fix My UI 20+ Times. The Problem Wasn't My Prompts. #css #ai #webdev #designsystem The feature was done. Everything worked. I opened the browser, looked at the page, and thought: it's functional, but it's just... off. So I did what felt natural — I asked AI to help fix the styling. That's when things got weird. When I was building features, AI understood me perfectly. "Add a loading state to this button." Done.

…

Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).

Anonymous · no account needed

Discussion

0 comments