promote-app-release · v1.3.0 · 2026-11-06 · sha256 034a701fcde69893
promote-app-release v1.3.0A
Immutable. This exact content never changes and is served at /api/v1/blob/034a701fcde69893.
--- name: promote-app-release description: >- Builds a release marketing pack from README Version History: device screenshots, GenerateImage feature board and phone mockup posters, and a newsletter draft. For web apps, builds a professional one-image-per-feature series composited from real browser captures (`/promote-app-release feature-series` runs only that). Asks for brand/app icon (if not already defined) and platform (Android, iOS, or web). Use when the user says promote release, marketing posters, release newsletter, feature highlight images, App Store / Play Store promo images, or asks for release marketing after publish-new-version. compatibility: >- Requires device/simulator tooling (mobile) or a browser automation tool (web) for screenshots, GenerateImage for mobile posters, and Windows PowerShell System.Drawing for the web feature series. license: MIT metadata: author: carrick87 version: "1.3.0" --- # Promote app release ## Goal After a version is already published (or while marketing an existing current version), produce a **promotional pack**: real device screenshots, feature highlight board, mockup posters, newsletter banner + copy. Save under **Desktop** and **`marketing/<VERSION>/`**. **This skill does not bump versions.** Changelog and semver come from `publish-new-version` / README. Do not run a version bump unless the user also asks for `/publish-new-version`. ## Triggers Apply when the user says any of: - promote release / promote app release - marketing posters / promo images - release newsletter - App Store / Play Store promo images - “make posters for vX.Y.Z” ## Commands | Command | Runs | |---------|------| | `/promote-app-release` | Full pack: screenshots, images for the chosen platform, and the newsletter | | `/promote-app-release feature-series` | **Only** the feature series: a cover plus one 1920×1080 image per feature, built from real web captures | `feature-series` also runs when the user says any of: *feature series*, *feature intro images*, *one image per feature*, *intro each feature*, *feature highlight images*, *make it professional* (about earlier promo images), or *create like this* while pointing at an existing feature series. ### `feature-series` command Platform is **web** unless the user says otherwise. Ask for the app icon only if it isn't already defined. Do not bump the version. 1. **Features:** read README Version History and pick 6–8 user-facing features. Use the whole app unless the user asks for what's new only. For each, write a tag, a title of 5 words or fewer, a body of 18 words or fewer, and 3 bullets. Keep the copy factual, with no exclamation marks. 2. **Review (optional):** if earlier images exist or the user calls them unprofessional, have a reviewer subagent critique them first and return a spec and copy. The reviewer doesn't edit files. 3. **Capture:** take the screenshots at 1× in the running app, following [references/web-feature-series.md](references/web-feature-series.md): - Remove the dev overlay and hide scrollbars. - Mask personal data. - Put each screen into a real state that shows the feature. - Save to `marketing/screenshots/<VERSION>/hires/`. 4. **Measure:** get element boxes with `getBoundingClientRect()` at the capture viewport size. Use one crop width for every feature, such as 1254. 5. **Spec:** copy [references/feature-series.example.json](references/feature-series.example.json) to `marketing/<VERSION>/features/feature-series.json`. Fill in product, version, palette, fonts, cover, and for each feature the crop, at most 2 outlines and at most 3 markers. Each marker number must match a numbered bullet. 6. **Build:** ```powershell powershell -NoProfile -ExecutionPolicy Bypass -File "<skill dir>/references/build-feature-series.ps1" -Spec "marketing/<VERSION>/features/feature-series.json" ``` 7. **Check:** open every image. Fix any of these, then rebuild: - A marker covers a label. - A title leaves one word on its own line. - A highlighted row is cut off. - Text overlaps the footer. 8. **Deliver:** - Copy the images to `~/Desktop/<Product>-<VER>-features/`. - Embed them in order in `marketing/<VERSION>/NEWSLETTER.md`, with the source capture behind each one and anything masked or left out. - Report the paths. ## Preconditions — ask before generating **Stop and confirm these inputs before screenshots or `GenerateImage`.** Do not assume StockApp / iOS defaults when the current project or chat has not already defined them. ### 1) Target version + baseline 1. Confirm **target version** (default: README `### vX.Y.Z (Current)`). 2. Confirm **baseline** for “what’s new” copy (default order): - User-stated baseline version, else - Previous `marketing/<version>/` folder if present, else - Last **3 patch** versions of user-facing notes from Version History ### 2) Brand / app icon (required) Ask for a **brand icon or app icon** unless one is already clearly defined in this conversation or the project (e.g. user attached an image, or a known path such as `marketing/<VERSION>/app-icon.png` / asset catalog was already agreed). When asking, accept any of: - An attached image in chat - An absolute or repo-relative file path - A short instruction to reuse the last icon from this chat / `marketing/<VERSION>/app-icon.png` Copy the chosen icon to `marketing/<VERSION>/app-icon.png` and pass it via `reference_image_paths` on every marketing image. **Do not invent or substitute a different logo** (e.g. leaf icons) when the dual-H / project icon is available or the user supplied one. ### 3) Platform (required) Ask which platform this promo pack is for unless already stated in the trigger (e.g. “Play Store only”, “iOS App Store”, “web release”): | Choice | Use for | |--------|---------| | **Android** | Google Play — Android phone frames, punch-hole / flat bezel (not iPhone notch / Dynamic Island), CTA **“GET IT ON Google Play”** / **“Update on Google Play”** | | **iOS** | App Store — iPhone frames, CTA **“Download on the App Store”** / **“Update available”** | | **Web** | Browser / product marketing — desktop or responsive web frames (not phone-first unless user asks), CTA **“Try it now”** / **“Update available”** | If the user picks more than one platform, produce **separate asset sets** (or clearly labeled variants) per platform — do not mix iPhone frames into an Android-only Play Store pack. ### Optional HAR StockApp defaults Only apply these when the project is clearly **HAR StockApp** (or the user says to reuse StockApp defaults): - Brand name: **HAR StockApp** - Icon: `StockMaster/StockMaster/Assets.xcassets/AppIcon.appiconset/1024.png` (dual-H navy/blue) — still confirm if missing from disk - Palette: Harbour Teal + navy — **no purple neon** - OTP bypass for screenshots (if needed): email `admin@testing.local`, username `csd.exec` - Default platform if unspecified for StockApp: **iOS** For other apps (e.g. LeaveApp), derive brand name from the repo/README and **always** ask for icon + platform when not already defined. ## Pipeline ```mermaid flowchart TD trigger[User: promote release / marketing posters] ask[Ask icon if missing + ask platform if missing] readPub[Read publish-new-version skill + README Version History] delta[Diff features since baseline] shots[Capture screenshots for chosen platform] gen[Mobile: GenerateImage posters / Web: composited feature series] news[Draft newsletter copy] out[Save to Desktop and marketing/VERSION/] trigger --> ask --> readPub --> delta --> shots --> gen --> news --> out ``` Execute in order. **Do not start step 2 (screenshots) until icon and platform are resolved.** ### 1) Read changelog source of truth 1. Skim personal/project **`publish-new-version`** skill so you know where versions live — do **not** bump. 2. Parse `README.md` **`## Version History`** from `(Current)` back to the baseline. 3. Optionally cross-check `git log` / tags since baseline. 4. Build a **user-facing** feature table (no SQL, no branch/internal names). Group into poster themes. ### 2) Capture real screenshots Match capture tooling to the chosen **platform**: | Platform | Prefer | Notes | |----------|--------|-------| | **iOS** | Booted iPhone Simulator | Commands: [references/sim-screenshots.md](references/sim-screenshots.md) | | **Android** | Booted Android emulator / device (`adb`) | Capture key tabs; use `screencap` | | **Web** | Running local/staging URL via browser MCP | 1× viewport captures, overlay/scrollbars hidden, personal data masked — see [references/web-feature-series.md](references/web-feature-series.md) | Minimum set depends on the app. For **HAR StockApp** (iOS default): | File | Screen | |------|--------| | `01-search.png` | Search | | `02-sales.png` | Sales Opportunities | | `03-stock-age.png` | Stock Age (filters expanded if possible) | | `04-more.png` / `05-reports.png` | More hub and/or Custom Reports | For other apps, capture the product’s primary tabs/screens (e.g. LeaveApp: Dashboard, Apply, History, Calendar, key detail states). Write to `marketing/screenshots/<VERSION>/`. If UI automation fails, drive as far as possible, document any missing screen in the newsletter footnote, and continue with available shots + icon. ### 3) Generate marketing images #### Web: feature series (default) For **Web**, the primary deliverable is a **feature series**: a cover plus one 1920×1080 image per feature, composited from the real captures. Do not let `GenerateImage` redraw app UI for web; it misorders and mislabels screens. 1. Optionally run a design review with a strong reviewer subagent (critique + layout spec + per-feature copy) before building, especially if the user calls earlier images unprofessional. 2. Pick 6–8 features from Version History (whole app if asked). Each one gets a title of 5 words or fewer, a body of 18 words or fewer, and 3 bullets. 3. Capture and measure element boxes at capture size, then write `marketing/<VERSION>/features/feature-series.json` (template: [references/feature-series.example.json](references/feature-series.example.json)). 4. Build: `powershell -NoProfile -ExecutionPolicy Bypass -File <skill>/references/build-feature-series.ps1 -Spec marketing/<VERSION>/features/feature-series.json` 5. **Look at every output image.** Fix markers that cover labels, titles that leave a one-word line, and cut-off highlighted rows. Then rebuild. Layout, highlight style, capture tricks, and PowerShell gotchas: [references/web-feature-series.md](references/web-feature-series.md). The four `GenerateImage` assets below are optional for web. Build them only if the user asks for them. #### Mobile (and optional web extras) Use **`GenerateImage`** with `reference_image_paths` = **confirmed app icon** + real screenshots. Follow **`imagegen-frontend-mobile`** (device frames, readable UI) and **`brandkit`** (sparse boards) spirit: Harbour Teal / navy when that is the brand palette, readable type. **Frame and CTA rules by platform:** | Platform | Device frames in mockups | Store / CTA wording | |----------|--------------------------|---------------------| | **Android** | Android phones only (punch-hole / thin bezel) | Google Play | | **iOS** | iPhones | App Store | | **Web** | Browser / laptop / responsive web chrome | Product URL / “Try it now” | Deliverables (16:9 unless user asks otherwise). Filename prefix = product short name (e.g. `LeaveApp`, `HAR-StockApp`): | Asset | Filename pattern | Spec | |-------|------------------|------| | Feature highlight board | `<Product>-<VER>-feature-board.png` | “What’s New” cards from delta; include icon; platform badge optional | | Hero mockup poster | `<Product>-<VER>-hero-mockup.png` | 1–2 devices with real key screens | | Feature mockup strip | `<Product>-<VER>-feature-strip.png` | 3 frames of primary screens | | Newsletter banner | `<Product>-<VER>-newsletter-banner.png` | Brand + headline + platform CTA | Copy outputs to: - `~/Desktop/` - `marketing/<VERSION>/` ### 4) Newsletter draft Write `marketing/<VERSION>/NEWSLETTER.md` (and Desktop copy) that: - Embeds the four filenames, or for web the cover + feature series in order - Lists the source capture behind each image and anything masked or left out (e.g. a report that timed out) - Summarizes user-facing bullets for Slack/email paste - Includes a short subject line and CTA matching the chosen platform (Google Play / App Store / web) ### 5) Completion message List absolute paths for: - Screenshots folder - Four images, or for web the feature series (Desktop + `marketing/<VERSION>/`) - Newsletter path - Icon path used - Platform targeted - Any screens that could not be captured Remind: version was **not** bumped; for the next semver release use **publish-new-version**, then re-run this skill. ## Related skills - **publish-new-version** — bump + changelog (run before or separately) - **imagegen-frontend-mobile** — phone mockup framing - **brandkit** — feature board composition - **create-skill** — skill authoring rules (when editing this skill)