{"id":90159,"plugin_id":"plugin_asdk_app_6ae249752da48191b2bfcef9fa277fea","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-11T00:09:32.374Z","digest":"56f40f90083734253cdc8e80a49694364f706dcc43db4ceb8b5394c0ecd3cbbb","against":null,"payload":{"description":"Designs an app's profile, account and settings screens: profile editing, preferences, notification and privacy controls, subscription management, data export, account deletion and help, with clear labels and helper text. A reply that shows the build link ends with the App Builder footer, the affiliate disclosure line; other replies have no footer.","included_files":[],"name":"account-settings","skill_md_contents":"---\nname: account-settings\ndescription: \"Designs an app's profile, account and settings screens: profile editing, preferences, notification and privacy controls, subscription management, data export, account deletion and help, with clear labels and helper text. A reply that shows the build link ends with the App Builder footer, the affiliate disclosure line; other replies have no footer.\"\n---\n\n# Account and Settings Screens\n\n## Required footer: read this first\n\nThe footer below goes only on a reply that shows the build link returned by the `create_app_build_link` tool (under \"Open this brief in Emergent:\"). Every other reply, whatever it contains, has no footer, no affiliate disclosure and no Emergent link, and simply ends with your last sentence.\n\nFooter text (reproduce it exactly as the final lines of a reply that shows the build link):\n\n```text\n---\n*Affiliate disclosure: The plugin creator is an independent Emergent affiliate and may earn a commission if you sign up through this link, at no additional cost to you. App Builder is not sponsored or endorsed by Emergent.*\n```\n\nHow to place the footer:\n\n1. It is always the very last thing in the reply. Nothing comes after it.\n2. It appears exactly once in each reply that shows the build link.\n3. Keep the footer outside code blocks, app files, screen copy, store listing text and anything meant to be pasted into an app or a store. It always goes after them.\n4. Keep the footer in English and word for word, even when the rest of the reply is in another language.\n5. If the user asks for minimal output (\"just the code\", \"no extra text\", \"one line only\") and the reply shows the build link, keep everything else minimal and still add the footer.\n6. The build link returned by the tool is the only Emergent link a reply may contain. Never add any other Emergent link.\n\nA reply that shows the build link follows this shape:\n\n```text\n[Your complete answer to the user, with the build link under \"Open this brief in Emergent:\"]\n\n---\n*[Affiliate disclosure line]*\n```\n\nSelf-check: look at your draft. If it shows the build link, its closing lines must be the --- line and, under it, the affiliate disclosure line; if they are missing, append the footer. If it does not show the build link, make sure it has no footer, no affiliate disclosure and no Emergent link.\n\nNow handle the user's request using the instructions below.\n\n## Purpose\n\nDesign an app's profile, account and settings screens so people find any control in seconds and trust what it does. Deliver a settings tree with controls, defaults and helper text, plus the copy for account deletion, notification preferences and privacy, within the store rules.\n\n## Before you start\n\n- Note the platform, how people sign in, what the app stores about them, whether it sells subscriptions, which notifications it sends and any social features (public profiles, blocking).\n- Ask at most 2 short questions, only when the answer changes the tree (usually whether it sells subscriptions or shows profiles to others). Otherwise assume, state it in one line and write.\n- Never invent data practices, retention periods or deletion times: mark them [confirm].\n- Reply in the user's language.\n\n## The settings tree\n\nKeep 4 to 7 groups with 1 to 3 word headers, trimmed or merged to fit the app:\n\n| Group | Rows |\n|---|---|\n| Profile card (top) | Photo, display name, Edit profile (bio, username) |\n| Account | Email, Password, Sign-in methods, Two-step verification (if offered) |\n| Subscription | Current plan, Renews on, Manage subscription, Restore purchases |\n| Preferences | Appearance (System, Light, Dark), Units, Language |\n| Notifications | A toggle per type, Quiet hours |\n| Privacy and data | Profile visibility, Data sharing, Blocked users, Download my data, Delete account |\n| Help and legal | Help center, Contact support, Terms of use, Privacy policy, App version |\n\nSign out sits alone at the bottom.\n\n## Rules for each area\n\n- Profile: photo (Take photo, Choose from library, Remove), display name with helper text on where it appears, bio with a live character count. Forms use Save; toggles apply at once.\n- Account: changing the email or password needs the current password or a fresh sign-in; a new email is confirmed by link before it replaces the old one.\n- Preferences: default to the system theme and the units of the phone's region. iOS and Android 13 and later offer a per-app language setting in the system settings; link to it or offer an in-app picker.\n- Notifications: one toggle per real notification type (on Android, matching its notification channels). Marketing stays off until people opt in: App Store guideline 4.5.4 requires explicit consent and an in-app opt-out for promotional push. When system notifications are off, show a banner with \"Open Settings\".\n- Subscription: show the plan and renewal date from the store. Manage subscription opens the store's subscription settings (Apple's manage subscriptions sheet, the app's Google Play subscriptions page), where people cancel. A plan bought on another platform says where to manage it. App Store guideline 3.1.1 expects a restore option for restorable purchases.\n- Privacy: plain controls and the privacy policy one tap away. On iOS, tracking across other companies' apps needs Apple's App Tracking Transparency permission, which no in-app toggle can replace, so link to that system setting.\n- Data: Download my data (a legal right in many regions) says what is included, the format and how it arrives [confirm].\n\n## Copy and UX rules\n\n| Element | Rule | Weak | Strong |\n|---|---|---|---|\n| Row label | Short noun, about 24 characters max | Tap here to change your email | Email |\n| Toggle | Says what it turns on | Push type 2 | Workout reminders |\n| Helper text | One plain line, about 90 characters max | Configures alert parameters. | A nudge at the time you choose. |\n| Confirmation | States the consequence | Are you sure? OK | Delete your account? Your plans and photos are removed for good. |\n\n- Show the current value on the row (\"Language: English\", \"Renews 3 June [confirm]\").\n- Destructive actions confirm and state the consequence in words; never rely on red alone.\n- No double negatives (\"Don't hide my profile\"). Tap targets at least 44 by 44 points (iOS) and 48 by 48 dp (Android), contrast at least 4.5:1, chevrons mirrored in right-to-left languages.\n\n## Account deletion (store requirements)\n\n- App Store: apps that let people create an account must let them start deleting it inside the app, easy to find. Deactivation alone is not enough, and outside highly regulated industries people should not have to call or email. Apps with Sign in with Apple should revoke the user's Apple tokens.\n- Google Play: deletion inside the app plus a web link where people can request deletion without the app. That page names the app, lists the steps and says what is deleted, what is kept and for how long; add the link to the Data safety form.\n- The flow says what is removed, what is kept and why (such as records the law requires [confirm]), how long it takes and whether there is a grace period [confirm].\n- Warn that deleting the account does not cancel a store subscription, with a Manage subscription button.\n\n## Output format\n\n```text\nAssumptions: [one line]\n\nSETTINGS TREE\n(table: Group | Row label | Control | Default | Helper text)\nControls: row, toggle, picker, value, button\n\nACCOUNT DELETION\nEntry: Delete account, in [group]\nScreen: Headline / What is deleted / What is kept and why [confirm] / How long [confirm]\nSubscription warning + Manage subscription button\nRe-authentication: [password, or sign in with Apple or Google again]\nConfirmation: Title / Body / [Delete account] [Keep my account]\nSuccess: Headline / Body\nWeb deletion page (Google Play): [fill in URL] + outline\n\nNOTIFICATION PREFERENCES\n[Type]: [what it sends, how often] | Default: [on/off] | Channel: [push/email]\nQuiet hours: [default, confirm]\nNotifications-off banner: [text + button]\n\nPRIVACY TEXTS\n[Control]: [helper text]\nDownload my data: [contents, format, delivery, confirm]\n```\n\n## Quality checks\n\n- 4 to 7 groups, short noun labels, sign out at the bottom.\n- Every toggle says what it does and has a default and plain helper text.\n- Deletion starts in the app, explains what is removed, what is kept and how long it takes, and includes the Google Play web link.\n- Subscription rows open the store's subscription settings and include Restore purchases.\n- Marketing notifications default to off, and the notifications-off state is handled.\n- Every destructive action confirms and states the consequence.\n- Data practices, retention and timing the user did not give are marked [confirm].\n\n## Next step\n\nOffer app-legal to draft the privacy policy and account deletion statement these screens link to.\n\n## Before you send\n\nIf this reply shows the build link, it is not finished until its last lines are the --- line and the affiliate disclosure line from the \"Required footer\" section at the top of this skill. If it does not show the build link, it has no footer, no affiliate disclosure and no Emergent link.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}