Import Prompt

Prompt for porting an existing SvelteKit site into a fresh cagiikit clone. Swap the old project path before running.

Port an Old Site

This is a fresh clone of cagiikit. Port the site at
/Users/zoonix/code/fapoh-bak into it. Both projects are SvelteKit.

Goal: the rendered site should be identical to the old one — same copy, same design, same routes — but built entirely with this starter kit's patterns. No redesign, no copy edits, no improvements.

STEP 1 — Learn this repo.
Read CLAUDE.md/README, then read enough code to write CONVENTIONS.md: a short doc covering how this kit does routing, layouts, components, state, data loading, styling, images, and SEO/meta, with a pointer to a representative file for each. Do not open the old project until it's written.

STOP. Show me CONVENTIONS.md and wait for my approval before continuing.

STEP 2 — Inventory the old project.
Every route, page, layout, component, content source, form, and asset. Write PORT-PLAN.md as an old → new checklist, noting for each item which convention from CONVENTIONS.md it maps to.

STOP. Show me PORT-PLAN.md and wait for my approval before writing any code.

STEP 3 — Port in checklist order.
Global layout and styles, then shared components, then pages. Tick items off in PORT-PLAN.md as you go.

RULES
- Copy and content are verbatim. Implementation is rewritten to match this repo.
- Conflicts: on HOW something is built, new wins. On WHAT is displayed, old wins.
- Both projects are SvelteKit, so file-copying will often "work." Don't. Every ported file gets rewritten against CONVENTIONS.md. The only things copied verbatim are copy text, content data, and static assets.
- Flag and convert any old pattern this kit has moved on from — stores vs runes, old load signatures, deprecated component APIs.
- Don't carry over the old package.json. Add dependencies to this one only when a ported feature actually needs it.
- If the old project uses a dependency this kit solves natively, drop it.
- Preserve URLs and slugs exactly. Port titles, meta descriptions, OG tags, and structured data as-is.
- Run images through this kit's pipeline, not the old approach.
- Don't port code whose purpose you can't explain — flag it in PORT-PLAN.md instead.
- Don't ask me about content, wording, or design — the old site is the answer. Only stop for real ambiguity in the new patterns, or for things that are broken or dead in the old site.

WHEN DONE
Run the build, fix errors, then give me the route list to spot-check against the old site.

Notes

The two hard STOP gates are what keep this from turning into an unreviewable diff — approval of CONVENTIONS.md before the old project is opened, and of PORT-PLAN.md before any code is written.

Writing CONVENTIONS.md before looking at the old project is deliberate: it stops the old codebase's patterns from leaking into the description of the new one.