# Shipany Quick Start

> Shipany Quick Start is an Agent Skill for apps & automation published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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.

- Skill name: `shipany-quick-start`
- Category: [Apps & Automation](https://www.openparable.com/skill/apps-automation/1)
- Source: https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/development/shipany-quick-start/SKILL.md
- Repository: majiayu000/claude-skill-registry (498 GitHub stars when collected)

## SKILL.md

# 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`
10. Showcase gallery (optional): `references/10-showcase.md`

## i18n Development (CRITICAL)

**All server-side pages MUST use explicit locale in `getTranslations()` calls.**

See `.claude/skills/shipany-page-builder/references/04-i18n-best-practices.md` for the required pattern and examples.

## Bundled script

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

---

Source: https://www.openparable.com/skill/apps-automation/shipany-quick-start (OpenParable). Cite the canonical URL above.
