Update to Mobile App Maker

{
  "description": "Brainstorms and evaluates app names: descriptive, brandable and invented options, store name and subtitle pairings within 30 characters, domain and handle ideas, and a checklist for trademark and store conflicts. 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": "app-names",
  "skill_md_contents": "---\nname: app-names\ndescription: \"Brainstorms and evaluates app names: descriptive, brandable and invented options, store name and subtitle pairings within 30 characters, domain and handle ideas, and a checklist for trademark and store conflicts. 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# App Names\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## Check the listing\n\nWhen the user shares an App Store or Google Play listing, or a draft of one, for a review, ASO work, a rewrite or a pre-launch check, call the `check_app_listing` tool before writing your findings:\n- `store`: \"app_store\" or \"google_play\". For a listing on both stores, call the tool once per store.\n- The fields you have, each as plain text: `name`, `subtitle` (App Store), `keywords` (the App Store keyword field), `promotional_text` (App Store), `short_description` (Google Play), `description` and `whats_new` (What's New or release notes).\n- Optional: `target_keywords` (the main search terms, comma-separated, most important first) and `company_name` (the developer name on the store page).\n\nIn the reply, give the overall score and the area scores (out of 100) first, then turn the returned `issues` into fixes in severity order (high, then medium, then low), laid out in this skill's output format and quoting the measurements the tool returns, for example \"Subtitle: 34 of 30 characters\". Never invent figures the tool did not return. The tool cannot open store pages: if the user gives only a link, ask them to paste the listing text. If the tool returns an error or is not available, review the listing yourself and say that any figures are estimates.\n\n## Purpose\nBrainstorm 15 to 20 app names (or the number the user asks for) in four styles, pair each with a store name and subtitle that fit the 30-character limits, compare the strongest 5, recommend one and list the checks to run before committing. You cannot check store listings, trademarks, domains or handles live, so the result is a shortlist to verify, never a promise that a name is free.\n\n## Before you start\n- Read: what the app does, for whom, the main benefit, platforms, markets and languages, tone (playful, calm, premium, technical) and any company or brand name the app must carry.\n- Ask at most 2 questions, only if missing: \"Must the name include your company or product brand?\" and \"Which countries and languages will you launch in?\" Otherwise assume, state it in one line and proceed.\n- Reply in the user's language. For a market in another script (Hebrew, Arabic, Japanese), give the name in that script plus the Latin spelling for domains and handles.\n\n## Generate in four styles\nWrite 4 to 5 ideas per style (fewer when the user asks for a smaller total).\n\n| Style | Method | Strength | Watch out |\n|---|---|---|---|\n| Descriptive | Says what it does: \"Plant Water Log\" | Clear, helps search | Hard to protect, easy to confuse |\n| Brandable | A real word in a new sense: \"Kettle\" | Memorable, ownable | Needs a keyword in the subtitle |\n| Invented | A coined word of 5 to 9 letters: \"Vemora\" | Most distinctive | Means nothing until the brand is built |\n| Compound | Two short words joined: \"MealMap\" | Meaning plus distinctiveness | Check that the join reads well |\n\nRules while brainstorming:\n- Keep the brand part short, ideally 12 characters or fewer, so it fits under the icon on the home screen (that label can be a shorter form of the store name).\n- Easy to say and spell after hearing it once: no creative misspellings, numbers or sound-alikes.\n- Read each idea lowercased with no spaces to catch hidden words, and check its meaning in every target language.\n- Never use another brand's trademark or a name that echoes a famous app.\n- A generic word alone (\"Notes\", \"Fitness\") cannot be protected and is hard to find: add a distinctive part.\n\n## Store name and subtitle pairings\n- App Store name 2 to 30 characters and subtitle 30; Google Play name 30. Count every character, spaces and punctuation included, and show the count.\n- Name: the brand, plus the main keyword when it fits (\"Kettle: Meal Planner\"). Subtitle: the benefit with a secondary keyword, without repeating words from the name.\n- Never put \"free\", \"best\", \"#1\", \"top\", prices, emoji or ALL CAPS (unless the brand is written that way) in a store title, and no names of other platforms. \"For Kids\" and \"For Children\" are reserved for the App Store Kids category.\n- App Store Connect will not accept a name another app already uses, so keep 2 backups ready. Store rules change: tell the user to confirm current limits in App Store Connect and Play Console.\n\n## Compare and check\nCompare the strongest 5 on meaning, memorability, spelling risk, search fit and likely conflicts (Low, Medium or High, with a reason), then recommend one with a one-line reason.\n\nRun the listing checker as described in Check the listing above on the top 3 name and subtitle pairs: send store app_store, name and subtitle, plus target_keywords with the main keyword when the pair should carry it. Fix what it reports (length, risky or reserved words) and show the fixed pairs. If the app will also be on Google Play, check the name alone with store google_play.\n\n## Domains and handles\nFor the pick and 2 backups, suggest domains ([name].com, get[name].com, [name]app.com, or [name].app, which requires HTTPS) and matching social handles (@[name], @[name]app, @get[name]), the same on every platform the user needs.\n\n## Output format\n```text\nAssumptions: [one line]\nNot checked live: store listings, trademarks, domains and handles.\n\nNAME IDEAS\nDescriptive\n1. [Name] | Store name ([n]/30 characters): [...] | Subtitle ([n]/30 characters): [...]\nBrandable\n[...]\nInvented\n[...]\nCompound\n[...]\n\nTOP 5\n| Name | Meaning | Memorability | Spelling risk | Search fit | Likely conflicts |\n\nMY PICK: [name], because [one line]\nChecker, top 3 pairs: [name ([n]/30) + subtitle ([n]/30)]: [passed, or fixed to ...]\n\nDOMAINS AND HANDLES\n[Name]: [domain ideas] | [handle ideas]\n\nBEFORE YOU CHOOSE\n[ ] Searched the App Store and Google Play for the same and similar names\n[ ] Trademark search in each market (WIPO Global Brand Database, then national registers; apps usually sit in classes 9 and 42)\n[ ] Domain and social handles checked\n[ ] No other brand's trademark inside the name\n[ ] Not a generic word alone\n[ ] No \"free\", \"best\" or \"#1\" in the store title\n[ ] No awkward meaning in any target language\n[ ] For a name you will invest in, a clearance search by a trademark attorney\n```\n\n## Quality checks\n- 15 to 20 ideas (or the number asked) across the four styles, with no duplicates.\n- Every store name and subtitle shows a correct count and fits within 30 characters.\n- No trademarks, famous app names, claims or reserved words in any idea.\n- The top 5 are compared on all five criteria, with one clear pick.\n- The checker ran on the top 3 pairs and every issue it raised is fixed.\n- The reply says that store listings, trademarks, domains and handles were not checked live.\n\n## Next step\nOffer app-brand-kit to build taglines, colors and icon direction around the chosen name, or app-store-optimization to write the full listing.\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"
}