Skip to content
AnonyfoxPublic

About

Agent-first landing page compiler: one Go binary plus skills that make Claude Code, Codex or Cursor research real buyers and ship one checked, fast static page with a payment link.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

1 star

Watchers

0 watching

Forks

Repository files navigation

lfm

CI codecov Release Go Reference License: MIT

lfm is an agent-first landing page compiler for people using coding agents to research buyers and build a page for one offer. Its own site, lfm.cash, compiles with 0 errors and 0 warnings after the same research, design and implementation process.

curl -fsSL https://lfm.cash/install.sh | sh

lfm check flags a generated page (violet gradient, cream background, stock phrases), then passes lfm.cash with 0 errors and 0 warnings

Your agent writes an HTML template with its config and assets; lfm compiles them into a standalone static folder. It checks correctness, speed, accessibility, search metadata and generic design defaults before publishing output. Every finding says how to fix it.

One Go binary produces one folder you can upload anywhere, with no framework or runtime required. The agent interface is a CLI with --json and SKILL.md.

How it compares

The landing page tool comparison describes these workflow fits:

  • Code / agent: lfm, one checked static page; Astro, multi-page components; Hugo, large content sites.
  • Visual editor: Carrd, simple one-page sites; Framer, design, interactions and CMS.
  • Agents read copy, metadata and accessibility findings together.
  • lfm lacks managed hosting and visual editing.

Ask your agent

Give any coding agent (Claude Code, Codex, Cursor, OpenCode, Gemini CLI and others) this request:

Make a landing page for my sourdough course with lfm: https://lfm.cash/SKILL.md

SKILL.md tells the agent how to install lfm, set up a project and follow the process. To have every agent session pick it up by itself for requests like "generate me a landing page", install it once as a user skill:

for d in ~/.agents/skills/lfm ~/.claude/skills/lfm; do mkdir -p "$d" && curl -fsSL https://lfm.cash/SKILL.md -o "$d/SKILL.md"; done

~/.agents/skills is read by Codex, Cursor, OpenCode, Gemini CLI and GitHub Copilot; ~/.claude/skills by Claude Code. Keep only the one your agents need.

On Grok Bot, add the lfm.cash bot: it installs lfm on its own computer and runs the same process, asking you only what you decide. Its setup is in docs/grok-bot.md.

Install

The script at the top downloads the release for macOS or Linux (amd64 or arm64), checks it against the release checksums and puts lfm in ~/.local/bin, without sudo. LFM_VERSION=v0.0.2 pins a release and LFM_INSTALL_DIR changes the folder. With Homebrew:

brew install anonyfox/tap/lfm

With Go 1.26 or newer:

go install github.com/Anonyfox/lfm/cmd/lfm@latest

Chrome or Chromium builds critical CSS and prints with lfm compile --release; --validate adds browser audits and Lighthouse scores. Missing validation tools are reported as errors, never installed.

Start a page

lfm init sourdough-course   # a starter project that compiles cleanly
cd sourdough-course
lfm skills install          # the process skills, where your agent loads them
lfm compile                 # findings, output/ and the next step

Then ask your agent for the page. It works in three phases, each with its own skill:

  1. research: real buyer voices and competitor pages, verbatim and dated, into research/.
  2. design: concept.md from the research: buyer, mechanism, direction, palette, type, imagery, motion and copy, every decision cited to a source.
  3. implementation: the page from concept.md, until lfm compile --release --validate is clean and every saved frame holds up on phone and desktop.

The compiler checks each handover: missing research, an uncited concept or a page that ignores the concept's palette, type and imagery show up as findings. Every report ends with the next step, such as Next (design): write concept.md from the research., and names the skill for it, so an agent working unattended stays on the path. When it says deploy, upload output/ to the URL in lfm.json.

For agents

