website-clone-final-report
Produce a before/after comparison report of a website clone project. Uses Phase 1 analysis as baseline and builder metadata as 'after' snapshot. Covers performance, SEO, security, UI/UX deltas, deviations, and GitHub Pages URL. Use when asked for a final report, before-after comparison, or project closure summary of a website clone. Don't use for ongoing monitoring or live site audits.
What this skill does
# Website Clone Final Report Produces a before/after comparison report closing the loop on a website clone project. Uses Phase 1 analysis as baseline and builder metadata as the "after" snapshot. ## When to Use Trigger when the user asks to: - Generate a final report for a website clone project - Compare before/after metrics of a site rebuild - Produce a project closure summary for a website improvement Do **not** use for ongoing monitoring or live site audits — those are separate activities. ## Workflow ``` 1. Read Phase 1 analysis (baseline) and builder metadata (after) 2. Read tasks.md for what was implemented 3. Read prd.md for what was planned 4. Compute before/after deltas per dimension 5. List deviations from the plan 6. Write final report 7. Present to user ``` ## Output: final-report.md Structure ```markdown # Final Report: <site name> Clone **Original URL:** <url> **New Site:** https://<user>.github.io/<repo>/ **Date:** <date> --- ## What Was Implemented A plain-language summary of what was built, drawn from tasks.md: "The improved website includes: - A redesigned landing page with a prominent CTA above the fold - Three additional pages: Features, About, and Contact - Performance optimizations including image compression and lazy loading - Full SEO implementation with structured data and meta tags" ## Before/After Comparison ### Performance | Metric | Before | After | Delta | |--------|--------|-------|-------| | LCP | 4.3s | 1.8s | -58% | | CLS | 0.18 | 0.03 | -83% | | TTFB | 0.8s | 0.2s | -75% | | Page Weight | 2.1 MB | 650 KB | -69% | | Requests | 87 | 32 | -63% | ### SEO | Dimension | Before | After | Delta | |-----------|--------|-------|-------| | Overall Score | 62/100 | 94/100 | +52% | | Meta Tags | 60 | 95 | +58% | | Heading Structure | 50 | 85 | +70% | | Alt Text Coverage | 30% | 100% | +233% | | Structured Data | 0 | 100 | +100% | ### Security | Check | Before | After | |-------|--------|-------| | HTTPS | Yes | Yes | | Security Headers | Partial | Strong | | Mixed Content | 2 issues | 0 issues | ### UI/UX Changes Plain-language description of UI/UX improvements: - **Hero section:** Restructured to put the CTA immediately above the fold. The original buried the sign-up button below two content sections. - **Navigation:** Simplified from 8 menu items to 5, removing low-value links. - **Mobile experience:** Completely redesigned for mobile with a hamburger menu and stacked layout. - **Visual hierarchy:** Improved contrast and spacing make the primary action 3x more prominent. ### Style Enhancements - Typography upgraded from generic system fonts to a modern paired font system - Color palette refined with better contrast ratios (WCAG AA compliant) - Spacing made more consistent and generous - Motion added sparingly for micro-interactions (button hover, scroll reveal) ## Deviations from Plan List any deviations from prd.md or tasks.md: | Planned | Actual | Reason | |---------|--------|--------| | 5 additional pages | 3 additional pages | Scope reduction requested | | Custom icon set | lucide-react icons | Time constraint | | Animated hero | Static hero with CSS fade-in | Performance priority | If no deviations, state: "No deviations from the approved plan." ## Summary A closing summary for non-technical stakeholders: "This website improvement project successfully addressed the key issues identified in the initial analysis. Performance improved by 58-83% across all metrics, SEO score increased from 62 to 94, and the user experience was significantly enhanced with a clearer visual hierarchy and better mobile support. The new site is live at the URL above." --- *This report was generated from the Phase 1 analysis baseline and builder metadata.* *All metrics are based on automated analysis and may not reflect actual user experience.* ``` ## Step 1: Read Inputs Read the analysis baseline and builder metadata: ``` Read file <path-to-analysis.json> Read file <path-to-builder-metadata.json> ``` Also read `tasks.md` for what was implemented and `prd.md` for what was planned: ``` Read file <path-to-tasks.md> Read file <path-to-prd.md> ``` If any input is missing, note it and proceed with what's available. ## Step 2: Compute Deltas Compare baseline metrics against builder metadata: | Metric | Source | Delta | |--------|--------|-------| | LCP, CLS, TTFB, page weight, requests | Phase 1 analysis vs. builder metadata | after - before | | SEO score, dimension scores | Phase 1 analysis vs. builder metadata | after - before | | Security checks | Phase 1 analysis vs. builder metadata | qualitative comparison | For UI/UX, describe changes based on the tasks.md implementation vs. the Phase 1 analysis. ## Step 3: Identify Deviations Compare tasks.md (what was planned) against what the builder actually delivered: - Tasks that weren't completed - Features implemented differently than specified - Assets that weren't collected or created as planned - Any scope changes ## Step 4: Write Draft Report Assemble the report using the structure above. ## Step 5: Present to User "Here is the final comparison report. Review it for completeness and accuracy." No approval gate is required for this phase — it's the last step and informational only. ## Step 6: Save Report Persist the assembled report using the Write tool — never `echo > path`, since markdown bodies routinely contain backticks, dollar signs, and backslashes that the shell would mangle. Default output path: `$PROJECT_DIR/final-report.md`, falling back to `~/workspace/clones/YYYY_MM_DD_slug/final-report.md` when no project dir is set. If `$ARGUMENTS` includes `--output <path>`, use that path verbatim. Confirm: ``` Final report saved to: <absolute-path> GitHub Pages URL: <url> ``` ## Error Handling | Failure | Behavior | |---|---| | No analysis input | Note missing baseline, proceed with qualitative comparison | | No builder metadata | Note missing after data, request builder metadata from orchestrator | | No tasks.md | Describe what was implemented based on available data only |
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".