prod-page-audit
Run a production readiness audit on a web page or site and fix the gaps it finds — covering SEO, favicon, Open Graph / social previews, and mobile optimization. Use whenever the user asks for a production check, launch checklist, SEO or OG audit, mobile readiness check, mentions going live, or asks about favicon, meta tags, social previews, or viewport issues.
glrodasz · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add glrodasz/dotfiles --skill prod-page-audit技能说明
name: prod-page-audit description: > Run a production readiness audit on a web page or site and fix the gaps it finds — covering SEO, favicon, Open Graph / social previews, and mobile optimization. Use whenever the user asks for a production check, launch checklist, SEO or OG audit, mobile readiness check, mentions going live, or asks about favicon, meta tags, social previews, or viewport issues.
Production Page Audit
Audit + auto-fix workflow for web pages before they go to production. Don't restructure
HTML blindly, and don't generate robots.txt or sitemap.xml unless asked.
| Area | What's checked | Auto-fix? |
|---|---|---|
| SEO | Title, description, semantic HTML, canonical, robots | Fix meta; flag structural issues |
| Favicon | Presence, sizes, formats, manifest | Generate if missing |
| Open Graph | og: tags, Twitter Card, image dimensions | Generate OG image if missing |
| Mobile | Viewport, font sizes, input zoom, touch targets | Fix in-place where possible |
Phase 0 — Understand the target
- Input type: file path / project directory → read source directly; URL → fetch or ask for the HTML.
- Page type: landing, blog post, product, portfolio — determines what the OG image and favicon should look like.
- Brand context: colors, logo, name — pull from CSS variables,
<meta>, or ask.
If ambiguous, ask one focused question before proceeding.
Phase 1 — SEO
For each item in Phases 1–4, record the file path, current state, and verdict (✅/⚠️/❌).
If a11y-page-audit already ran on this page, skip the landmarks, single <h1>, alt
and lang checks below and report them as covered there.
Check:
<title>: exists, 50–60 chars, descriptive and unique<meta name="description">: exists, 120–160 chars, action-oriented<link rel="canonical">present;<meta name="robots">not accidentallynoindex- Single
<h1>, logical heading nesting - Images have meaningful
alt; links have descriptive text (not "click here") - Landmarks:
<header>,<main>,<footer>,<nav>,<article>/<section>where appropriate <html lang="...">set- JSON-LD structured data if applicable (article, product, local business)
Fix: add/rewrite title, description, canonical, and lang inline. Add missing alt
with descriptive placeholders marked <!-- TODO: update alt -->. Flag structural issues
(heading hierarchy, missing <main>) with a TODO comment and suggested fix — don't
restructure HTML blindly.
Phase 2 — Favicon
Check: <link rel="icon"> exists; sizes 16/32 (ICO or PNG), 180 (apple-touch-icon),
192 + 512 (PWA manifest); <link rel="manifest"> if PWA icons expected; SVG favicon for
modern browsers.
Fix if missing:
- Extract brand identity: primary color from CSS custom properties or dominant styles;
initials from
<title>/og:site_name; any existing logo SVG. - Generate an SVG favicon — brand initial(s) on a rounded rect in the primary color.
- Save as
favicon.svg; render the PNG sizes from it and pack 16/32/48 intofavicon.ico. Node projects: sharp for the PNGs,png-to-icofor the ICO (sharp can't write ICO). Python projects: Pillow for both (img.save("favicon.ico", sizes=[(16, 16), (32, 32), (48, 48)])). If neither is installed, note conversion is a build-time step. - Inject the standard
<head>links: SVG icon, 32×32 PNG, apple-touch-icon, manifest. - Generate
site.webmanifestif missing (name, short_name, 192/512 icons, theme/background color,display: standalone).
Phase 3 — Open Graph & social previews
Check: og:title, og:description, og:image (absolute URL, 1200×630), og:url
(canonical), og:type, og:site_name; Twitter Card tags (twitter:card,
twitter:title, twitter:description, twitter:image).
Fix if missing: derive basic OG tags from existing meta content. If og:image is
missing or placeholder, generate one:
- Pick the source by page type: article → hero image; product → product image; landing/portfolio → generate a branded card.
- Generate at 1200×630 with ~60px safe-zone padding: brand background, logo, title (max 2 lines), subtitle, site name/URL in a corner. Render with sharp + resvg in Node projects or Pillow in Python projects; fall back to an HTML template screenshot at build time only when neither is installed.
- Save under
/public/og/and injectog:image(+ width/height) andtwitter:card: summary_large_image.
Phase 4 — Mobile
Check:
<meta name="viewport" content="width=device-width, initial-scale=1">— and nouser-scalable=no/maximum-scale=1(accessibility violation)- All
<input>/<select>/<textarea>havefont-size≥ 16px — iOS Safari zooms on focus below that; the most common overlooked issue - No fixed widths wider than the viewport; images
max-width: 100%; no horizontal scroll at 375px @mediacoverage: ≤640px and ≤1024px if the layout is complex- Touch targets ≥ 44×44px with ≥ 8px gaps
- Typography: base ≥ 16px, line-height ≥ 1.5, nothing below 12px
- Performance (flag, don't fix): image
width/heightattributes (CLS),loading="lazy"below the fold,defer/asyncon scripts
Fix: add/correct the viewport meta; add
input, select, textarea { font-size: max(16px, 1rem); } if missing; add missing
max-width: 100% on images; flag touch-target issues with specific selectors and
suggested fixes.
Phase 5 — Verify
- Re-run the Phase 1–4 checks against the modified files; every item that was ❌ is now ✅ or explicitly listed under "Still needs human attention".
- The
<head>still parses: no duplicate<title>/og:*tags, every injected<link>points at a file that exists. - When a URL or dev server is available, run Lighthouse (it emulates a mobile device by default) and an OG preview check; treat the scores as a regression catch, not the verdict. Lighthouse needs Chrome; without it, list the check under "Still