Update to Mobile App Maker

{
  "description": "Writes an in-app help center and FAQ: questions grouped by task, short step-by-step answers, troubleshooting, account and billing answers that point to the right store settings, and searchable article titles. A reply that shows the build link ends with the Mobile App Maker footer, the affiliate disclosure line; other replies have no footer.",
  "included_files": [],
  "name": "help-center",
  "skill_md_contents": "---\nname: help-center\ndescription: \"Writes an in-app help center and FAQ: questions grouped by task, short step-by-step answers, troubleshooting, account and billing answers that point to the right store settings, and searchable article titles. A reply that shows the build link ends with the Mobile App Maker footer, the affiliate disclosure line; other replies have no footer.\"\n---\n\n# Help Center\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. Mobile App Maker 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\nWrite an in-app help center and FAQ that answers questions before people need support: 8 to 15 questions grouped by task, short step-by-step answers, troubleshooting that works, billing answers that point to the right store settings and titles people find by searching. Deliver the grouped FAQ, 2 full articles for the most important tasks and the help entry points inside the app.\n\n## Before you start\n\n- Use what the user gave: the app's main tasks, platforms, sign-in and subscription setup, the exact menu and button labels, and real questions from support emails or reviews.\n- Ask at most 2 short questions, only when the answer changes the content (usually the platforms, or whether subscriptions are sold in the app or on the web). Otherwise assume, state it in one line and write.\n- Never invent menu names, policies, prices or timeframes: mark assumed details [confirm] and unknown ones [fill in].\n- Reply in the user's language.\n\n## Groups and titles\n\nGroup by task in this order, dropping any that do not apply: Getting started, Account, Subscriptions and billing, [Main features], Troubleshooting, Privacy and data.\n\n- Phrase titles the way users ask: \"How do I...?\", \"Why can't I...?\", \"What happens if...?\"\n- Keep titles under about 60 characters, one task per article, in the user's words rather than internal feature names.\n\n| Weak title | Strong title |\n|---|---|\n| Subscription management | How do I cancel my subscription? |\n| Sync issues | Why aren't my workouts on my new phone? |\n| Data policy | Can I download or delete my data? |\n\nStarter questions to adapt: \"How do I [core task] for the first time?\", \"How do I change my email?\", \"How do I delete my account?\", \"How does the free trial work?\", \"How do I cancel my subscription?\", \"How do I restore my purchase on a new phone?\", \"Why am I not getting notifications?\", \"Why won't the app load?\", \"Who can see my profile?\"\n\n## Answer rules\n\n- 80 words or fewer. The first sentence answers or names the place, then numbered steps, one action each, with the exact labels in bold (\"Tap **Settings**, then **Account**\").\n- Label platform differences: \"On iPhone\", \"On Android\", \"On the web\".\n- End every answer with \"Still need help? Contact us\", so no article is a dead end.\n- Add search keywords (synonyms, everyday words, common misspellings: \"cancel, unsubscribe, stop paying, end trial\") and 2 to 3 related articles.\n\nWeak answer: \"Subscriptions can be managed via the relevant platform settings.\" Strong: \"You cancel in your phone's subscription settings, not in the app. On iPhone: 1. Open **Settings**. 2. Tap your name, then **Subscriptions**. 3. Choose [App] and tap **Cancel Subscription**.\"\n\n## Account and billing answers\n\n- Delete account: give the in-app path (Settings > [group] > Delete account [confirm]) and, for Android, the web deletion page [fill in]; say what is deleted, how long it takes [confirm] and that it does not cancel a store subscription.\n- Can't sign in: remind people to use the method they signed up with (Apple, Google or email), since another method can create a separate account [confirm], then give the reset steps.\n\nStore subscriptions are managed in the store, not the app. Use these paths and tell the user to check them against current OS versions:\n\n- iPhone: Settings > [your name] > Subscriptions > [App] > Cancel Subscription.\n- Android: Google Play Store app > profile icon > Payments & subscriptions > Subscriptions > [App] > Cancel subscription.\n- Web purchases: [App] account > Billing [confirm].\n- Deleting the app does not cancel a subscription. Restoring purchases needs the Apple or Google account that paid.\n- Refunds for store purchases: Apple at reportaproblem.apple.com, Google from the Google Play order history [confirm current steps]. Never promise a refund.\n\n## Troubleshooting order\n\nEvery troubleshooting answer uses the same order, cheapest fix first:\n\n1. Check the connection (Wi-Fi or mobile data on, airplane mode off).\n2. Update the app from the App Store or Google Play.\n3. Restart the app (close it fully), then the phone.\n4. Reinstall, last, after a warning: data saved only on the phone is lost unless it is synced or backed up [confirm how the app stores data].\n\nThen \"Still not working? Report a problem\", with the app version included. When a setting may be the cause (notifications, permissions), check it before step 1: the app's settings, then the phone's (iPhone: Settings > Notifications > [App]; Android: Settings > Apps > [App] > Notifications, varying by phone maker), plus any Focus or Do Not Disturb mode.\n\n## Long-form articles\n\nWrite 2 complete articles for the most important tasks (usually getting started with the core feature, and managing the subscription): a title, a one-line summary, 3 to 6 short sections with numbered steps, notes per platform, one tip, screenshot placeholders with alt text ([Screenshot: Subscriptions screen]), related articles and the contact line. 250 to 500 words each.\n\n## Output format\n\n```text\nAssumptions: [one line]\n\nFAQ\n### [Group]\n**[Question in the user's words?]**\n[First sentence answers.]\n1. [Step]\n2. [Step]\nKeywords: [...]\nRelated: [title], [title]\nStill need help? Contact us\n(8 to 15 questions in total)\n\nARTICLE 1: [title]\n[full article]\n\nARTICLE 2: [title]\n[full article]\n\nHELP ENTRY POINTS\n- [Where in the app]: [label] > [what opens]\n```\n\nEntry points to consider: Settings > Help, a \"?\" on complex screens, empty states, error screens, the paywall (\"How does the free trial work?\") and a web version of the help center, which can double as the App Store support URL if it includes contact details.\n\n## Quality checks\n\n- 8 to 15 questions grouped by task, titles in the user's words, no duplicates.\n- Every answer is 80 words or fewer, answers in its first sentence and uses numbered steps.\n- Troubleshooting follows connection, update, restart, reinstall, with a data warning before reinstalling.\n- Billing answers point to the iPhone and Android subscription settings and never promise refunds.\n- Every entry has keywords, 2 to 3 related articles and a contact line.\n- Labels, policies and timeframes not given are marked [confirm].\n- 2 complete long-form articles are included.\n\n## Next step\n\nOffer support-feedback to design the contact and bug report screens these articles 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"
}