Websites & apps · SKILL

Website Planning & Delivery

Plan, build and verify a public website, with a traceable release record and a rehearsed migration and recovery path.

Skill introduction

For owners and developers of personal and company websites. When building, redesigning or moving a site, use visitor goals, approved material, the repository and target environment to deliver visitor journeys, a site and maintenance records through prototypes, preview builds and a migration checklist.

How to verify the work

Rebuild the specified commit and try key journeys using a keyboard and a narrow screen. Once release is authorized, verify the production entry and version. In a migration, check old URLs and validate dynamic snapshots and the legacy Reader manifest in isolation.

When to hand it over

Give the maintainer or release owner the accepted build, tested and open items, and rollback evidence. Hold the affected migration or release if recovery evidence or authorization for the target environment is missing.

What to measure

Log time to trace a comparable update from commit to production, plus broken links and recovery gaps found in rehearsals.

What it does

Plan around visitors’ tasks and verify pages, builds, deployment and migration in layers.

What it helps with

Trace each release to its version and identify old URLs and dynamic data before moving.

Why it matters

Preserve evidence for maintenance and recovery when a site changes teams, moves or is rebuilt.

PDF · Chinese

Guide

Core guidance, examples and a revision worksheet. PDF in Chinese.

V1.4 · 23 pages · 335 KB

Usage guide

For public websites run by individuals, companies or organizations. Use verified material to plan visitor journeys, sections and editing workflows. Verify build, interactions and deployment separately, including legacy URLs, data at the original browser origin, independent dynamic objects and older Reader manifests.

What to prepare

  • Site objectives, audience, content scope and verifiable material
  • Existing repositories, pages, assets, technology and authorized publication scope
  • The intended commit, build and deployment records, and target environment

What you receive

  • Information architecture, working pages and maintainable delivery
  • A verification record connecting code, builds, deployment and live behavior
  • Tested and untested scope, rollback evidence and maintenance handover
  • Website-side contracts and client integration records
  • Migration inventory, backup expiry and evidence from an isolated recovery rehearsal

Who it is for

  • Planning, developing or handing over personal, corporate and organizational sites
  • Checking whether an intended PR or commit actually runs in production
  • Connecting localization, content management and authorized publication
  • Migrating a site while preserving URLs, dynamic data and client compatibility

How the work progresses

  1. 01

    Confirm objectives, source material and the working baseline

  2. 02

    Implement content and visitor journeys as real pages

  3. 03

    Set page experience budgets and test keyboard use, narrow screens, network usage and interactions.

  4. 04

    Verify production versions, key assets and handover

  5. 05

    Check stable IDs, revisions/hashes of original UTF-8 body bytes, requested locale and actual text language. Treat richText as optional enhancement and retain the blocks compatibility path.

  6. 06

    Rehearse migration and recovery in an isolated environment; verify dynamic snapshots and older Reader manifests.

Getting started

Download and extract the complete ZIP. Read the README if included, or start with SKILL.md. Install the complete folder containing SKILL.md in your AI tool’s skills directory under the skill name. In a multi-version repository, choose the version you need and retain its supporting files. Try a small task with the required inputs and review the result.

Scope and limits

  • A passing build, merged PR or successful upload alone does not establish that production pages have changed.
  • The public package is a reviewed method snapshot without the original private Git history. Account, DNS and publication permissions remain project-specific.
  • The source is Chinese; seven-language website descriptions do not imply multilingual installation packages.
  • Verify installed-client support for each field independently. Public APIs carry only material approved for public release.
  • This Skill owns website-side content/APIs, versions, publication, compatibility contracts and client integration checks. Native UI, client cache implementation and device delivery belong to the separate App Planning & Delivery Skill.
  • The Chinese manual is V1.4. The source download still points to a separately identified public commit.

Updates for this Skill

Back to My Skills All updates
SEARCH