shipany-page-builder

majiayu000's avatarfrom majiayu000

Create new dynamic pages from a short spec (keywords, route/path, reference content).

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 5, 2026
[Ads and Landing Pages]

When & Why to Use This Skill

The ShipAny Page Builder is a specialized Claude skill designed to automate the creation of dynamic, multi-language landing pages. By converting brief specifications—such as keywords, routes, and reference content—into structured JSON configurations, it enables rapid web development and deployment. It features automated routing and scheduled publishing, making it an essential tool for scaling web content and executing programmatic SEO (pSEO) strategies without manual coding overhead.

Use Cases

  • Rapid Landing Page Generation: Quickly build and deploy new marketing or feature pages by providing only a short specification and desired route.
  • Programmatic SEO (pSEO): Scale your site's search footprint by generating and scheduling multiple keyword-targeted pages to go live at specific dates.
  • Multi-language Content Localization: Automatically create synchronized page versions in both English and Chinese (Simplified) to maintain global brand consistency.
  • Marketing Campaign Prototyping: Transform competitor reference copy or raw notes into structured page sections including Hero, Features, FAQs, and CTAs.
nameshipany-page-builder
descriptionCreate new dynamic pages from a short spec (keywords, route/path, reference content).

ShipAny Page Builder (Dynamic Pages)

This skill creates new pages using ShipAny’s evolved dynamic page builder approach: a page is rendered from a JSON file (per-locale).

KEY UPDATE: The system now supports Automated Routing.

  • NO need to register routes in index.ts.
  • NO need to run scripts.
  • Just create the JSON file, and it's live!

v1 edit scope (hard limit)

For v1, you may only:

  • Add new multi-language dynamic page JSON files:
    • src/config/locale/messages/en/pages/** (new page JSON files only)
    • src/config/locale/messages/zh/pages/** (new page JSON files only)

22: Hard rules:

  • Do not modify src/config/locale/index.ts (it is no longer needed).
  • Do not modify any existing page JSON files (only create new ones).
  • Do not touch routing code, layouts, components, or theme blocks.
  • Do not add or edit any images under public/. Use placeholder images in JSON only.

Inputs (normalize first)

Normalize the user request into:

  • route: string (e.g. /features/ai-image-generator)
  • slug: string (derived from route, e.g. features/ai-image-generator)
  • keywords: string[] (3–10)
  • publishedAt: optional string (ISO 8601) for Scheduled Publishing (pSEO strategies).
  • referenceCopy: optional raw text snippets, bullets, competitor copy, or notes
  • sectionsWanted: optional list of section keys (default: ["hero","introduce","benefits","features","faq","cta"])

See references/00-guide.md.

Execution order

  1. Normalize input + decide route/slug: references/00-guide.md
    • MUST consult references/02-block-specs.md for JSON block schemas.
  2. Generate locale files directly:
    • Create src/config/locale/messages/en/pages/<slug>.json
    • Create src/config/locale/messages/zh/pages/<slug>.json
  3. (Optional) Set publishedAt in metadata if user requested a scheduled release.
  4. Validate build (required):
    • Build: pnpm build

Scheduled Publishing (pSEO)

You can now schedule pages to go live in the future.

{
  "metadata": {
    "title": "Future Page",
    "publishedAt": "2025-12-31T12:00:00Z" // Page returns 404 until this time
  },
  "page": { ... }
}