Biblioteca de prompts para designers

Act as a skeptical user who is resistant to technology and highly concerned about data privacy. Review my proposed feature list for a [Health App] below. List 5 distinct reasons why you would refuse to use these features, focusing on privacy concerns and usability friction. Be critical and direct.

I am designing a [Platform Name] for [Target Audience]. Based on the Jobs-To-Be-Done framework, generate 5 core 'Jobs' that these users are hiring my product to do. Format the output as - 'When I... (Situation), I want to... (Motivation), So that I can... (Expected Outcome).'

Role: Act as a senior UX researcher. Task: Generate a user interview script to uncover deep insights. Context: The script is for a new mobile banking app targeting millennials (25-35). The goal is to understand their current financial habits, frustrations with existing apps, and attitudes toward saving. Format: Structure the output with a friendly introduction, 5 warm-up questions, 10 deep-dive questions, and 3 wrap-up questions.

Role: You are a market research analyst specializing in user experience. Task: Perform a competitive analysis of Duolingo, Babbel, and Memrise. Context: Focus specifically on their user onboarding flow, core learning mechanics, and the clarity of their value proposition for new users. Format: Present the findings in a markdown table with columns for 'Competitor,' 'Onboarding Strength,' 'Learning Loop Weakness,' and 'Key Differentiator'.

Role: Act as a UX strategist. Task: Synthesize the provided research notes into a detailed user persona. Context: The notes are: 'Users are busy parents, they plan family meals weekly, struggle to find kid-friendly recipes, and value quick grocery list creation.' Format: Create a persona named 'The Weekly Planner' that includes a bio, 3 key goals, 3 major frustrations, and a short personal quote.

Create a persona for [target audience] with goals, frustrations, and preferred tools.

Summarize 5 user interviews about struggles with calendar apps. Focus on friction points.

Create a short survey to collect feedback on mobile app usability.

Design a customer feedback process for an online food delivery service.

Before proposing UI, audit the current source of truth.

Check:
1. Existing routes, components, tokens, design docs, and tests.
2. Similar screens or patterns already in the product.
3. Accessibility and interaction constraints.
4. Unknowns, stale assumptions, and places where screenshots are not enough.

Return:
- Evidence links or file paths.
- What can be reused.
- What must be changed.
- Risks if we skip verification.

Only after this audit, propose the design direction.

Role: You are a design lead preparing for a project kickoff. Task: Create a list of key questions for the stakeholder interview. Context: The project is a redesign of an e-commerce checkout process. We need to define business goals, success metrics (e.g., conversion rate, cart abandonment), known technical constraints, and market positioning. Format: Organize the questions into three sections: 'Business Goals,' 'Technical Constraints,' and 'User & Market'.

Map out the user journey for a [User] booking a [Service]. Break it down into stages - Awareness, Consideration, Booking, Consultation, and Post-Care. For each stage, identify the user's likely Sentiment - High/Neutral/Low and potential drop-off points.

Role: You are a design thinking facilitator. Task: Reframe a user problem into a set of optimistic, solution-oriented questions. Context: The core user problem is: 'Users get overwhelmed by the number of choices on the restaurant delivery app and often give up.' Format: Generate 5 unique 'How Might We' statements based on this problem.

Role: Act as an innovation consultant. Task: Generate a wide range of feature ideas. Context: The brainstorming is based on the 'How Might We' statement: 'HMW make tracking personal spending feel effortless and rewarding?' Format: Provide a list of 15 ideas, categorized under the headings 'Conventional Features,' 'Gamification Ideas,' and 'Forward-Thinking Concepts'.

I want to increase the sign-up rate on my SaaS landing page. Based on behavioral psychology principles, generate 3 distinct A/B testing hypotheses involving layout or copy changes. Format as - 'If we change [Variable], then [Result] will happen because [Rationale]'.

Role: You are a data-informed product designer. Task: Formulate hypotheses and suggest experiments based on post-launch data. Context: Analytics show a 50% user drop-off on our app's payment screen. User feedback suggests a lack of perceived security. Format: Propose two data-driven hypotheses for the drop-off and suggest a specific A/B test for each hypothesis to validate it.

