Youmake

View saved version →

---
name: create-mobile-app
description: Create an Expo mobile app with Youmake when the user requests a new iOS, Android, or cross-platform mobile application. Use edit-project for an existing Youmake project.
---

1. Read references/workflow.txt before calling tools. Identify the core user task,
   screens, navigation, and requested device capabilities. Ask only for essential
   missing requirements; otherwise state reasonable first-build assumptions.
2. Write a mobile-focused prompt describing touch interactions, safe areas,
   keyboard behavior, loading and error states, and the user's design references.
   Include platform constraints and connected-service requirements when relevant.
3. Call create_project with projectType="mobile", a concise name, and a fresh
   UUID requestId. This selects the Expo template. Continue with its project.id.
4. Call start_build with that projectId, the mobile prompt, and a separate fresh
   UUID requestId. Follow the shared status and recovery procedure.
5. Return the editor/preview links and verified status. Device testing, native
   permissions, signing, and store submission require the Youmake editor and
   platform tooling; completion here does not establish store readiness.

Referenced files: 2 — file references are metadata, not package contents.

View saved version →

---
name: create-slide-deck
description: Create a presentation with Youmake when the user requests a new pitch deck, lesson slides, sales presentation, or slide-based report. Use edit-project for an existing Youmake deck.
---

1. Read references/workflow.txt before calling tools. Identify the audience,
   purpose, desired length, and supplied source material. Ask for essential missing
   content; otherwise state an outline and reasonable slide-count assumption.
2. Write a slide-by-slide build prompt with a clear narrative, concise headlines,
   visual guidance, and supplied data. Label placeholders for missing metrics and
   sources; preserve the distinction between supplied facts and proposed copy.
3. Call create_project with projectType="slides", a concise name, and a fresh
   UUID requestId. Continue only after receiving the deck's project.id.
4. Call start_build with that projectId, the presentation prompt, and a separate
   fresh UUID requestId. Follow the shared status and recovery procedure.
5. Return the preview/editor links and verified status. Slide export and sharing
   are completed in the Youmake editor; these tools do not return a PPTX or PDF.

Referenced files: 2 — file references are metadata, not package contents.

View saved version →

---
name: create-website
description: Create a website with Youmake when the user requests a new landing page, business site, or web application. Use edit-project for an existing Youmake project.
---

1. Read references/workflow.txt before calling tools. Identify the site's purpose,
   audience, pages, and primary action from the conversation. Ask only for missing
   information that prevents a useful first build; otherwise state assumptions.
2. Write a build prompt with the requested content, visual direction, responsive
   behavior, and functional requirements. Distinguish requested integrations from
   features that can be built without connected services.
3. Call create_project with projectType="web", a concise name, and a fresh UUID
   requestId. Continue only after receiving a project.id.
4. Call start_build with that projectId, the build prompt, and a separate fresh
   UUID requestId. Follow the shared status and recovery procedure.
5. Return the resulting preview/editor links and verified status. Publishing and
   domain setup take place in the Youmake editor; a completed build is a preview.

Referenced files: 2 — file references are metadata, not package contents.

View saved version →

---
name: edit-project
description: Continue or modify an existing Youmake website, mobile app, or slide deck when the user requests changes to its content, design, or functionality.
---

1. Read references/workflow.txt before calling tools. Resolve the target using a
   project ID already supplied by Youmake or list_projects. Use pagination when
   needed. If multiple projects fit the request, ask the user to choose.
2. Call get_project with the selected projectId. Proceed when canEdit is true;
   otherwise explain that editor access is needed. Preserve its projectType.
3. Write a prompt containing the requested change and the existing behavior to
   preserve. Obtain clarification before an ambiguous destructive change. Reuse
   the existing project rather than creating a duplicate.
4. Call start_build with that projectId, the edit prompt, and a fresh UUID
   requestId. Follow the shared status and recovery procedure.
5. Report the verified build status and editor/preview links. Describe the
   requested change as confirmed only if tool results or inspection establish it.

Referenced files: 2 — file references are metadata, not package contents.