← Back to Superprez

AI prompt templates & Superengine zip packaging

Copy-ready prompts plus how to assemble a zip that matches Superengine port conventions. Browse official port repos on Superengine Git, then tailor your archive for Superprez drop-code or collaborator uploads.

Prepare a zip the way Superengine ports expect

Superengine ships many reference “port” repositories (templates showing layout, Dockerfile snippets, hooks, metadata). Explore them here: https://software.superengine.tech/explore/repos. Pick a port closest to your stack (for example Handlebars/HTML or Node-centric examples), mirror its file tree, then replace body content with your presentation app—do not invent a layout that diverges from the port README without reason.

Typical files to ship in drop-code zip

Exact names vary by port; always cross-check the specific repository you cloned from Superengine Explore.

  • README.md — how to build/run; note env vars for operators.
  • package.json + committed lockfile (e.g. package-lock.json) with build and start scripts where applicable.
  • Dockerfile or whatever container/build entry the chosen port demonstrates.
  • Application source folders the port specifies (often src/, public/, templates, assets).
  • .env.example — every secret or toggle with placeholder values.
  • Cover image for Superengine portfolio: many ports document a raster image such as picture.png (dimensions and filename follow the README of the repo you fork). Superprez usually shows the dashboard title separately; treat this PNG as lightweight catalog metadata—the AI may generate something minimal (solid brand color, gradient, simple icon) so operators are not blocked. Keep it tiny (e.g. under a few hundred KB).
  • Any additional metadata files referenced in port docs (.dockerignore, etc.).

Before zipping: delete node_modules, .next, build artifacts, OS junk (__MACOSX, .DS_Store).

Return to narrative context: Packaging & build expectations, Drop code & zip updates in Superprez.

Prompt templates for AI assistants

Replace bracketed fields. When scoping structure, cite the concrete port repo filenames you mirrored from Superengine Explore.

1) Build a flagship company presentation app (style, logo, legacy decks)

Use when marketing or leadership hands you PDFs/PPTX plus brand assets and you need a Superprez-ready web app.

You are a senior front-end engineer. Build a single interactive presentation web app for [COMPANY] targeting [AUDIENCE]. Brand & assets: - Primary colors: [HEX / tokens]. Font stack: [FONTS]. Logo path: /assets/logo.svg (I will place the file). - Recreate narrative flow from these sources: [upload paths to PDF/PPTX or describe sections]. Match slide order and key metrics; improve clarity but do not invent financials. Product expectations: - Output a clean repo structure with package.json scripts: "build" and "start", plus a lockfile. - Use [FRAMEWORK] with accessible components, responsive 16:9 layout, keyboard navigation between sections. - Implement at least two interactive moments (e.g., scenario slider + tabbed proof) tied to real data provided in /data. - Superprez will show the deck title from its dashboard field, not from your <title> alone—still set a sensible document title for browser tabs, and keep in-repo copy aligned with "[DECK_DISPLAY_NAME]". Deliverables: - README with setup, env vars, and how to zip the project excluding node_modules. - Include picture.png per the Superengine port template you mirrored (simple gradient/brand block is OK; see Superengine port README). - Optional /docs/NOTES.md describing mapping from legacy slide numbers to new sections.

2) Prepare a repo for personal GitHub + Superprez

Covers what must exist before the presenter connects or pushes from Superprez.

You are helping me ship a deck repo to GitHub for Superprez/Superengine. Requirements: - Initialize [FRAMEWORK] app with deterministic dependencies and lockfile. - Add CI-friendly scripts; no local absolute paths. - Mirror the filesystem layout documented in Superengine Explore port repos: https://software.superengine.tech/explore/repos (cite which *-port you followed). - Default branch main. Squash stray binaries; use LFS only if unavoidable. - Document required secrets (API keys, map tokens) with placeholder names matching .env.example. - Generate a minimal placeholder picture.png if the chosen port expects one—flat color OK. Provide: - Commands: install, lint (if any), build, preview/start. - A checklist verifying GitHub PAT scopes the user needs. Both PAT types work in Superprez: fine-grained PAT needs Administration + Contents + Webhooks (read & write) plus Metadata (read); classic PAT needs the "repo" scope plus "admin:repo_hook" (and "read:org" for org-owned repos). - Guidance to avoid files >50MB without Git LFS so zip uploads remain practical.

3) Edit zip exported from Superprez and ship it back

Mirrors the collaborator / owner workflow in-product.

You have the Superprez source zip mounted at ./deck.zip. Tasks: 1) Unzip locally. Identify default branch folder layout (often one root directory); keep that structure intact. 2) Apply these UI/content changes: [LIST]. 3) Remove node_modules, .next/.cache, build artifacts before re-zipping. 4) Keep picture.png/port metadata updated if visuals changed materially (optional simple regen acceptable). 5) Produce deck-resubmit.zip <12MB ready for HTTP upload JSON base64 flows. 6) Summarize which files changed and why for the presenter changelog. Reminder: each upload becomes one snapshot commit on main (Superprez rebuilds the git tree from the zip rather than computing a textual diff), followed by automated check-for-update + update on Superengine; note if a dependency change warrants npm install messaging.

4) Debugging a failed Superengine build

Given this Superprez-linked repo tarball and Superengine stderr [PASTE], enumerate: 1) Missing dependency/build script issues 2) Node version mismatches vs engine field 3) Files not committed but imported (including missing picture.png if required by port) 4) Static asset path casing problems Produce a prioritized patch checklist and unified diff stubs.

5) Collaborator onboarding without GitHub

Write a concise email for [NAME] explaining they can iterate on slide [X] inside the zipped project, run it locally via [COMMANDS], and return deck.zip without GitHub CLI access. Mention Superprez will push for them, and optionally link to Documentation → Collaboration section.

6) Differentiate presenter title vs embedded deck headline

Coach the presenter: Superprez uses the dashboard title "[SUPERPREZ_TITLE]" independently of the app's internal H1 "[IN_APP_HEADLINE]". Tasks: 1) When should they match vs differ (e.g., confidential codename externally)? 2) Provide microcopy snippets for aligning both after rebrands. 3) Suggest changelog tags for syncing marketing + product decks.