Build new localized web pages by creating simple JSON configuration files.
Install
mkdir -p .claude/skills/shipany-page-builder && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14219" && unzip -o skill.zip -d .claude/skills/shipany-page-builder && rm skill.zipInstalls to .claude/skills/shipany-page-builder
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Create new dynamic pages from a short spec (keywords, route/path, reference content).Key capabilities
- →Create new dynamic pages by generating JSON configuration files
- →Support multi-language dynamic page JSON files
- →Enable automated routing for new pages without manual registration
- →Set `publishedAt` metadata for scheduled page publishing
- →Validate the build after creating new page files
How it works
The skill creates new dynamic pages by generating JSON configuration files for specific routes, which are then rendered by the ShipAny system with automated routing.
Inputs & outputs
When to use shipany-page-builder
- →Launch a new feature landing page
- →Create a localized page version
- →Add a new marketing page
- →Publish a new FAQ section
About this skill
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 notessectionsWanted: optional list of section keys (default:["hero","introduce","benefits","features","faq","cta"])
See references/00-guide.md.
Execution order
- Normalize input + decide route/slug:
references/00-guide.md- MUST consult
references/02-block-specs.mdfor JSON block schemas.
- MUST consult
- Generate locale files directly:
- Create
src/config/locale/messages/en/pages/<slug>.json - Create
src/config/locale/messages/zh/pages/<slug>.json
- Create
- (Optional) Set
publishedAtin metadata if user requested a scheduled release. - Validate build (required):
- Build:
pnpm build
- 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": { ... }
}
When not to use it
- →When modifying existing page JSON files
- →When changing routing code, layouts, components, or theme blocks
- →When adding or editing images under `public/`
Limitations
- →The skill is limited to adding new dynamic page JSON files
- →The skill does not allow modification of existing page JSON files
- →The skill prohibits touching routing code, layouts, components, or theme blocks
How it compares
This skill enables dynamic page creation through JSON configuration and automated routing, eliminating the need for manual route registration or code modifications for each new page.
Compared to similar skills
shipany-page-builder side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| shipany-page-builder (this skill) | 0 | 5mo | Review | Beginner |
| payload | 73 | 2mo | Review | Intermediate |
| ssr-hydration-scraping | 0 | 4mo | No flags | Intermediate |
| nuqs | 0 | 5mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
payload
payloadcms
Use when working with Payload CMS projects (payload.config.ts, collections, fields, hooks, access control, Payload API). Use when debugging validation errors, security issues, relationship queries, transactions, or hook behavior.
ssr-hydration-scraping
Project-N-E-K-O
Best practices for extracting data from modern React/Vue SSR pages (like Next.js or Nuxt.js) by targeting hydration state blocks (__NEXT_DATA__, __NUXT__) using regex and `jmespath`, avoiding brittle DOM selector scraping.
nuqs
fellipeutaka
>
generate
Sophiasuu
Generate one static framework page per entity using the appropriate Sophon adapter. Supports Next.js, Astro, Nuxt, SvelteKit, and Remix. Use when the user wants to scaffold programmatic SEO pages.
publish-weekly
miantiao-me
使用 Payload REST API 将周刊写入 CMS(发布为草稿),通过 users API Key 认证。
docs
matteocervelli
Build and publish project documentation — Starlight (Astro) for apps, markdown for libraries/services, with IT+EN i18n and VPS deploy. Use when writing user guides, scaffolding a docs site, or publishing docs. Trigger on "write docs", "documentation site", "user guide", "publish docs".