// Improve the www.gormes.ai landing page content, UI, visual hierarchy, install flow, and public trust signals from current Gormes evidence. Use when the user asks to audit, redesign, polish, rewrite, or periodically improve the Gormes landing page or homepage UI.
[HINT] Download the complete skill directory including SKILL.md and all related files
| name | gormes-landing-web |
| description | Improve the www.gormes.ai landing page content, UI, visual hierarchy, install flow, and public trust signals from current Gormes evidence. Use when the user asks to audit, redesign, polish, rewrite, or periodically improve the Gormes landing page or homepage UI. |
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.
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.
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/progress/static
asset mirror used before dev/build.webpages/landing/tests/home.spec.mjs - Playwright homepage expectations.webpages/landing/src/data/progress.json - roadmap mirror generated from the
canonical progress file.webpages/landing/legacy/go-renderer/ - deprecated former Go-rendered site;
reference/rollback only.benchmarks.json and webpages/docs/content/building-gormes/architecture_plan/progress.json - canonical proof inputs.State whether the pass is about:
If the change would require runtime behavior that is not shipped, route through
gormes-skill-manager instead of promising it on the landing page.
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.
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.
Prefer direct edits to the active Astro + Tailwind site:
src/data/landing.js;src/pages/index.astro;src/styles/global.css;scripts/sync-assets.mjs;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/ unless the old renderer is explicitly restored.
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.
Report: