agentleFS
Sign inStart free
ForgeyClapForgeyClap/claude-forge/.claude/skills/forge-website/SKILL.md

forge-website

Skill2 starsChanged 34 days agoMITView on GitHub

Forge: websites, landing pages, and frontend UI: website, landing page, responsive, mobile layout, SEO, accessibility, Lighthouse, React, Vue, Tailwind.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    No placeholder/Lorem/test/mock content in anything headed for prod.

    line 12
  2. Very specific:

    When a build uses GSAP/ScrollTrigger for scroll-driven or compositor-friendly motion (per ~/.claude/rules/ecc/web/performance.md), load the …

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.
  • Meta and sharing basics: every page has a unique title and meta description, a canonical URL, Open Graph title/description/image, and JSON-LD (Organization or WebSite) where it fits — checked in the built HTML.
  • Performance proof: run Lighthouse or PageSpeed on the built site and report LCP, CLS and INP; numbers measured on localhost are labelled "local, indicative".

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free