Communitygithub.com

Launch-QA

Führe eine Pre-Launch-Qualitätsprüfung einer Website durch, die Performance, Barrierefreiheit, SEO-Grundlagen, Formulare, geräteübergreifendes Verhalten und Inhalte abdeckt, und melde die Ergebnisse nach Schweregrad sortiert mit Lösungen.

Was ist Launch-QA?

Launch-QA ist ein Skill, der eine umfassende, automatisierte Qualitätsprüfung vor dem Start einer Website durchführt. Er deckt Performance, Barrierefreiheit, SEO, Funktionalität, geräteübergreifendes Verhalten und Sicherheit ab. Der Skill priorisiert Ergebnisse nach Schweregrad (Blocker, Sollte behoben werden, Kosmetik) und liefert klare, umsetzbare Lösungen. Er unterstützt sowohl Live-URLs als auch lokale Build-Ordner durch Integration mit dem `webcraft`-CLI-Tool oder dem `audit_site` MCP-Tool. Der generierte Bericht folgt einer strukturierten Vorlage mit einer direkt einschbaren Bewertung (Bereit / Bereit nach Behebung von Blockern / Nicht bereit). Der Skill ist ideal für Entwickler und QA-Teams, die sicherstellen möchten, dass eine Website kurz vor dem Launch die grundlegenden Standards erfüllt und keine kritischen Probleme aufweist.

Funktioniert mit~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/imperfec-t/webcraft/tree/HEAD/skills/launch-qa

In Ihrer bevorzugten KI fragen

Öffnet einen neuen Chat, in dem dieser Agent-Skill bereits geladen ist.

Dokumentation

Launch QA

Find what will embarrass the owner or cost them enquiries, rank it, and say how to fix it. A list of forty equal-weight nitpicks is not useful; three blockers and a short tail is.

How to run it

  1. Establish what you can inspect: live URL, source files, or both. Say which checks you could not perform (for example, real-device testing or form delivery) instead of marking them passed.

  2. If the webcraft CLI is available, run it first for the measurable checks (or call the audit_site MCP tool):

    webcraft audit https://example.com --pages 10     # live site: also robots, sitemap, redirects, 404, links
    webcraft audit ./dist                             # local build folder
    webcraft audit ./dist --json --fail-on blocker    # CI: exit 1 on blockers
    

    It produces the report template below with a "Not checked" list. Verify surprising findings before repeating them, then spend your own effort on what it cannot see: rendering, keyboard use, real devices, content accuracy.

  3. Work through the areas below. Prefer measurement to opinion: run the page, read the markup, count the bytes.

  4. Classify each finding:

    • Blocker: broken functionality, inaccessible core content, form that does not deliver, wrong or placeholder content, site not indexable when it should be.
    • Should fix: measurable harm to speed, accessibility or search appearance.
    • Polish: minor inconsistencies.
  5. Report with the template at the end.

Functionality and content

  • Every link and button goes somewhere real. No #, no lorem ipsum, no template leftovers, no test email addresses.
  • Forms: required validation, clear error messages, success state, spam protection, and a real test submission that arrives in the right inbox.
  • Phone numbers use tel:, emails use mailto:, and they are the correct ones (check for mismatched numbers between header and footer).
  • 404 page exists and links home.
  • Legal pages present where needed: privacy policy, terms, cookie notice if tracking is used.
  • Copyright year and business details are current and consistent.

Performance

Targets on a mid-range phone over 4G: LCP under 2.5s, INP under 200ms, CLS under 0.1.

  • Images: modern format (WebP or AVIF), sized to their display size, width and height set, loading="lazy" below the fold, and the LCP image preloaded and not lazy.
  • Video: poster image, no autoplay with sound, compressed, not loaded on small screens if decorative.
  • Fonts: at most two families, font-display: swap, preload the above-the-fold files.
  • CSS and JS: minified, deferred where possible, no unused libraries (a slider library loaded for one static image is common).
  • Third-party scripts: each one justified. Chat widgets and trackers are frequent LCP and INP offenders.
  • Caching and compression enabled on the server.

Accessibility

  • One h1; heading levels do not skip.
  • All meaningful images have alt text; decorative ones have empty alt="".
  • Text contrast at least 4.5:1 (3:1 for large text). Check text over images and muted grey text first.
  • Everything works by keyboard: visible focus ring, logical order, menus and accordions operable, no focus trap.
  • Form fields have associated <label> elements; errors are announced, not shown by color alone.
  • prefers-reduced-motion respected; nothing flashes; autoplaying motion can be paused.
  • lang attribute on <html>; page works at 200% zoom.

