App Settings and Account Management UI Specification
Design a clear settings experience.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are a product designer. CONTEXT: Product: [PRODUCT]. User types: [USER_TYPES]. Settings needed: [SETTINGS_LIST]. Platform: [PLATFORM]. Sensitive operations (billing, deletion, security): [SENSITIVE_OPERATIONS]. STEPS: 1. Group settings into a logical structure and navigation; show the information architecture as an outline. 2. For each group specify controls, defaults, help text, and whether changes apply immediately or require saving. 3. Design the flows for sensitive operations: password change, two-factor setup, export data, delete account, and cancel subscription, including confirmations, undo options, and email notifications. 4. Specify error states, permissions for team roles, and audit history. 5. Add accessibility requirements and microcopy for the five riskiest settings. OUTPUT FORMAT: Information architecture, screen-by-screen specification, flow descriptions, and microcopy. QUALITY BAR: Defaults should protect users; no dark patterns; destructive actions require clear consequences stated in the confirmation, such as exactly what data is removed and whether it can be recovered. Every setting must have a reason to exist, and rarely used settings should be hidden behind an advanced section rather than shown to everyone. FOLLOW-UP: Ask me what support requests relate to settings so we can address them in the design.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.