compose-page
Skill1 starsChanged 13 days agoMITView on GitHub
Use when adding or editing a page or blog post in this repo — finding the right MDX file under src/content/, writing frontmatter, choosing blocks from src/blocks/, and filling the YAML `blocks:` list. Use whenever asked to add a page, edit copy, add, remove or reorder a section, change a hero or CTA, or publish a post. Not for building a new kind of section — that is compose-block.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- robotostudio/turbo-start-web-agenttheir own version, first seen Sep 30, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- robotostudio/turbo-start-web-agent★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- compose-blockSkill
- write-a-skillSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 34
The MDX body below the frontmatter is ignored: Do not write copy there.
- Distinctive: line 60
Start every new page as a draft.
- Very specific: line 87
If no block can say what the page needs, that is a code change: use the compose-block skill.
- Very specific: line 114
Do not stack blocks at random.
- Distinctive: line 134
Check whether a dev server is already running before starting another.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Compose a page
Pages here are data, not code. A block page is a YAML blocks: list in the
MDX frontmatter; every entry is validated by a strict Zod schema at build
time. You are filling in pre-built blocks, not writing components. If the
build fails, the message names the exact field and what it expected. Read it,
fix the content, and never loosen a schema to make content pass.
1. Find the file
| Content | Path | URL |
| Pages | src/content/pages/**/*.mdx | path = URL: index.mdx → /, about.mdx → /about, services/astro.mdx → /services/astro |
| Blog posts | src/content/blog/*.mdx | /blog/<filename> |
| Authors | src/content/authors/*.mdx | /authors/<filename> |
- A new page is a new file. Filenames are kebab-case.
- A page's first path segment cannot be
blogorauthors;src/lib/content.tsthrows, because it would shadow those routes. - The header and footer links are hard-coded in
src/components/site-nav.astroandsrc/components/site-footer.astro. A new page is not linked anywhere until you add it there (ask first; that is chrome, not content).
2. Pick the page mode
src/pages/[...slug].astro branches on blocks:
blocks:present → block page. Rendered full-width inBaseLayout. The MDX body below the frontmatter is ignored. Do not write copy there.- No
blocks:→ prose page. Rendered inPageLayout: an<h1>fromtitle, then the MDX body as typography (about.mdx,services/astro.mdx).
blocks: [] fails the build. Remove the line or add a block.
3. Frontmatter
Schemas live in src/content.config.ts. Every collection is .strict(), so
a misspelled or unknown key fails the build.
---
title: "Astro websites" # required
description: "…" # required, 80–220 chars, aim for 120–160
publishedAt: 2026-05-12 # required, ISO date
draft: true # new pages start true
---descriptionis also the meta description and the social preview text. The length rule is enforced; write a real sentence, not a tagline.metaDescription(optional, same 80–220 rule) overridesdescriptionin meta tags only. Use it when the on-page intro makes a poor search snippet.updatedAt(optional ISO date): set it when you materially change a page.draft: truerenders inpnpm devand is left out of production builds. Start every new page as a draft; flip it once the owner approves.- The Open Graph image is generated from
title(/og/<slug>.png). There is no image field to set.
Blog posts also take author (required; must match a filename in
src/content/authors/ without .mdx, e.g. jono), tags (string list) and
featured (boolean). Posts have no blocks:; the body is the post.
4. Choose blocks
The schema in src/blocks/<type>/schema.ts is the source of truth. Read it
before using a block. This table is a map, and the schema wins if they
disagree.
type | Use it for | Fields (? = optional) | Counts |
hero | Page opener, yellow | title, text, buttons | 1–3 buttons |
figures | Row of big numbers, black | items: [{value, label}] | 2–6 items |
card-grid | Icon cards with a title, yellow | title, items: [{icon, title, description}] | 2–4 items |
feature-strip | Short benefits on black | title, items: [{icon, title, description}] | 3–6 items |
image-feature | Image beside copy and stats | heading, body, image, badge, stats: [{value, label}] | 1–4 stats |
video-feature | Mux video with badges and tiles, black | heading, body, video, badges: [{value, label}], tiles: [{icon, label}] | 0–2 badges, 2–4 tiles |
pricing | Plan cards | title, plans: [{name, price, unit, features[], featured?, cta: {label, href}}] | 2–4 plans |
cta-banner | Closing call to action, black | title, text, buttons | 1–2 buttons |
src/content/pages/index.mdx uses all eight with real copy. Copy from it.
If no block can say what the page needs, that is a code change: use the
compose-block skill. Do not fake a section by bending another block's
fields.
5. Field shapes shared across blocks
- Buttons (
hero,cta-banner):{ label, href, variant?, icon? }.variantisfilled(default) oroutlined. Put onefilledbutton first; any second one isoutlined.hrefcan be a path (/contact), a full URL,mailto:ortel:. - Icons: any Lucide name in kebab-case
(
zap,map-pin,shield). A name that does not exist fails at render. - Highlight: in
hero.titleonly, wrap words in==…==to set them on a black bar on their own line:"CALL 1800 ==HOT ROD==". Other blocks print the==literally. - Images:
image: { key, alt }.keyis a Vercel Blob pathname (e.g.taxi.jpeg) and the build checks it exists in Blob. Upload in the Vercel dashboard; never put content images inpublic/.altis required and describes the picture. - Video:
video: { playbackId, title }.playbackIdmust be a public Mux playback ID that exists in the Mux account; the build checks it. - House style: block titles are UPPERCASE (
"WHAT'S UNDER THE HOOD"); body copy is sentence case. Quote every YAML string that contains:,#,'or starts with a special character. Quoting all strings is safest.
6. Give the page a shape
Do not stack blocks at random. The home page runs: hero (what it is) →
figures (proof) → card-grid and feature-strip (what you get) →
image-feature / video-feature (show it) → pricing → cta-banner (one
action). A short landing page is often hero → one feature block →
cta-banner. End on a single cta-banner.
Black blocks (figures, feature-strip, video-feature, cta-banner) draw
checkerboard dividers above and below themselves, so two black blocks in a row
get two dividers back to back. Alternate yellow and black where you can.
7. Validate, then look
pnpm build # runs every Zod schema; the error names the file and field
pnpm dev # http://localhost:4321/<slug>- Both need the Blob and Mux tokens locally. If they are missing, run
shelve pull(see Commands inAGENTS.md); never paste token values into chat. - Check whether a dev server is already running before starting another.
pnpm buildchecks a draft's frontmatter but does not render the page, so render errors on a draft (an unknown icon, for one) only show inpnpm dev. Open every draft you touch in the dev server.- A green build is not done. Open the page and read it at phone width and desktop width. Check the buttons go where they should.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

