cloning-websites-to-weaverse
Cloning Websites to Weaverse
Overview
Use this repo-specific workflow to turn a reference website into maintainable Weaverse pages. Optimize for reusable sections, accurate section matching, and clear schema boundaries, not one-off screenshot cloning.
Priority order: brand guideline beats source website on visual conflicts. The source website drives page structure, content flow, interaction patterns, and merchandising logic.
Conflict Rule
.guides/brand-guideline.md is the source of truth.
If the live site conflicts with the brand guideline, you MUST follow the brand guideline. This is mandatory even when:
- a stakeholder says
make it look like the live site - leadership will compare screenshots
- the live site appears newer or more polished
More from weaverse/shopify-hydrogen-skills
shopify-hydrogen
Core Shopify Hydrogen APIs — createHydrogenContext, cart handler, CartForm, caching strategies, pagination, SEO, variant selection, analytics, and CSP.
19hydrogen-cookbooks
Step-by-step implementation guides for building features in a Shopify Hydrogen storefront — bundles, combined listings, customer accounts, 3D models, performance, variant media, and Weaverse integration.
19hydrogen-upgrades
Step-by-step guides for upgrading Shopify Hydrogen between versions — breaking changes, code diffs, and migration steps for each release.
18theme-update
Safely update a Weaverse Pilot theme to the latest version — detects current version, fetches release diffs, plans changes category-by-category, preserves customizations, verifies build.
16weaverse-hydrogen
Build Shopify Hydrogen storefronts with Weaverse — components, schemas, loaders, theming, data fetching, React Router v7, deployment, and advanced features.
15weaverse-integration
Integrate Weaverse into an existing Shopify Hydrogen project — analyze codebase, convert existing components to Weaverse sections, set up SDK, configure routes, and preserve coding style. For projects not yet using Weaverse.
13