smithery.ai

shipany-page-builder

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

First seen Mar 23, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,487 B
  • docs SUMMARY.md 113 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

ShipAny Page Builder (Dynamic Pages)

This skill creates new pages using ShipAny's dynamic page builder approach: a page is rendered from a JSON file (per-locale), and activated by registering that JSON path in localeMessagesPaths.

This skill is intentionally much simpler than shipany-quick-start: it only creates new dynamic pages.

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)

  • Update src/config/locale/index.ts:

- Append new 'pages/<slug>' entry to localeMessagesPaths (do not duplicate)

Hard rules:

  • 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.

Dev workflow (required)

  • Before starting: Ensure project skeleton is available
  • Before starting: Verify route/slug parameters are normalized
  • After finishing:

- Clear Next.js cache: rm -rf .next - Run pnpm build to validate (ensure no errors) - Verify new page is accessible

Inputs (normalize first)

Normalize 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)
  • 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
  2. Generate locale files (based on configured localeNames) and register 'pages/<slug>':

- Use scripts/createdynamicpage.py

  1. Quick validation checklist: references/01-checklist.md
  2. Validate build (required):

- Build: pnpm build

Bundled script (recommended)

Use bundled script to create files + register message path:

  • scripts/createdynamicpage.py

It is intentionally conservative:

  • Creates missing folders
  • Refuses to overwrite unless --force
  • Adds TODO: markers for missing translations/content