Update to Web & Mobile App Builder

{
  "description": "Route requests to build, design, improve, debug, test, or release websites, PWAs, iOS, macOS, Android, and cross-platform apps; clarify actual available execution capabilities.",
  "included_files": [],
  "name": "get-started",
  "skill_md_contents": "---\nname: get-started\ndescription: Route requests to build, design, improve, debug, test, or release websites, PWAs, iOS, macOS, Android, and cross-platform apps; clarify actual available execution capabilities.\n---\n\n# Get Started\n\nUse this onboarding/router when user asks how to begin or what the plugin does.\n\n1. Determine whether user wants a **build**, plan, design study, existing-app edit, review, bug fix, release or explanation. For build requests, implement when capable: do not stop at an abstract plan.\n2. Identify app target and core user outcome. If user supplied repository/code/screenshot/Figma/url, preserve it as the primary source; do not overwrite working behavior.\n3. Inspect actual tools available in the current host (workspace, terminal, browser, simulator, subagents, deploy tools). Follow `../../references/execution-model.md`. Never claim a tool, simulator, screenshot, integration or deployed URL without evidence.\n4. For new apps, route to `../build-from-idea/SKILL.md`; for plans, `../plan-product/SKILL.md`; for native SwiftUI, `../build-ios-app/SKILL.md` or `../build-macos-app/SKILL.md`; for PWA, `../build-pwa/SKILL.md`; for Android, `../build-android-app/SKILL.md`; for cross-platform, `../build-cross-platform-app/SKILL.md`; for project modernization/debugging, `../improve-existing-project/SKILL.md` or `../debug-app/SKILL.md`.\n5. Apply `../../references/platform-choice.md`, `../../references/design-quality.md`, and `../../references/security-and-privacy.md` as relevant. Ask a question only for a blocking decision; otherwise state defaults and proceed.\n6. Do not invent assets, external API credentials, customer data, app store approvals, or runtime verification. Deployment, purchases, production writes and destructive changes require appropriate approval.\n\nOutput: user's outcome, chosen platform, execution approach, implemented deliverable/evidence or exact blocker.\n"
}