gormes-landing-web

name	gormes-landing-web
description	Use when the user asks to audit, redesign, polish, rewrite, or periodically improve the www.gormes.ai landing page, homepage UI, visual hierarchy, install flow, public trust signals, or conversion copy from current Gormes evidence.

Gormes Landing Web

Repository Branch Rule

For Gormes work, stay on the existing development branch. Do not create or use feature branches, short-lived branches, or git worktrees. If the checkout is not on development, stop before editing and switch safely or report the blocker.

Mission

Keep www.gormes.ai clear, accurate, and usable for strangers. This skill is for landing-page content and UI passes, not runtime feature implementation or roadmap invention.

Source Files

• webpages/landing/src/data/landing.js - landing copy, CTAs, links, proof, and progress/benchmark projection.
• webpages/landing/src/pages/index.astro - HTML structure, metadata, and bounded copy-button behavior.
• webpages/landing/src/styles/global.css - Tailwind import, theme, and base states.
• webpages/landing/public/static/ - favicon, social-card, and landing visual assets.
• webpages/landing/scripts/sync-assets.mjs - canonical installer/static asset mirror used before dev/build.
• webpages/landing/tests/home.spec.mjs - Playwright homepage expectations.
• webpages/landing/legacy/go-renderer/ - deprecated former Go-rendered site; retained for reference/rollback only and excluded from active Astro builds, asset sync, and progress mirror generation.
• benchmarks.json and webpages/docs/content/building-gormes/architecture_plan/progress.json - canonical proof inputs.

Workflow

1. Bound The Pass

State whether the pass is about:

• hero and first viewport;
• install and model-backed quick start;
• "what works today" and current limits;
• proof/trust signals;
• visual hierarchy, spacing, responsive layout, or accessibility;
• stale Hermes/Goncho/Honcho wording;
• progress, benchmark, or release status.

If the change would require runtime behavior that is not shipped, route through gormes-skill-manager instead of promising it on the landing page.

2. Gather Evidence

Start with:

git status --short
sed -n '1,220p' webpages/landing/README.md
sed -n '1,260p' webpages/landing/src/data/landing.js
sed -n '1,260p' webpages/landing/src/pages/index.astro
go run ./cmd/progress validate
rg -n "Hermes|backend|install|doctor|offline|oneshot|Goncho|No Python|progress|benchmark|production" README.md webpages/docs webpages/landing

Use current code, tests, generated progress, and benchmarks as the source of truth. Do not invent performance, release, or production-readiness claims.

3. Apply The Landing Lens

For broad audits, rewrites, or UI polish, read references/landing-quality-rubric.md. Prioritize a first-time visitor who needs to understand what Gormes is, why it matters, what works today, how to try it, and why the claims are trustworthy.

4. Edit In Scope

Prefer direct edits to the active Astro + Tailwind site:

• copy and link data in src/data/landing.js;
• page structure in src/pages/index.astro;
• presentation through Tailwind utility classes and src/styles/global.css;
• installer/progress/static mirroring in scripts/sync-assets.mjs;
• Playwright assertions in tests/home.spec.mjs when user-facing behavior changes.

Keep the page fast, static-exportable, and readable without client-side JavaScript except the existing bounded install-copy behavior. Do not add new work to legacy/go-renderer/, and do not wire build/sync/progress generation back into it, unless the old renderer is explicitly restored.

5. Validate

Run focused checks:

(cd webpages/landing && npm run build)
(cd webpages/landing && npm run test:e2e)
go run ./cmd/progress validate

If progress or benchmark data changed, also run the repo tool that refreshes the embedded data or rebuilds the site. For UI layout work, inspect desktop and mobile Playwright output or screenshots before reporting done.

Final Report

Report:

1. Landing surfaces checked
2. Evidence used
3. Content/UI changes made
4. Claims kept conservative
5. Validation run
6. Remaining landing-page gaps