القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| 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. |
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/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.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/, and do not wire build/sync/progress generation
back into it, 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:
Implement one selected repo-scoped Gormes row with tests. Use when next-work says decision=build. Do not use for decision=plan, broad parity audits, or untracked feature ideas.
Shape source-backed Gormes progress rows. Use for decision=plan builder handoffs, row splitting, feature maps, or parity planning. Do not use when decision=build or for runtime code.
Route Gormes work to the smallest repo-local skill chain. Use before substantial planning/building/refactor work, when unsure which Gormes skill applies, or when creating/improving repo-local skills.
Build one selected Gormes behavior with red-green-refactor. Use when the row or reproduced bug defines a test target. Do not use after decision=plan or for broad planning.
Move one bounded cmd/gormes command domain out of root files toward root main.go only. Use when thinning cmd/gormes, burning down loose root files, preserving CLI behavior, or catching refactor regressions during cmd moves.
Use when an agent is unfamiliar with a Gormes code area, a change crosses package boundaries, or a refactor needs a source-backed module map before edits.