How do I install the Shipany Quick Start skill?

Run npx skillmds add majiayu000/shipany-quick-start in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Shipany Quick Start safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Shipany Quick Start?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Shipany Quick Start free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Shipany Quick Start?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Shipany Quick Start by majiayu000 — Agent Skill

Name: Shipany Quick Start
Rating: 4.2 (5 reviews)
Author: majiayu000

Shipany Quick Start

Automate first-pass customization of a new ShipAny (ShipAny Two) project from a short project brief (app name, domain/app URL, product description/features, reference links, and branding preferences). Use when the user says they are starting a new project.

majiayu000 8739c36 2 files · 2.6 KB Updated Sep 9, 2026 567 repo stars

File contents

ShipAny Quick Start (Project Bootstrap)

This skill is intentionally split into small reference modules. Load only the module(s) you need.

v1 edit scope (hard limit)

For the first pass, only modify the files listed in references/09-checklist.md.

Do not change any other files (no routing, no components, no templates, no extra locale message files).
Do not introduce login/auth/payment features unless explicitly requested.

Dev workflow (required)

Before starting edits: run pnpm install (once) to ensure dependencies are installed.
After finishing all edits: clear Next.js cache before validation, otherwise you may see stale assets (e.g. old logo.png):
- macOS/Linux: rm -rf .next
- Windows (PowerShell): Remove-Item -Recurse -Force .next
- Windows (cmd): rmdir /s /q .next
Then run pnpm build to validate the project (build + lint checks). If it fails, fix issues only within the v1 allowlist unless the user expands scope.

Project brief

Normalize the user’s request first:

references/00-project-brief.md

Execution order (ShipAny Two)

App basics (env-driven): references/01-env-app-info.md
SEO metadata: references/02-seo-metadata.md
Landing page (EN/ZH): references/03-landing-page.md
- Page sections live in src/config/locale/messages/{locale}/pages/index.json
- Header/footer/nav live in src/config/locale/messages/{locale}/landing.json
Theme styles: references/04-theme-styles.md
Logo + favicon: references/05-logo-favicon.md
Sitemap: references/06-sitemap.md
Legal pages: references/07-legal-pages.md
Images (extract from links or use Picsum placeholders): references/08-images.md
Minimal checklist: references/09-checklist.md

Bundled script

scripts/fetch_og_image.py: Best-effort OG/Twitter preview image downloader for a reference link.

---name: shipany-quick-startdescription: Automate first-pass customization of a new ShipAny (ShipAny Two) project from a short project brief (app name, domain/app URL, product description/features, reference links, and branding preferences). Use when the user says they are starting a new project.--- # ShipAny Quick Start (Project Bootstrap) This skill is intentionally split into small reference modules. Load only the module(s) you need. ## v1 edit scope (hard limit) For the first pass, **only modify the files listed in** `references/09-checklist.md`. - Do **not** change any other files (no routing, no components, no templates, no extra locale message files). - Do **not** introduce login/auth/payment features unless explicitly requested. ## Dev workflow (required) - Before starting edits: run `pnpm install` (once) to ensure dependencies are installed. - After finishing all edits: **clear Next.js cache** before validation, otherwise you may see stale assets (e.g. old `logo.png`): - macOS/Linux: `rm -rf .next` - Windows (PowerShell): `Remove-Item -Recurse -Force .next` - Windows (cmd): `rmdir /s /q .next` - Then run `pnpm build` to validate the project (build + lint checks). If it fails, fix issues **only within the v1 allowlist** unless the user expands scope. ## Project brief Normalize the user’s request first: - `references/00-project-brief.md` ## Execution order (ShipAny Two) 1. App basics (env-driven): `references/01-env-app-info.md` 2. SEO metadata: `references/02-seo-metadata.md` 3. Landing page (EN/ZH): `references/03-landing-page.md` - Page sections live in `src/config/locale/messages/{locale}/pages/index.json` - Header/footer/nav live in `src/config/locale/messages/{locale}/landing.json` 4. Theme styles: `references/04-theme-styles.md` 5. Logo + favicon: `references/05-logo-favicon.md` 6. Sitemap: `references/06-sitemap.md` 7. Legal pages: `references/07-legal-pages.md` 8. Images (extract from links or use Picsum placeholders): `references/08-images.md` 9. Minimal checklist: `references/09-checklist.md` ## Bundled script - `scripts/fetch_og_image.py`: Best-effort OG/Twitter preview image downloader for a reference link.

Frequently asked questions