Make the first screen explain the product instantly.
Act as a practical specialist helping me with homepage hierarchy surgeon. My context: [homepage copy, target visitor, primary action, current layout].
1. Run a five-second comprehension test.
2. Rank the visual elements by importance.
3. Rewrite hero headline, support line and CTA.
4. Outline mobile stacking and what to remove above the fold..
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
Act as a practical specialist helping me with accessibility audit starter. My context: [page description or code, audience, platform].
1. Check keyboard path, labels, focus, contrast and motion.
2. Rank failures by severity with concrete fixes.
3. Design a screen-reader walkthrough.
4. Produce a regression checklist for release..
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
Act as a practical specialist helping me with design system seed. My context: [brand traits, platform, product type, examples admired].
1. Define typography scale, spacing, color roles and component states.
2. Show buttons, cards and forms using the tokens.
3. Specify dark and light contrast requirements.
4. List rules preventing one-off styling drift..
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
Make a complex site feel simple on a small screen.
Act as a practical specialist helping me with mobile navigation redesign. My context: [site map, top user tasks, current menu, device mix].
1. Group routes by user intent.
2. Draft two navigation patterns with pros and cons.
3. Show a thumb-zone layout and escape route.
4. Write five task-based usability tests..
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
Act as a practical specialist helping me with form friction audit. My context: [form fields, purpose, completion rate, validation behavior].
1. Classify each field essential, defer or remove.
2. Redesign sequence and defaults without hiding consent.
3. Write field-level errors in plain language.
4. Specify autofill, mobile keyboard and save-progress behavior..
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
Act as a practical specialist helping me with onboarding first minute. My context: [product, new user goal, setup steps, known drop-off].
1. Define the first meaningful success event.
2. Remove or defer every step that does not serve it.
3. Script the first three screens with microcopy.
4. Add a measurable drop-off test and recovery email idea..
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
Act as a practical specialist helping me with dashboard signal filter. My context: [metrics, user roles, decisions made there, current layout].
1. Choose the three numbers that trigger action.
2. Separate status, trend and exceptions.
3. Draw a text wireframe with information hierarchy.
4. Define empty, loading and error states..
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
Act as a practical specialist helping me with empty state writer. My context: [feature, reason screen is empty, next action, tone].
1. Write versions for first use, no search results and filtered-out data.
2. Pair each with one primary CTA and optional secondary.
3. Avoid blaming language.
4. Specify what illustration would add information rather than decoration..
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
Help users recover from failure instead of dead-ending.
Act as a practical specialist helping me with error recovery map. My context: [failed action, technical causes, user stakes].
1. Classify recoverable and terminal cases.
2. Write specific error copy with what happened and what to try.
3. Design retry and support paths.
4. Prevent duplicate submissions after a timeout..
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
Act as a practical specialist helping me with microinteraction spec. My context: [component, user action, brand style, accessibility needs].
1. Define feedback timing and animation stages in milliseconds.
2. Specify reduced-motion equivalent and keyboard behavior.
3. Make error and success states clear without color alone.
4. Write test cases for interrupted transitions..
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
Act as a practical specialist helping me with visual identity directions. My context: [brand values, audience, competitors, desired feeling].
1. Describe three distinct directions using palette, type, imagery and motion.
2. Include example hero compositions and a sample button.
3. Name the tradeoff of each.
4. Choose one against audience needs, not personal taste..
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
Act as a practical specialist helping me with usability test script. My context: [product link or flow, participant type, core tasks].
1. Draft neutral tasks that avoid hinting at the answer.
2. Write think-aloud instructions and follow-up probes.
3. Create an observation sheet for hesitation and errors.
4. Define severity and next iteration priority..
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
Act as a practical specialist helping me with responsive layout blueprint. My context: [desktop structure, content priority, breakpoints, device constraints].
1. Reorder content by task priority rather than shrinking it.
2. Specify grid changes and touch targets.
3. Identify horizontal overflow risks.
4. Write visual checks for 320, 390, 768 and 1440 pixels..
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
Help customers compare plans without a spreadsheet headache.
Act as a practical specialist helping me with pricing page ux. My context: [plans, limits, audience, common objections].
1. Choose the right comparison depth and default plan emphasis.
2. Write honest feature labels and a yearly/monthly toggle rule.
3. Surface cancellation and overage terms where decisions happen.
4. Outline mobile presentation..
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
Act as a practical specialist helping me with search ux upgrade. My context: [content types, search behavior, common queries, result count].
1. Define instant results, typo handling and synonym strategy.
2. Write zero-result and partial-match states.
3. Show result cards with decision-making metadata.
4. Set latency and relevance tests..
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
Act as a practical specialist helping me with design critique protocol. My context: [mockup description, design goal, target users, constraints].
1. Separate objective failures from taste opinions.
2. Critique hierarchy, clarity, accessibility and consistency.
3. Prioritize three edits with expected impact.
4. Write questions to test with real users..
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
Act as a practical specialist helping me with trust signals placement. My context: [offer, proof available, audience doubts, current page].
1. Map each objection to the proof that answers it.
2. Place testimonials, specifics and guarantees at decision points.
3. Flag weak or unverifiable claims.
4. Propose a lean mobile proof layout..
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
Act as a practical specialist helping me with notification experience. My context: [event types, urgency, channels, quiet hours].
1. Sort notifications by criticality and user control.
2. Write examples for in-app, email and push.
3. Set batching, dedupe and expiry rules.
4. Design settings defaults and a test for notification fatigue..
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
Remove friction while keeping costs and choices clear.
Act as a practical specialist helping me with checkout flow audit. My context: [cart, payment steps, shipping rules, return policy].
1. Map every required decision and surprise cost.
2. Propose a minimal step sequence with edit and back paths.
3. Surface total and delivery details before final commit.
4. Write recovery states for decline and timeout..
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
Act as a practical specialist helping me with motion language guide. My context: [brand, key components, performance limits, motion examples].
1. Set principles for entrance, feedback and spatial continuity.
2. Give durations and easing for three interactions.
3. Define reduced-motion alternatives.
4. Specify a performance budget and jank test..
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.