Unbounce

Build me a focused websites and landing pages workflow for the personal core of Unbounce. Requirements:

- Use Next.js 15, TypeScript, Tailwind CSS, SQLite, Drizzle ORM, and static export. Persist projects in SQLite and support a portable JSON export.
- Paid product context: Create a focused landing-page builder and run a small user-controlled A or B test. Build only this DIY scope: Assemble responsive landing pages, edit copy and media, preview breakpoints, run a small user-controlled A or B test, and publish a static site to a user-owned target.
- For websites and landing pages, define pages, route slugs, assets, and draft/published revisions.
- Edit one page with the supported components and preview it at mobile and desktop widths.
- Publish a static build or export the site files with an asset manifest.
- Use a local web page with input, progress, review, and export views. Required input or access: domain and deploy target; local images. Keep credentials in .env.
- Recovery: Preview desktop, tablet, and mobile widths and surface overflow errors.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: A failed publish must leave the last published revision intact; internal links must resolve in the exported site.
- Out of scope: managed traffic routing, experimentation, integrations, templates, and conversion intelligence; large template marketplace. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

# AGENTS.md — Build guide for Unbounce

## Project scope
Assemble responsive landing pages, edit copy and media, preview breakpoints, run a small user-controlled A or B test, and publish a static site to a user-owned target.

Catalogue verdict: no. A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Unbounce, create a focused landing-page builder and run a small user-controlled A or B test. The hard boundary is managed traffic routing, experimentation, integrations, templates, and conversion intelligence, plus editor polish, hosting, templates, and ecosystem.
Use the implementation prompt below to define the deliverable. Complete each phase's acceptance checks before extending the scope.

## Working agreement
- Inspect the repository and its existing instructions before choosing paths, dependencies or commands. Keep one coherent stack and explain changes to the proposed architecture.
- Plan a vertical slice that accepts a real input and produces the useful output described below. Persist only the state the prompt calls for; respect memory-only and upstream-managed workflows. Use fixtures only when they are clearly labelled.
- After scaffolding, document the actual install, development, check and build commands in README and keep them synchronized with the package or project manifest. Do not report commands as successful unless they ran.
- Work in small steps. At handoff, list implemented flows, checks actually performed, remaining blockers, and any credentials or provider setup the owner must supply.
- Do not publish, spend money, contact customers, delete source data or run irreversible migrations without the project owner's authorization.

## Prerequisites
- Node.js 22
- domain and deploy target
- local images
- optional form-email API key

## Stack and architecture
- Use Next.js 15, TypeScript, Tailwind CSS, SQLite, Drizzle ORM, and static export.
- Persist projects in SQLite and support a portable JSON export.
- Interface for this websites and landing pages workflow: a local web page with input, progress, review, and export views.

## Security and data integrity
- Preview desktop, tablet, and mobile widths and surface overflow errors.
- Keep API keys and OAuth secrets in .env; redact them from logs, generated files, and error responses.
- State the practical limit: managed traffic routing, experimentation, integrations, templates, and conversion intelligence.

## Agent implementation rules
- Project rule, data: Persist projects in SQLite and support a portable JSON export.
- Project rule, behavior: Allow inline text editing and local image upload with responsive optimization.
- Project rule, recovery: Preview desktop, tablet, and mobile widths and surface overflow errors.

## Optional agent skills and references
No installable skill is listed for this guide; use the project rules and the stack documentation.

Read the linked SKILL.md and its dependencies before adding a skill. Select only the skills matching this project's runtime and task; their documentation does not supply API access, credentials or approval to perform external actions. Pin the reviewed revision where the tool supports it. Follow the chosen agent's documented project-level installation mechanism.

## Distribution ideas
These are optional planning notes. Obtain the owner's approval before publishing or contacting anyone.
- Demonstrate this websites and landing pages operation with sample or user-owned data: Allow inline text editing and local image upload with responsive optimization.
- Show a concrete result or export: Use Next.js 15, TypeScript, Tailwind CSS, SQLite, Drizzle ORM, and static export; do not offer alternative stacks.
- State the practical limit: managed traffic routing, experimentation, integrations, templates, and conversion intelligence.

## Engineering roadmap
1. Phase 1, architecture and data: Use Next.js 15, TypeScript, Tailwind CSS, SQLite, Drizzle ORM, and static export. Persist projects in SQLite and support a portable JSON export.
2. Phase 2, implement: Allow inline text editing and local image upload with responsive optimization.
3. Phase 3, implement: Generate a clean static Next.js output and document deployment to one target.
4. Phase 4, review and output: Assemble responsive landing pages, edit copy and media, preview breakpoints, run a small user-controlled A or B test, and publish a static site to a user-owned target. Use Next.js 15, TypeScript, Tailwind CSS, SQLite, Drizzle ORM, and static export; do not offer alternative stacks.
5. Phase 5, recovery and acceptance: Preview desktop, tablet, and mobile widths and surface overflow errors. Verify this invariant with a saved fixture: A failed publish must leave the last published revision intact; internal links must resolve in the exported site. State the practical limit: managed traffic routing, experimentation, integrations, templates, and conversion intelligence.

## Paid-product capabilities outside this build
- managed traffic routing, experimentation, integrations, templates, and conversion intelligence
- large template marketplace
- managed hosting and CDN
- advanced CMS
- commerce and agency workflows

## Implementation prompt
Build me a focused websites and landing pages workflow for the personal core of Unbounce. Requirements:

- Use Next.js 15, TypeScript, Tailwind CSS, SQLite, Drizzle ORM, and static export. Persist projects in SQLite and support a portable JSON export.
- Paid product context: Create a focused landing-page builder and run a small user-controlled A or B test. Build only this DIY scope: Assemble responsive landing pages, edit copy and media, preview breakpoints, run a small user-controlled A or B test, and publish a static site to a user-owned target.
- For websites and landing pages, define pages, route slugs, assets, and draft/published revisions.
- Edit one page with the supported components and preview it at mobile and desktop widths.
- Publish a static build or export the site files with an asset manifest.
- Use a local web page with input, progress, review, and export views. Required input or access: domain and deploy target; local images. Keep credentials in .env.
- Recovery: Preview desktop, tablet, and mobile widths and surface overflow errors.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: A failed publish must leave the last published revision intact; internal links must resolve in the exported site.
- Out of scope: managed traffic routing, experimentation, integrations, templates, and conversion intelligence; large template marketplace. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

## Completion evidence
Demonstrate the prompt's acceptance scenarios against the scoped workflow. Include setup from a clean checkout and failure recovery. Check persistence across restart and export/restore only for the state the prompt says to store; for memory-only tools, confirm that temporary content is discarded as specified. Record actual results and remaining limitations. A detailed plan alone does not establish a working replacement.