Review this user flow - [User clicks 'Pay Now' -> Processing Spinner -> Success]. Identify 7 specific edge cases or failure states we need to design screens for (e.g., Insufficient funds, API timeout, 3DSecure verification required, Session timeout). Suggest a user-friendly recovery path for each.

Create a product strategy for launching a design system for a mental wellness platform.

Suggest 3 unique brand voice directions for a new electric bike company.

Create a hierarchical sitemap for my app tailored for small businesses. The structure should be 3 levels deep. Include sections for Dashboard, Contacts, Pipeline, and Settings. Output the result in a tree structure or bulleted list, highlighting the primary user flow.

Role: You are an Information Architect. Task: Create a logical, text-based sitemap. Context: The sitemap is for a new guided meditation app. It needs to be simple for new users but provide depth for experienced ones. Format: Use a nested bulleted list to show the hierarchy of the primary sections (Home, Discover, Library, Profile) and their key sub-pages.

Role: You are a UI designer describing a layout to a junior designer. Task: Describe the key components and layout for a wireframe. Context: The screen is the main 'recipe search results' page for a cooking app. It needs to display results clearly and provide easy-to-use filtering options. Format: Write a clear, descriptive paragraph detailing the header, filter bar (with specific filter examples), the grid layout for recipe cards, and the content on each card (image, name, cook time, rating).

Create a dashboard layout with filters, graphs, and tabs.

Design a 3-screen UI flow for [product] that [goal], keeping the style [adjective].

Prototype a smart home controller app with voice UI.

Link this flow for a standard checkout process.

A subscription-based coffee delivery landing page.

Design a SaaS analytics dashboard for marketing teams with sidebar navigation, KPI cards showing conversion rates and traffic, and a dark theme.

Create a fitness tracking mobile app with dark theme, workout logging, progress charts, and social sharing features for millennials.

Use clean sans-serif typography, ample whitespace, subtle shadows, and a minimal color palette with one accent color.

Design a B2B SaaS landing page with hero section, feature grid, testimonials, pricing table, and a prominent CTA. Style similar to Stripe.

