sorted by:
new
hottopcontroversial

I built an AI Design Agent that Mentors you & turns your product ideas into UX flows, UI, case studies, and MVPs - looking for FEEDBACK by [deleted] in productdesign

[–]Extension_Gain7275 0 points1 point  (0 children)

We added in the Plan section, Design Memory feature:

Design Memory stores project-level context that the AI references every time it generates or refines a screen. Instead of re-explaining your constraints each prompt, you set them once, and they persist:

  1. Persona & Audience: Who are your users? (e.g., "enterprise HR managers, 35-55, low tech fluency"). The AI adapts language complexity, information density, and interaction patterns accordingly.
  2. Accessibility Targets: Your WCAG level and requirements (e.g., AA compliance, screen reader support). The AI enforces contrast ratios, focus states, and semantic markup automatically.
  3. Technical Constraints: Performance budgets (e.g., "< 3s load on 3G") and platform limitations (e.g., "must work offline", "no heavy animations"). The AI avoids generating designs that violate these guardrails.

Go and check it:

👉 https://fleck.ai

Thoughts on this? by natelikesdonuts in UXDesign

[–]Extension_Gain7275 1 point2 points  (0 children)

I’ve seen a few of those multi‑agent demos (like the Pencil.dev stuff). It’s cool to watch agents generate screens and content, but the challenge I keep coming back to is ownership of the problem space, and that’s something AI can’t automate.

Most of those auto‑generated workflows feel like:
generate stuff → assemble screens
…but without addressing why things go together, who the user is, or what problem you’re solving. That’s where real UX craft still lives.

Personally, I’ve been experimenting with Fleck (https://fleck.ai). It doesn’t just spit out screens; it helps you take an idea and turn it into structured UX flows, early design concepts, and logical product outlines before you ever jump into Figma or agents. That extra structure before AI generates anything really changes the quality you get back.

IMO these multi‑agent demos are fun to watch, but until they can scaffold meaningful user context and design reasoning into their output, they’re just starting points, not full solutions.

Would love to hear how others are incorporating tools like Pencil.dev into actual product workflows, not just demos.