Payload CMS + Astro starter
Describe what you want. Your agent builds it.
You describe outcomes in plain language; the agent turns them into real CMS blocks, components and database migrations — following a pipeline that will not let it skip the parts that keep your content safe.
View the GitHub repository01 / Workflow
How you work with this
- 01
Describe an outcome
Plain language. "A pricing section", "make the hero say this", "here is my Figma".
- 02
Approve the design
A new section is built in Storybook first. Nothing reaches the database without your yes.
- 03
It gets wired up
Block, editable fields, renderer, types and a database migration — in one pass.
02 / Inside the starter
Skills worth knowing about
- 01
vibe-codingThe front door. Turns what you asked for into a spec and picks the rest.
- 02
setupFirst run on a new machine: secrets, Docker, migrations, the first admin.
- 03
design-modeDesigns a new section in Storybook and holds the approval gate.
- 04
debug-modeSomething broken? Reproduces it against real logs instead of guessing.
- 05
security-auditSeven areas against the OWASP Top 10 before you launch.
- 06
+ 10 moreMigrations, SEO, data fetching, design system, CMS migration. You never invoke one — the agent picks.
03 / Stack
Built on
- Astro 6.4
- Payload CMS 3.81
- TypeScript 5.9
- PostgreSQL 17
- Tailwind CSS 4.1
- Storybook 9
- Turborepo
- Docker Compose
- Mailpit
Looking to build on Payload?
Work with WAYF to turn the starter into a production-ready website.