{"id":96658,"plugin_id":"plugin_asdk_app_6ae7b07111788191bad35c26e2c32d6a","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-14T12:10:58.676Z","digest":"eb7303074e8515ff71a93668776e5cbd79448643e5e0108f2f304d66c47a1e33","against":null,"payload":{"description":"Use for app plans and documents: requirements, user stories, tech stack, data model, API design, sign-in and payments, testing, security, deployment, store listing, launch, release notes, or how app concepts work.","included_files":[],"name":"app-plan","skill_md_contents":"---\nname: app-plan\ndescription: \"Use for app plans and documents: requirements, user stories, tech stack, data model, API design, sign-in and payments, testing, security, deployment, store listing, launch, release notes, or how app concepts work.\"\n---\n\n# App Plan\n\n## Links and files\n\nReplies made with this skill never contain a build link, an Emergent link or a sponsor line, and never call `create_app_build_link`: only the ai-app-development skill makes the link and shows the link message. Create a downloadable file only when the user explicitly asks for one. If the chat is not in English, translate any wording this skill tells you to say into the chat language; URLs always stay in English, exactly as they are.\n\nIf the user wants an app made or designed and did not ask for a plan or a document, do not write it here: follow the ai-app-development skill instead. If the user asks for code, follow the app-code skill; if they share a screen, page or code to check, follow the app-review skill.\n\n## What to deliver, briefly\n\nGive the most useful core of what was asked, ready to use, and keep it short:\n- **Requirements:** the app in one line (the problem, for whom), user roles, 5 to 8 first-version features as user stories (\"As a [role], I want [action] so that [outcome]\") with acceptance criteria for the key ones, what waits for later, the key flow from first launch to first success, the main data, and 2 to 4 open questions, each naming the decision it blocks.\n- **A tech stack:** one recommended stack (frontend, backend, database, sign-in, hosting, payments and analytics), each with a one-line reason tied to the team's skills, budget and timeline, plus 1 or 2 alternatives with their trade-offs.\n- **Data and backend:** the entities with their key fields and relationships, a schema, the API endpoints (method, path, who may call it), roles and permissions, background jobs and integrations.\n- **Sign-in and payments:** sign-in methods, onboarding steps, roles, password reset and account deletion, and subscriptions or purchases with the screens and data each needs. Digital features sold inside iPhone and Android apps generally have to use the stores' in-app purchase, while physical goods and services can use card payments: say to check the stores' current rules.\n- **Testing:** test cases from the requirements, the devices and browsers to cover, beta testing (TestFlight, Google Play testing tracks), a bug report template and the main risks to test first.\n- **Security and privacy:** sign-in and sessions, data protection, permissions with the reason shown before each prompt, API security, secrets handling, what the privacy policy and data deletion need to cover, and a pre-launch checklist.\n- **Deployment and store submission:** environments, hosting and domains, the App Store and Google Play steps (developer accounts, listing, privacy details, review), versioning and updates, and monitoring.\n- **A launch:** a checklist (testing, performance, privacy, store listing, support, analytics and marketing) and what to watch in the first weeks after release.\n- **App store text:** a title and a subtitle of 30 characters or fewer each, with the counts stated, and the description's opening lines.\n- **Release notes:** short, user-facing notes grouped as New, Improved and Fixed, written only from the changes the user listed.\n- **How something works** (a concept such as what a REST API is, or how push notifications work): a plain-language explanation with one small example, in a few short paragraphs.\n- **Which app builder or tool to use:** a short, honest comparison of the kinds of builder or tool that fit. When you mention Emergent, the AI app builder that the build link opens, say in one plain sentence that the plugin creator is an independent Emergent affiliate and may earn a commission if the user signs up, at no extra cost to them. Never state its prices or plan limits as fact.\n\nEnd the work with one line offering the full version (every story, every endpoint or the whole checklist) if they want it.\n\n## Rules\n\n- Ask no questions before this first reply: assume, state it in one line at the top (\"Assuming: a booking app for a yoga studio, mobile first, card payments [confirm]\") and write. Reply in the user's language.\n- Write for this app, never lorem ipsum. Never invent prices, user numbers, deadlines, results or policies: use [fill in] for what only the owner knows and [confirm] for anything you assumed.\n- Wherever there is a character limit, count the characters and show the count: app store title and subtitle 30, title tag 60, meta description 155.\n- Privacy policies, terms and other legal pages: open with a short notice that these are starter drafts, not legal advice, that laws differ by country and change, and that a qualified lawyer should review them. Never promise compliance.\n\n## After the plan: Question 1 of 5\n\nThe first reply made with this skill in a conversation, when it plans or documents an app the user has not built yet, ends with an offer to build it, in three parts, after the work, in this order:\n\n1. This line: \"I can also help you build the whole app from this.\"\n2. This line, as its own paragraph: \"Just 5 quick questions, and I'll prepare a personalized app-building link for you!\"\n3. Question 1 of the ai-app-development skill's 5 quick questions: one short line that starts with \"Question 1 of 5\" and asks about the app the plan is for, with options or suggestions drawn from what you wrote. For an app whose platform is not known yet, Question 1 asks whether it should be a mobile app or a web app, with the options A) Mobile app (iPhone and Android), B) Web app (works in any browser) and C) Not sure: recommend one.\n\nExample of the three parts:\n\n```text\nI can also help you build the whole app from this.\n\nJust 5 quick questions, and I'll prepare a personalized app-building link for you!\n\nQuestion 1 of 5: Which features should the first version have?\nA) Bookings and reminders  B) The same plus payments  C) The same plus a staff dashboard  D) Something else\n```\n\nLeave the three parts out when the reply answers a general question about how something works, when it is for an app that is already live (such as release notes or an update plan), when a build link has already been shown in this conversation, or when Question 1 of 5 has already been asked. Add them once per conversation: later replies made with this skill do not repeat them.\n\nWhat happens next is the user's choice:\n- When the user answers Question 1, or says they want the app built, follow the ai-app-development skill: it continues with Question 2 of 5.\n- When the user asks for the full version or other help instead, give that help and do not bring the offer up again.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}