nice to have
Back to the shelf Sign in Submit a kit
← All kits

Service Landing Page Kit

Build a service landing page after measuring real ones

How to use
Example output from Service Landing Page Kit

Service Landing Page Kit is a vibe coding kit for Claude Code and Codex. Build a service landing page after measuring real ones. It includes 9 fixes for pitfalls the maker hit in real work. Free.

When this helps

When you build a page for your own service, it looks obviously AI-made

What it does

Builds a one-page landing page (LP) for your service. Before writing, it captures and measures at least five real service pages (how the hero is laid out, text per section, image share, use of colour), decides which patterns to adopt, then rewrites the template. It checks the page against a list of what makes pages look AI-made, captures it on PC and phone, and compares it side by side with the reference sites before publishing. It never invents customer counts or testimonials; anything unknown stays as a placeholder and is listed at the end.

The fixes baked into this kit

  1. Gradient and dot-pattern backgrounds read as AI-madeA hero with a navy gradient, dot pattern, glow and floating chips was called '100% obviously AI-made'. Switched to a white background with copy → large photo → CTA, the layout common on real SaaS pages.
  2. Monotonous even with little textThe page had less text than the references but was called too wordy. The cause was alternating white/grey backgrounds and rows of identical cards. Added three dark bands, varied the background per section and gave images more area.
  3. Skipping the analysis means starting overBoth versions built without looking at real sites had to be redone. Now it captures five or more first and counts heading length, image share and colour bands before choosing patterns.
  4. Full-page screenshots repeat midwayChrome repeats the same area once a capture goes past about 16,000px. Tall pages are now captured in 8,000px pieces.
  5. Sticky header appears in the middle of full capturesThe sticky header showed up partway down the image. It is unpinned only while capturing.
  6. Hidden images counted as brokenImages hidden on phones never load because of loading=lazy, so they were counted as broken. Only images actually on screen are counted now.
  7. Generated photos show facesEven when told not to, a clear side profile came back. Now it first makes an empty room, then uses it as a reference to add a person seen from behind.
  8. Image generation refused when busyThe high-quality model returned 503 (busy) repeatedly. It now retries three times, 30 seconds apart, and suggests switching models.
  9. Test data and real names in product screenshotsReview-site screens showed 'test' and 'demo' clients, names that looked real, booking IDs and 'not working yet' notices. Rules for usable screens were set, and only the part you want read is cropped.

What's inside

  • An LP template you can rewrite (hero, features, safety, onboarding, FAQ, company)
  • Step-by-step flow (capture and measure five sites before writing)
  • What makes a page look AI-made, and how to fix it
  • A tool that captures and measures reference sites on PC and phone
  • A page check (horizontal scroll, broken images, placeholders left)
  • A tool that lines your page up against the references
  • How to ask for photos without faces, and a tool to make them
File list (30)
  • .env.example
  • .gitignore
  • AGENTS.md
  • CLAUDE.md
  • KIT.md
  • css/style.css
  • img/ph-band-1.svg
  • img/ph-band-2.svg
  • img/ph-band-3.svg
  • img/ph-final.svg
  • img/ph-hero.svg
  • img/ph-photo-a.svg
  • img/ph-photo-b.svg
  • img/ph-roles.svg
  • img/ph-screen-1.svg
  • img/ph-screen-2.svg
  • img/ph-screen-3.svg
  • img/ph-screen-sp.svg
  • lp.html
  • rules/CHECK.md
  • rules/FLOW.md
  • rules/PROMPTS.md
  • rules/TONE.md
  • tools/build.mjs
  • tools/check.mjs
  • tools/compare.mjs
  • tools/genimg.mjs
  • tools/lib/chrome.mjs
  • tools/lib/measure.mjs
  • tools/shoot.mjs

The first three decisions

  1. What the service is (whose work, what chore, how it gets easier)
  2. What you may and may not say (pricing, track record, company names)
  3. Colours (your company or service colours)

What you need

  • No extra costClaude Code or CodexThe AI rewrites the page. Both CLAUDE.md and AGENTS.md are included.
  • No extra costGoogle Chrome and Node.js 22+To capture reference sites and check your page. Nothing else to install.
  • Extra costA Gemini API keyOnly if you want AI to make photos. Not needed if you use your own.

How to use

Just paste this into your AI.

I want to use the nice to have kit "Service Landing Page Kit". Follow https://nicetohave.app/en/g/7HMKRMW4-•••••••••• and set it up.

Works the same in Claude Code or Codex.
Read what this tells your AI to do, before you paste it

If you would rather take the files yourself

Paste the line above and your AI fetches it. If your AI cannot fetch it, or you would rather download it yourself, start here.

Download the kit as a zip

  1. Unpack the zip you downloaded
  2. Open the resulting folder in Claude Code or Codex (in VS Code, "Open Folder")
  3. Type "start building with this kit". The instructions are inside (Claude Code reads CLAUDE.md, Codex reads AGENTS.md)

FAQ

How do I publish the finished page?
Once the check shows zero items to fix, the AI bundles everything needed for publishing. You upload that to wherever you host (Vercel, Netlify, a rental server, etc.). After it's live, the AI also checks that the page, CSS and images all load from the published URL.
Can I publish before I have real photos?
No. The images in the template are placeholders that only show where an image goes and how big it is. Bundling for publishing stops until they are replaced with real photos or screenshots.
Do I have to keep every section of the template?
No, you can delete whole sections you don't need (for example, the "who uses it" section if there is only one type of user). To add one, copy an existing section from the template rather than building a new layout from scratch.
How many tries does it take to get a usable AI-generated photo?
Rarely the first. In practice it took four attempts to get one keeper. Each image costs money, so if three tries don't work, change the scene instead—fewer people, or a closer shot of hands at work.
How do I give the AI my Gemini API key (the key for generating images)?
Copy the key, then just tell the AI "I've copied it." You don't need to paste it into the chat or open any files.

Reviews

Used it? Leave a rating
A few words are optional. A thank-you, or show off what you made. It goes to the maker.
Sign in with GitHub to write

Supporters

Once support opens, the people who backed this kit will be listed here.

Publisher
ohirutabeyo
Published
2026/10/07
Price
Free
Category
Documents
Personal data
Not handled
Security review
不要(問い合わせフォームは入っていません。届け先は使う人が自分のものを入れます)
What's inside
An LP template you can rewrite (hero, features, safety, onboarding, FAQ, company)Step-by-step flow (capture and measure five sites before writing)What makes a page look AI-made, and how to fix itA tool that captures and measures reference sites on PC and phoneA page check (horizontal scroll, broken images, placeholders left)A tool that lines your page up against the referencesHow to ask for photos without faces, and a tool to make them

More kits