Use deep navy (#1a1a3e) as the primary background with electric blue (#0066ff) accents and pure white (#ffffff) text. Secondary elements should use slate gray (#64748b).

Design a note-taking app that feels clean and minimal like Notion, with the playful touches of Duolingo. Include a sidebar, content area, and quick-add buttons.

Include hover states for buttons, loading skeleton for the data table, and an empty state for when no results are found. Show both collapsed and expanded sidebar states.

Design for mobile (iPhone 14 size) with proper safe areas, thumb-friendly button placement, and swipe gesture hints for card interactions.

Create a dark-mode dashboard for a renewable energy startup with a focus on real-time data visualization.

We are designing an interface for a Spatial Computing headset (like Vision Pro). Describe how a standard e-commerce 'Product Detail Page' should adapt to a 3D space. How does the user interact with the 'Add to Cart' button using eye-tracking and hand gestures? Describe the Z-axis depth layering.

Draft the documentation for a 'Modal' component in our design system. Include sections for - Usage Guidelines (When to use vs. when not to), Anatomy (Header, Body, Footer, Overlay), Behavior (transitions, dismissal logic), and Accessibility specs (focus trapping, aria-modal='true').

I am handing off a design for a 'Multi-Select Filter Bar'. Describe the logic required for the developer. Specifically, detail how the state should change when multiple filters are selected, how the 'Select All' toggle interacts with individual items, and how the URL parameters should update dynamically.

Generate 3 distinct color palettes for a Mental Health App. 1. Calming/Pastel. 2. Trust/Corporate. 3. Energetic/Gen Z. Provide Hex codes for the Background, Primary, and Secondary colors. Ensure all text combinations meet WCAG 2.2 AA contrast ratios.

Write a highly detailed text-to-image prompt for a UI design of a Music Streaming App. Include keywords for - Mobile Interface, Dark Mode, Spatial UI elements, Glassmorphism, 8k resolution, and high fidelity. The vibe should be immersive and futuristic.

<use_interesting_fonts>
Typography instantly signals quality. Avoid using boring, generic fonts.
Never use: Inter, Roboto, Open Sans, Lato, default system fonts.

Impact choices:
- Code aesthetic: JetBrains Mono, Fira Code, Space Grotesk
- Editorial: Playfair Display, Crimson Pro, Fraunces
- Startup: Clash Display, Satoshi, Cabinet Grotesk
- Technical: IBM Plex family, Source Sans 3
- Distinctive: Bricolage Grotesque, Obviously, Newsreader

Pairing principle: High contrast = interesting. Display + monospace, serif + geometric sans, variable font across weights. Use extremes: 100/200 weight vs 800/900, not 400 vs 600. Size jumps of 3x+, not 1.5x. Pick one distinctive font, use it decisively. Load from Google Fonts. State your choice before coding.
</use_interesting_fonts>

<always_use_solarpunk_theme>
Always design with Solarpunk aesthetic:
- Warm, optimistic color palettes (greens, golds, earth tones)
- Organic shapes mixed with technical elements
- Nature-inspired patterns and textures
- Bright, hopeful atmosphere
- Retro-futuristic typography
</always_use_solarpunk_theme>

Create a dashboard for renewable energy monitoring.

Design a split-screen hero section for a B2B SaaS tool. Left side: headline, subheadline, email input, primary CTA, and social proof logos. Right side: abstract dashboard mockup. Dark mode, Tailwind CSS, clean aesthetic with a primary purple accent (#8B5CF6).

Build a centered hero section for a consumer startup launch. Gradient mesh background (teal to blue), large typography, waitlist email input, and a subtle floating animation on a central product image. Use Framer Motion for the animation.

Create a full-bleed e-commerce hero section for a luxury watch brand. Large high-quality background image, minimalist white text, simple 'Shop the Collection' ghost button. Extremely clean typography using Playfair Display.

Design a 3x3 bento grid feature section for an AI app. Different sized cards (some spanning 2 cols/rows). Each card needs a subtle inner shadow, a gradient border on hover, a Lucide icon, and a short description. Use shadcn/ui cards.

Create a masonry layout testimonial section. 6 cards of varying heights. Each needs a user avatar, name, company role, 5-star rating, and the quote. Use a light gray background (#F8FAFC) for the section to separate it from the white main content.

Build a 3-tier pricing table (Starter, Pro, Enterprise). Highlight the Pro tier with a subtle glow and an 'most popular' badge. Include a toggle for monthly/annual billing. Use checkmarks for included features and grayed-out crosses for excluded ones.

Create a detailed feature comparison table for a SaaS product vs competitors. Sticky header row on scroll. Alternate row background colors for readability. Use tooltips to explain complex features.

Create a mega menu dropdown for 'Features'. 2-column layout inside the dropdown. Left column: 4 core features with icons. Right column: A featured case study card. Use Radix UI primitives for accessible keyboard navigation.

Create a drag-and-drop file upload zone. Dashed border that turns solid blue on drag-over. Include an upload icon and 'Drag & drop or click to browse' text. Below the zone, show a list of uploaded files with a progress bar and a remove button.

Create a responsive line chart component for MRR over 12 months. Use Recharts. The line should have a smooth curve (monotone), a gradient fill underneath, and custom tooltips showing the exact value and month on hover.

Create a toast notification component. Position bottom-right. Include variants for success (green check), error (red x), and info (blue i). Smooth slide-up enter animation and fade-out exit. Include a close button and an auto-dismiss progress bar.

Create a set of 3 feature cards. On hover, the card should slightly lift (-translate-y-1), the shadow should expand (shadow-lg), and the icon should rotate 12 degrees. Use smooth 300ms transitions.

Create a dark/light mode toggle switch. Use a sun icon that rotates and cross-fades into a moon icon when clicked. The background of the switch should change from gray-200 to slate-700. Provide the Tailwind config needed for this to work.

Build a login form with strict accessibility. Every input needs a visually hidden <label> if not explicitly shown. Inputs must have aria-invalid and aria-describedby linked to error messages when validation fails. Focus rings must be visible (ring-2 ring-blue-500) and never outline-none without replacement.

Create a mobile onboarding flow with 3-4 screens for a [type] app. Include illustrations, concise copy placeholders, progress indicators, and prominent CTAs. Use a [style] aesthetic with [color scheme] colors.

UI design of a [type of app/website] for [target audience], color scheme [x], style: [brutalist/minimal/realistic/3D/flat], layout inspiration from [Dribbble/Behance link or concept], shot in [isometric/top-view], clean background.

Design a mobile app UI layout for a personal finance tracker with a playful and clean design.

Design 5 icon concepts for a health & wellness app that feels organic and high-tech.

Build a mobile-first settings page with a sticky header, grouped cards, toggles, select menus, inline validation, and a destructive account section, using semantic HTML, accessible focus states, and a 12-column desktop grid.

Build a [component/screen] for [user goal].
Layout: [desktop layout], [mobile layout].
Components: [list exact components].
Style: [spacing, typography, radius, colors, density].
States: [default, hover, active, focus, loading, empty, error, disabled, selected].
Behavior: [sorting, filtering, validation, animation, dismiss, pagination].
Accessibility: semantic HTML, keyboard support, focus states, ARIA labels, contrast.
Constraints: [framework, libraries, tokens, no external deps, existing design system].

Set up a typography scale using tailwind with fluid typography (clamp) so font sizes scale down gracefully on mobile.

Default selected button shouldn't have a black background, fix that.

Create a SaaS pricing table with Material UI React components.

Verify this prototype before summarizing the result.

Run:
1. Typecheck, lint, and production build.
2. Desktop and mobile screenshots.
3. Keyboard navigation and visible focus.
4. Reduced motion check for animated interactions.
5. Loading, empty, error, disabled, hover, focus, and active states.
6. Accessibility basics: labels, landmarks, contrast, touch target size.
7. Claim check: remove or qualify anything that was not verified.

Return only verified facts, failing checks, screenshots or file paths, and the smallest next fix.

Draft the documentation for a 'Modal' component in our design system. Include sections for - Usage Guidelines (When to use vs. when not to), Anatomy (Header, Body, Footer, Overlay), Behavior (transitions, dismissal logic), and Accessibility specs (focus trapping, aria-modal='true').

I am handing off a design for a 'Multi-Select Filter Bar'. Describe the logic required for the developer. Specifically, detail how the state should change when multiple filters are selected, how the 'Select All' toggle interacts with individual items, and how the URL parameters should update dynamically.

{
  "instruction": "Extract user details from the text.",
  "input": "John Doe, aged 34, from New York.",
  "output_format": {
    "name": "string",
    "age": "number",
    "city": "string"
  }
}

Extract design tokens from the Figma file [URL]. Define them as CSS variables in a globals.css file.

Build a React component for the Project Card based on the Figma design. Ensure it uses the exact spacing, typography, and shadow tokens extracted in Phase 1.

I want clean, spacious design. 48px gaps between major sections. Use CSS Grid for the project cards. Hover effects should lift the card slightly with a soft shadow. Use Inter for typography. Keep it minimal.

Build me a black and purple dashboard about us page for a modern SaaS and put it in this Figma file [URL].

Update the dashboard cards based on the changes I made here [Figma URL].

Make a duplicate of the home mobile Figma frame. I'll give you the link so you can read it, then do some design explorations.

Call pwd; you can only read and write files in this directory. Review progress.txt, tests.json, and the git logs. Manually run through a fundamental integration test before moving on to implementing new features.

Add all shadcn components.

You are a design engineer. Read the provided Figma frame, screenshots, product context, and repository conventions before writing code.

Return a design intent brief with:
1. User job and business goal.
2. Layout structure by region.
3. Component inventory and expected states.
4. Token mapping for color, type, spacing, radius, elevation, and motion.
5. Interaction rules, keyboard behavior, focus order, loading, empty, and error states.
6. Open questions that would block implementation.

Do not implement yet. Do not infer a new visual system if existing tokens or components are available.

Audit whether this design system is ready for AI agents.

Inspect:
1. Token names: semantic names vs raw color or spacing names.
2. Component metadata: purpose, props, variants, states, constraints, accessibility.
3. Machine-readable contracts: JSON, code syntax, TypeScript types, Storybook, MDX, MCP output.
4. Human-readable rules: usage guidelines, anti-patterns, examples, AGENTS.md or skills.
5. Trust levels: what the agent may suggest, edit mechanically, or never change without review.

Return a severity-ranked report with quick fixes, medium fixes, and structural gaps.

Classify this task before acting.

Axes:
- Scope: open exploration or controlled adherence.
- Autonomy: agentic execution or manual/human-led execution.

Choose one mode:
1. Open + agentic: generate several directions and explain tradeoffs.
2. Agentic + controlled: create variations inside explicit constraints.
3. Manual + controlled: implement exactly what is specified.
4. Open + manual: help me think, but do not execute.

For the selected mode, write the prompt, constraints, verification steps, and what the human should review.

Split this design engineering task into specialized subagents:

1. design-deconstructor: extracts layout, hierarchy, components, tokens, motion, and interaction intent.
2. frontend-implementer: builds with existing components, code style, responsive rules, and tests.
3. a11y-reviewer: checks semantics, keyboard, focus, contrast, labels, and reduced motion.
4. evidence-verifier: validates claims against source files, screenshots, build output, and linked references.
5. copy-humanizer: rewrites public text in natural Portuguese, removing AI smell and unsupported claims.

For each subagent, define input, output, success criteria, and handoff format. Then define the final integration gate.

Role: [Quem a IA deve ser]
Task: [O que a IA deve fazer]
Context: [Informações de contexto do projeto/audiência]
Format: [Como a IA deve estruturar e formatar a saída final]

<instruction>Summarize the following article in three bullet points.</instruction>
<input>
[Insert article here]
</input>

<task>Evaluate the financial risk of the provided portfolio.</task>
<step1>Analyze asset diversification.</step1>
<step2>Calculate risk-to-reward ratio.</step2>
<output_requirements>Present findings as a brief report.</output_requirements>

<context>
[Insert retrieved document snippet here]
</context>
<question>What are the key policy changes mentioned?</question>
<instruction>Answer using only the provided context.</instruction>

<examples>
  <example>
    <input>I love this product!</input>
    <sentiment>Positive</sentiment>
  </example>
</examples>
<target_input>
[Insert new text here]
</target_input>

<output_format>
  <headline>[Insert Title]</headline>
  <summary>[Insert 2-sentence summary]</summary>
</output_format>

{
  "instruction": "Extract user details from the text.",
  "input": "John Doe, aged 34, from New York.",
  "output_format": {
    "name": "string",
    "age": "number",
    "city": "string"
  }
}

{
  "instruction": "Classify the sentiment of the following review.",
  "input": "The service was terrible and my food was cold.",
  "categories": ["Positive", "Neutral", "Negative"],
  "output": "JSON"
}

Please answer directly without any preamble or pleasantries.

Your response should be composed of smoothly flowing prose paragraphs. Write the prose sections of your response in <smoothly_flowing_prose_paragraphs> tags.

Outline the steps required to design a [404 page], considering UX best practices, and then describe the final layout.

Before answering, please think carefully about the problem in <thinking> tags. Then, provide your final answer in <answer> tags.

Always proactively implement your suggestions unless I explicitly tell you otherwise. Don't ask for permission to make changes.

Never make any changes or implement suggestions without first asking for my explicit permission and waiting for my approval.

You should execute as many tasks in parallel as possible. Do not wait for one task to finish before starting another unless there is a strict dependency.

Base your code only on the provided context and standard libraries. Do not hallucinate external dependencies or functions.

Your solution must be robust and generalizable. Do not hardcode values to pass specific tests.

Vou te apresentar [uma ideia / um plano / uma decisão]. Quero que você aja como um crítico bem-intencionado, alguém que me quer bem mas que vai ser honesto sobre o que pode dar errado.

[DESCREVA SUA IDEIA OU PLANO AQUI]

Agora me diz:

1. O que você acha que pode dar errado nesse plano?
2. Quais premissas eu estou fazendo que podem estar erradas?
3. Qual é o argumento mais forte contra essa decisão?

Não precisa ser diplomático. Prefiro encontrar os problemas agora do que depois.