SEO basics

  • Unique <title> (50 to 60 characters) and meta description (around 150) per page.
  • Canonical URL set; one version of the domain (https, with or without www) redirecting the others.
  • robots.txt not blocking the site, no stray noindex from staging, XML sitemap present.
  • Open Graph title, description and image (1200 by 630, served over https) so shared links look right.
  • Structured data where it fits (Organization or LocalBusiness, FAQ, Article) and valid.
  • Descriptive link text rather than "click here"; clean URLs.

Cross-device

  • Widths 320, 390, 768, 1024, 1440: no horizontal scroll, no overlapping text, tap targets at least 44px.
  • Current Chrome, Safari, Firefox and Edge; iOS Safari specifically for vh units, sticky positioning and video autoplay.
  • Animations do not hide content if JavaScript fails.

Security and operations

  • HTTPS everywhere, no mixed content.
  • CMS, theme and plugins updated; unused plugins and themes removed; no default admin username.
  • Backups scheduled and one restore tested.
  • Analytics and search console connected, with consent handling where required.
  • Favicon and touch icon present.

Report template

# Launch QA: [site]   Checked: [date]   Scope: [what was and was not inspected]

Verdict: Ready / Ready after blockers / Not ready

## Blockers
1. [What is wrong] — [where] — [fix]

## Should fix
...

## Polish
...

## Not checked
- [Check] — [why, and how the owner can check it]

Keep each finding to one line of problem, one of location, one of fix. Lead with the verdict so the owner knows immediately where they stand.

Individual skills in this repo

This repo contains 8 individual skills — each has its own dedicated page.

design-tokens

Create a website's visual system as CSS custom properties, covering color palette, typography scale, spacing, radius and shadows, with contrast checked. Use this whenever someone asks for a color scheme, a palette from one brand color, font pairing, a type scale, "make it look consistent", dark mode, a rebrand of an existing site into new colors, or starts a build with no defined styles.

hero-section

Design and build the hero (first screen) of a website, including headline layout, media treatment, CTA, proof badge, marquee and entrance animation. Use this whenever someone asks for a hero section, a landing page header, "the top of my homepage", a cinematic or animated intro, a video background, a text marquee, or says their first screen looks plain or generic.

homepage-blueprint

Plan the section structure and content slots of a homepage for an agency, freelancer, studio or service business before any design or code. Use this whenever someone asks "what sections should my homepage have", "plan my website", "structure a landing page for my business", wants a wireframe or sitemap for a service site, or starts building a homepage without a clear outline.

responsive-layout

Build page layouts that work from phones to wide desktops using CSS grid, flexbox, container queries and fluid sizing, including card grids, bento grids, split sections, sticky sidebars and navigation that collapses. Use this whenever someone says their site "breaks on mobile", asks for a responsive grid, a bento layout, a mobile menu, fixing horizontal scroll or overflow, or is laying out any multi-column section.

scroll-motion

Add scroll-driven and entrance animation to a website with GSAP, ScrollTrigger and Lenis, including reveals, parallax, pinned sections, horizontal scroll, line drawing, counters and preloaders. Use this whenever someone wants a site to "feel premium", asks for smooth scrolling, scroll animations, parallax, text reveals, a pinned or sticky scroll section, an animated preloader, or names GSAP, ScrollTrigger, Lenis, Locomotive or AOS.

site-teardown

Analyze a live website and turn it into a section-by-section build brief that another person or AI can rebuild from, with brand name, colors, fonts and images swapped for placeholders. Use this whenever someone shares a URL and says "analyze this site", "make something like this", "give me a prompt to build this", "recreate this effect", "clone the layout with my branding", or asks how a page's animation or structure works, even if they never say "teardown".

website-workflow

Plan and sequence a whole website build, from structure through design, code, WordPress and launch, by routing each stage to the right webcraft skill. Use this when someone asks to "build me a website", "design my site from scratch", "redo our homepage", wants an end-to-end plan for a marketing, agency, studio or service site, or the request spans more than one of structure, look, layout, motion, CMS and QA.

wordpress-theme-build

Turn a static HTML/CSS/JS design into a custom WordPress theme that the client can edit, covering theme structure, theme.json, enqueueing scripts, block patterns, custom post types and editable content. Use this whenever someone wants to convert a design or static site to WordPress, build a custom or block theme, make sections editable in Gutenberg, add GSAP or other scripts to a theme properly, or asks why their theme edits are lost or their content is hard-coded.

Verwandte Skills