# Lp Site Upgrade > Build website-upgrade strategy in three layers: (1) periodic platform capability baseline, (2) per-business upgrade brief from reference sites, and (3) lp-do-fact-find handoff packet for prioritized implementation backlog. Use when upgrading an existing site by synthesizing best-of patterns with platform-fit constraints. - Skill: `majiayu000/lp-site-upgrade` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds add majiayu000/lp-site-upgrade` - Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/lp-site-upgrade/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Product & Planning - Author: majiayu000 (https://skillmd.com/u/majiayu000) - Updated: 2026-09-09 - Page: https://skillmd.com/skills/majiayu000/lp-site-upgrade --- # Site Upgrade Best Of Use this skill when you want to upgrade an existing site using reference websites while staying grounded in current platform capability and business outcomes. ## Invocation ```bash /lp-site-upgrade --mode=platform-baseline /lp-site-upgrade --mode=platform-baseline --baseline-max-age-days=30 /lp-site-upgrade --biz=HEAD --existing-site=https://example.com --reference-sites="siteA.com,siteB.com" /lp-site-upgrade --biz=PET --launch-surface=pre-website --brief-max-age-days=21 ``` Defaults: - `mode=business-brief` unless explicitly set to `platform-baseline` - `baseline-max-age-days=30` - `brief-max-age-days=21` - `launch-surface=website-live` unless site is not launch-ready - `WEBSITE-02` first cycle is treated as **L1 Build 2** (auto-mode contract below) ## Canonical Artifacts Platform baseline: - `docs/business-os/platform-capability/latest.user.md` - `docs/business-os/platform-capability/-platform-capability-baseline.user.md` - `docs/business-os/platform-capability/-platform-capability-baseline.user.html` - template: - `docs/business-os/platform-capability/_templates/deep-research-platform-capability-baseline-prompt.md` - `docs/business-os/platform-capability/_templates/platform-capability-baseline-template.user.md` Business upgrade brief: - `docs/business-os/site-upgrades//latest.user.md` - `docs/business-os/site-upgrades//-upgrade-brief.user.md` - `docs/business-os/site-upgrades//-upgrade-brief.user.html` - template: - `docs/business-os/site-upgrades/_templates/deep-research-business-upgrade-prompt.md` - `docs/business-os/site-upgrades/_templates/site-upgrade-brief-template.user.md` ## Workflow ### Stage 1: Select Mode - `platform-baseline`: periodic platform capability refresh. - `business-brief`: per-business best-of synthesis for website upgrade. ### Stage 2A: Platform Baseline Mode 1. Check `docs/business-os/platform-capability/latest.user.md`. 2. Treat baseline as stale if: - file missing, - `Status` is not `Active`, or - `Last-reviewed` older than `baseline-max-age-days`. 3. If stale, present a fully filled Deep Research prompt using: - `docs/business-os/platform-capability/_templates/deep-research-platform-capability-baseline-prompt.md` 4. Pause until Deep Research output is provided. 5. Save baseline doc to: - `docs/business-os/platform-capability/-platform-capability-baseline.user.md` 6. Update `latest.user.md` to point to the new baseline and set `Status: Active`. 7. Render HTML companions (required): - `pnpm docs:render-user-html -- docs/business-os/platform-capability/-platform-capability-baseline.user.md docs/business-os/platform-capability/latest.user.md` ### Stage 2B: Business Brief Mode 1. Require active platform baseline first. 2. Determine WEBSITE-02 phase: - If `launch-surface=website-live` and no dated upgrade brief exists for the business, classify as `L1 Build 2`. 3. Apply **Image-First Merchandising Auto-Mode** when either is true: - `L1 Build 2` and catalog is visual-first physical product. - category cues indicate bags/fashion/accessories/footwear/jewelry/beauty, or launch assortment is high-variant (about 40+ SKUs/variants). In this mode, require world-class exemplar analysis and shot-board outputs (see Output Contract). 4. Check business brief pointer at: - `docs/business-os/site-upgrades//latest.user.md` 5. Treat brief as stale if: - file missing, - `Status` is not `Active`, or - `Last-reviewed` older than `brief-max-age-days`, or - reference-site list changed materially. 6. If stale/missing, present a fully filled Deep Research prompt using: - `docs/business-os/site-upgrades/_templates/deep-research-business-upgrade-prompt.md` 7. Pause until Deep Research output is provided. 8. Save output to: - `docs/business-os/site-upgrades//-upgrade-brief.user.md` 9. Update `docs/business-os/site-upgrades//latest.user.md` to `Status: Active`. 10. Render HTML companions (required): - `pnpm docs:render-user-html -- docs/business-os/site-upgrades//-upgrade-brief.user.md docs/business-os/site-upgrades//latest.user.md` ### Stage 3: Build Fact-Find Handoff Packet From the business brief, produce a lp-do-fact-find-ready packet in the same brief (or a linked addendum) containing: - outcome frame and decision links - best-of synthesis matrix (`Adopt/Adapt/Defer/Reject`) - prioritized backlog candidates with acceptance criteria - dependencies and open questions - source evidence pointers Then hand off to `/lp-do-fact-find` for formal planning brief generation and task seeding. ## Prompt Presentation Rules (Required) When baseline/brief is stale or missing, output must include: 1. exact reason for block 2. exact template path 3. fully filled copy-paste prompt block for Deep Research 4. exact save path for returned output 5. explicit mode declaration: `L1 Build 2` or `post-Build 2`, plus whether Image-First Merchandising Auto-Mode is active ## Quality Rules 1. Never jump straight from reference site names to build tasks without platform baseline and business brief. 2. Do not copy proprietary creative/assets from reference sites. 3. Every backlog candidate must map to a business outcome. 4. Each P1/P2 candidate must include acceptance criteria and evidence refs. 5. If confidence is low on a claim, mark it explicitly and attach a validation test. 6. In Image-First Merchandising Auto-Mode, never ship generic visual advice; require measurable media contracts for homepage, PLP, PDP, and mobile gallery behavior. 7. For any customer-facing website build or upgrade, include a legal/compliance baseline in the brief or handoff packet: required policy pages for the business model/jurisdictions, disclosed business identity/contact surface, consent-management surface for non-essential tracking, and storefront promise-copy alignment against those policies. ## Output Contract ### Platform baseline output Must include: - capability matrix - delivery constraints - gaps register - preferred patterns and anti-patterns - adopt/adapt/defer/reject scoring rubric - freshness contract ### Business brief output Must include: - existing site baseline - reference-site pattern decomposition - best-of synthesis matrix - exemplar image shot-board (required when Image-First Merchandising Auto-Mode is active) - website and technical implications - legal/compliance website baseline when customer-facing commerce, lead capture, or tracking is present - image-heavy launch contract with measurable acceptance criteria (required when Image-First Merchandising Auto-Mode is active) - prioritized backlog candidates - open questions - source list ### Fact-find handoff packet Must include: - candidate backlog table with priority, rationale, acceptance criteria, dependencies - mapping from each item to outcome and decision link - unresolved decisions requiring user input - explicit legal/compliance backlog items when policy pages, consent management, business disclosure, or storefront-policy alignment are missing ## Red Flags (Invalid Run) 1. Marks brief ready without active platform baseline. 2. Produces build backlog without best-of synthesis matrix. 3. Lacks acceptance criteria on prioritized items. 4. Omits source evidence for competitor/reference claims. 5. Continues despite stale prerequisites without presenting Deep Research prompt. 6. Writes/updates `.user.md` artifacts but does not render matching `.user.html` companions. 7. Marks an L1 Build 2 brief complete for a visual-heavy catalog without exemplar shot-board and image-heavy launch contract sections.