Menu

Individual skill

the-homepage

0upvotes

Structure a dev-tool homepage that converts developers into champions. Use when the landing page is written for the buyer instead of the developer, reads as salesy, buries what the product does, or makes it hard to start. Pairs with the ShipReady homepage audit.

skills/07-the-homepage/SKILL.md

Read pinned source

Source commit 7919aa3d559bcf170c7ab20a8919d44eec5a7e2e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
339
Repository last updated
Nov 9, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# The homepage

> Write your homepage for the person who actually reads it: the **end-user developer**, not the CTO who signs the check. The developer becomes your champion and sells it internally for you.

**Use this when:** your homepage speaks to buyers/ROI, it's clever but vague about what the thing does, or a developer can't tell in 5 seconds whether to care, and can't start in 5 minutes if they do.

## The core rule (Czakon)

**Address end-user developers on the homepage; put enterprise/ROI/buyer messaging on separate pages** (enterprise, pricing, case studies). If you write the homepage for the buyer, you've written it for someone who isn't there.

## Framework: the sections, in order (Czakon)

1. **Hook / core message**: immediately: what *is* it? Use a category ("CI for monorepos"), a known-incumbent comparison ("a Datadog alternative"), or a plain statement. **Headline = what it is · subhead = for whom / what job.**
2. **Hero**: a real product shot; two CTAs: **Get started** (signup) *and* **Docs**. Answer "what's in it for me?" up top. Lead with the **how**, not the why.
Back to top