Command Use
lfm What lfm is, how to start, every command
lfm <command> -h Usage, flags and behaviour of one command
lfm skills The process skills in the order a page needs them
lfm skills <topic> One SKILL.md, rendered for the installed version
lfm skills install All skills into the project's .agents/skills or .claude/skills
lfm compile [--release] [--validate] [--browser-jobs N] [--json] Check and build; the last line is the next step
lfm check <url|folder|file> [--release] [--json] Check any built page from a URL or disk
lfm serve --open Live preview that recompiles on every save
lfm rules [id] Every check, or what one means and how to fix it

lfm skills install updates the folders that already hold lfm skills. Otherwise it writes to .claude/skills when Claude Code runs it or the project has only a .claude folder, and to .agents/skills in every other case; --agents, --claude and --global choose explicitly. Each installed SKILL.md records the lfm version and a digest of its text, so running it again after an update replaces untouched copies and keeps copies the project changed (--force replaces them too). lfm compile never writes skill files. After an upgrade, run the printed lfm skills install command to update each folder with older copies.

lfm compile --json prints the result as one object with errors, warnings, the findings under validation, next (phase, do, skill) and the installed skills. Exit status is 0 when output/ was written, 1 when errors kept it unchanged or there is no project, and 2 for a mistake in the command line.

Every compiled page includes a black footer with a boxed “crafted with lfm” link and the fixed Anonyfox credit. Configure branding, link groups and badges with footer, or set "footer": false for a client storefront.

Made with lfm

lfm.cash is an lfm project, built by an agent through the same three phases: 120 buyer posts and 20 competitor pages, a concept that chose one of ten directions with every decision cited, and a page that compiles with 0 errors and 0 warnings. Its proof section compiles the page an agent wrote from one sentence without lfm, with the agent's file and lfm's full report.

What a compile guarantees

  • Correct: every template value exists and has the right shape; config mistakes point at their JSON key; links match the declared URLs; HTML parses without browser repairs.
  • Fast: CSS and JS are bundled and minified, small assets inlined, large ones emitted as content-named files, images sized against layout shift, HTML compacted without touching text.
  • Findable and shareable: canonical URL, metadata, headings, structured data and social previews are checked; sitemap and root robots files are generated; preview image sizes come from the real files.
  • Usable: controls have names, labels and focus order work, forms and disclosures behave, text keeps its contrast.
  • Distinct: typical generated-design defaults (stock palettes, eyebrow labels, emoji bullets, icon-card grids and more) and stock phrases of generated copy are reported, with an explicit way to keep one deliberately; the page is held to the palette, typefaces, imagery and phrases its concept.md decided.
  • Sellable: a Stripe Payment Link or Checkout offer shows its price, and the page links the legal pages a purchase needs.
  • Seen whole: --release --validate scrolls the page at phone and desktop sizes, saves every frame and reports empty stretches, sideways scrolling, covered or unreadable text, split values and missing glyphs.
  • Safe to ship: nothing is written until all checks pass, and a failed compile keeps the last good output.

FAQ

What is an agent-first landing page compiler?

lfm gives coding agents a CLI and skills for research, design and implementation, then checks and compiles their template into static files. Reports include findings, fixes and the next step; --json exposes the same information to an agent.

Can I use lfm with Claude Code, Codex or Cursor?

Yes, as well as OpenCode, Gemini CLI and other coding agents. Give the agent the request under Ask your agent, or install the entry skill for future sessions.

Where can I host an lfm landing page?

Upload output/ to a static host at the URL declared in lfm.json. The compiled page needs no framework or server runtime; see compiling for output details.

Can lfm check an existing website?

lfm check accepts a URL, folder or file without an lfm project. See checking any built page for targets, limits and browser checks.

Do I need Chrome or Lighthouse to use lfm?

They are optional: Chrome or Chromium enables browser checks in lfm compile --release --validate, and Lighthouse adds its scores. Browser validation requires both tools; releases reuse cached outputs and render missing critical CSS and prints.

Docs

License

MIT · lfm.cash

About

Agent-first landing page compiler: one Go binary plus skills that make Claude Code, Codex or Cursor research real buyers and ship one checked, fast static page with a payment link.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages