landingforge: Instructions file for Claude Code

LandingForge — project guide for agents

LandingForge is a Claude Code plugin that manufactures and scores SaaS, dev-tool, and B2C consumer-app landing pages across four axes (conversion, organic SEO, AI-search/GEO, visual craft). See README.md for the architecture and references/ for the knowledge base.

Browser automation (REQUIRED for workflows and agents)

When any task needs to load, render, screenshot, or inspect a real web page — landing-page teardowns, scoring the calibration anchors, /landing-critique, build/visual QA — use the browser bundled with this plugin at scripts/browse. Do not use WebFetch for these, and do not reach for an externally-installed browser tool.

How:

B="${CLAUDE_PLUGIN_ROOT}/scripts/browse"
"$B" goto <url>                 # navigate (starts a browser on first use — there is no connect step)
"$B" js "<expr>"                # computed CSS / DOM facts (font-size, weight, letter-spacing, colors, JSON-LD, counts)
"$B" text                       # rendered copy
"$B" screenshot <path> --viewport   # above-the-fold; then Read the PNG
"$B" inspect <selector>         # computed style + box + aboveTheFold for one element
"$B" perf                       # navigation timings + LCP/CLS observed for this load
"$B" resize 390 844             # mobile fold checks
"$B" close                      # shut the session down when finished

It runs on the playwright already declared in scripts/package.json — cd scripts && npm install once (the postinstall fetches Chromium). Nothing global to install, nothing to connect to.

Why not WebFetch: it can't see rendered CSS or computed styles and gets bot-blocked on JS-heavy marketing sites — useless for visual teardowns and scoring.

Operating rules:

• The session persists across invocations. goto once, then probe that one page load as many times as you need. Re-goto only to change page — never to re-read the same one.
• Sessions are named. Concurrent work on different pages must pass distinct --session <name> values. Agents sharing a name share a tab and will clobber each other.
• For SPAs that poll, use "$B" wait --load (not --networkidle, which times out). A timeout is reported as reached: false, not raised — the run continues.
• Use --viewport for hero/above-the-fold screenshots (a full-page shot of a tall lazy-loaded page can capture a near-blank PNG).
• perf reports transferBytesKnown as a floor: cross-origin resources without Timing-Allow-Origin report zero bytes and are counted in opaqueCount. Never quote it as total page weight. Lighthouse (scripts/score.ts) owns the real CWV numbers.
• Close sessions you opened so a stray Chromium does not outlive the run.