agentsclimarketplace
Sign in

Forge website

Skill ForgeyClap/claude-forge/plugins/forge/skills/forge-website

Forge playbook for websites, landing pages, and frontend UI. Use when building or improving a website, landing page, marketing site, dashboard UI, or frontend — keywords: website, landing page, hero, CTA, responsive, mobile layout, UI, UX, accessibility, a11y, SEO, page speed, Lighthouse, frontend, React, Vue, Tailwind. Covers UI/UX, responsiveness, accessibility, SEO, performance, forms, and screenshot-loop review.From its SKILL.md

Install
npx -y skills add ForgeyClap/claude-forge --skill forge-website

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.7 KB, 575 tokens by cl100k_base, as published. Nobody here has run it

Forge playbook — Website / landing / frontend

Do not duplicate ECC skills — defer to: design-is (design audit), browser (screenshot loop). This file is orchestration only.

Hard rules

  • Mobile and desktop layout verified by screenshot before claiming done.
  • No placeholder/Lorem/test/mock content in anything headed for prod.
  • Forms validate input and hit a real endpoint; clear error + success states.
  • Any analytics/form keys live in env, never in the committed bundle.

Team (conditional by stack/level)

  • Lead: planner / architect.
  • Build review: react-reviewer or vue-reviewer (by stack).
  • Audits (parallel): a11y-architect, seo-specialist, performance-optimizer.
  • Copy/CTA: marketing-agent.

Skills / commands / MCP

design-is (pick a real style direction first — see ~/.claude/rules/ecc/web/design-quality.md), browser (mobile+desktop screenshots), /react-build + /react-review (or the Vue equivalents), /test-coverage. Canva MCP only if asset generation is explicitly requested. humanizer skill (.claude/skills/humanizer/SKILL.md) MAY run as an on-demand rewrite pass on client-facing marketing/landing copy — never on exact-command setup docs or forge-report output, and not always-on (34KB context cost). When a build uses GSAP/ScrollTrigger for scroll-driven or compositor-friendly motion (per ~/.claude/rules/ecc/web/performance.md), load the relevant gsap skill (.claude/skills/gsap/<skill-name>/SKILL.md) on demand for correct API usage — not always-on.

Fan-out & flow

L2 for a single page, L3 for a multi-page site. Serial: design direction (design-is) → build → audits → fixes → review gate. Parallel: a11y ∥ seo ∥ performance ∥ copy audits on the built artifact (independent).

Domain gates

Accessibility pass; SEO meta/OG + canonical; performance budget (see ~/.claude/rules/ecc/web/performance.md); responsive at ~360/768/1280; CTA clarity; no broken links.

Ship-readiness (unique)

Screenshots at mobile+desktop breakpoints; no test copy; all CTAs/links resolve; forms submit to a real endpoint with validation; favicon/meta/OG present; 404 route; secrets in env. The ship-readiness website checklist is advisory; optionally run codex-reviewer (Codex) on important code — not a blocker.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most marketing audience skills give in 575 tokens

Counted across 690 of the 894 authors here whose files we hold, read 2026-08-07

  • Apply Poppins font to headingsin 41 of 690, across 6 files
  • Apply Lora font to body textin 41 of 690, across 6 files
  • Use Arial fallback for headingsin 39 of 690, across 4 files
  • Use Georgia fallback for body textin 39 of 690, across 4 files
  • Maintain text hierarchy and formattingin 39 of 690, across 4 files
  • Use accent colors for non-text shapesin 38 of 690, across 3 files
  • Use RGB values for precise color matchingin 38 of 690, across 3 files
  • Use brand colors for primary text and backgroundsin 36 of 690, across 1 file
  • Read product marketing context file before asking questions, starting, or auditingin 35 of 690, across 23 files
  • Use active voice instead of passive voicein 26 of 690, across 10 files
  • Implement or generate appropriate JSON-LD structured datain 24 of 690, across 17 files
  • Prioritize clarity over clevernessin 22 of 690, across 8 files

Said here and by no other author read

  • verify mobile and desktop layouts by screenshot before claiming done
  • use real content only in production-bound output
  • validate forms and submit them to a real endpoint
  • store analytics and form keys in environment variables
  • run design direction before build
  • run accessibility SEO performance and copy audits in parallel

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.