DEV Community

Cover image for Build a magazine-style landing page from your README with one agent skill
Lookbk
Lookbk

Posted on

Build a magazine-style landing page from your README with one agent skill

You have a good README and no homepage. The README explains the tool well enough, but every landing page template you open looks like every other SaaS page: a gradient, three icon cards, a testimonial carousel. You want something that reads more like a printed page, and you want it as a single file you can drop on any static host.

We built a skill for this called Mono Editorial Landing. It is one of our 38 free MIT skills. Your agent drafts the page from your README, you rewrite the headline together, and the build produces one responsive HTML file with its CSS inside. This post walks through the whole loop.

What the page looks like

The design is a black-and-white editorial layout: ink on warm white, a masthead with a thin "issue" line, a large serif headline, and an introduction with a drop cap. Below that come numbered columns divided by hairlines, feature spreads that alternate sides with framed figures captioned "Fig. 1", "Fig. 2", a centred italic pull quote, a list of questions, a closing line and a typewriter-style colophon.

Dark mode and an accent colour are a matter of changing three colours in the theme. The hero holds either a real waitlist form or two buttons, depending on whether your product is out yet.

Install the skill

Use whichever route fits your setup:

npx skills add lookbkdev/lookbk-skills --skill mono-editorial-landing
Enter fullscreen mode Exit fullscreen mode

Or, in Claude Code, add the marketplace and install the plugin:

/plugin marketplace add lookbkdev/lookbk-skills
/plugin install mono-editorial-landing@lookbk-skills
Enter fullscreen mode Exit fullscreen mode

You need Node.js 18 or newer and nothing else to install. Chrome, Chromium or Edge is used for the checks; the scripts find it, and you can set CHROME_PATH if they do not. The source lives at https://github.com/lookbkdev/lookbk-skills.

Step 1: draft from the README

The skill's folder is written as <skill> below. The first script reads your README, plus the package.json beside it if there is one:

node <skill>/scripts/from-readme.mjs README.md page.json
Enter fullscreen mode Exit fullscreen mode

The output is a page.json that already builds. The tool name becomes the brand, the tagline becomes a first headline, and the introduction becomes the lede. A "Features" list whose items start with a bold name turns into columns. Install and quick-start commands become a terminal figure, other sections become feature spreads with their screenshot or code, an FAQ section becomes the questions, and the repository becomes a button. Badges, logos, link rows, tables of contents, licence and contributing sections are skipped.

The script does not write copy of its own beyond labels like "Get started". It ends with three lists, and this is where you and the agent work together:

  • Write with the person: always the headline, and every feature title that is still a README heading such as "Install" or "How it works".
  • Cut to fit: text it shortened at a sentence or word boundary. Read each one again.
  • In the README but not on the page: sections it had no room for. Swap them in if they matter more.

If you have no README, or a thin one, the agent writes page.json from your notes or the docs, starting from one of the bundled examples.

Step 2: decide what the hero asks for

If the product is not launched, the hero gets a waitlist form. You choose which service collects the emails with hero.form. The providers are formspree, netlify, buttondown, or a generic endpoint for anything that takes a form post, such as your own API or a mailing-list form's action URL.

A minimal form block looks like this:

{
  "hero": {
    "title": "A calendar that stays *quiet*",
    "lede": "One or two sentences on what it is, for whom, and why.",
    "form": {
      "provider": "formspree",
      "id": "xayzbqwe",
      "button": "Join the waitlist"
    },
    "note": "Invites go out in small batches."
  }
}
Enter fullscreen mode Exit fullscreen mode

The title takes *word* for an italic word and \n for a line break, up to three lines. By default the page sends the form with JavaScript and shows your success or error message in place. Without JavaScript, or with "ajax": false, it falls back to a normal form post. Every provider but Buttondown also gets a hidden spam-trap field. Every "Join" button on the page scrolls to the form and puts the cursor in it.

If the product is already out, use hero.actions instead: a primary button (download, sign up, install) and an optional secondary one (docs, source).

Step 3: write the rest

Fields have hard limits, and the build tells you when you go over. Columns are two to four items with a kicker, title and text. Features are up to four spreads, each with an optional figure. A figure is one of four types:

  • image: a real screenshot or illustration, with required alt text.
  • window: an app screen drawn in the page style, with a sidebar and rows.
  • stats: two to four numbers that are true and sourced.
  • code: up to 14 lines for install commands or a config file. Lines starting with $ get a prompt.

The skill is strict about honesty here. Every number, quote, customer and claim must come from you, your README or a source you point to. The pull quote should be a real quote from a real person who agreed to it; leave it out otherwise. A window figure may use made-up example rows, but the caption should say so if names appear.

For style, the headline says what the reader gets, in their words, with one word carrying the italic. Column titles are short statements, not feature names.

Step 4: build

node <skill>/scripts/build.mjs page.json out
Enter fullscreen mode Exit fullscreen mode

The build lists every problem in page.json at once: missing fields, text over its limit, a nav link to an id that is not on the page, colours that do not contrast. It writes nothing until they are fixed. Once it passes, you get out/index.html, plus out/assets/ for pictures. It also prints where the form posts and what only you can confirm: the quote, the numbers and the window figures.

Step 5: check and look

node <skill>/scripts/check.mjs out/index.html
node <skill>/scripts/try-form.mjs out/index.html
node <skill>/scripts/screenshot.mjs out/index.html
Enter fullscreen mode Exit fullscreen mode

check.mjs loads the page at 390, 768, 1024 and 1440 px and must say ok at each width. It looks for anything wider than the screen or cut off, unreadable contrast, missing alt text, an unlabelled form field, more than one h1 and skipped heading levels.

try-form.mjs signs up with test@example.com in headless Chrome against a stand-in for the form service on your machine, so nothing reaches the real one. It shows what was sent, what the visitor sees afterwards, and what they see when the service fails. It must end with The form works.

screenshot.mjs saves out/screens/desktop.png and mobile.png. Open both. Does the first screen say what the product is? Does a headline break badly on a phone? Is a spread lopsided? Shorten the text or the figure until it sits right.

Step 6: put it live

Upload out/index.html and out/assets/ to any static host. If you use a waitlist, sign up once on the live page with your own address and confirm it reaches the service. When the page collects emails, link a privacy policy from footer.links.

A few failures are worth knowing. If the live form fails but try-form.mjs passes, the service rejected the post, so check the form ID, the endpoint's CORS settings and its status code. If the page shows system fonts, the web fonts could not be reached; install the families and set "fonts": "". If try-form.mjs says nothing was sent, rebuild instead of editing the HTML by hand, because the email field must stay required.

Try it

The skill is free, MIT licensed and works with any agent that reads SKILL.md files. You can see a preview and the full details on Lookbk, where the same catalogue lists 200+ skills.

This post was drafted with AI assistance and checked against the skill's SKILL.md.

Top comments (0)