Hi PageAI team - I found this starter through your vibe coding guide. Since it already has Cursor/Claude rules for landing page components and next/image, I think one small missing path is how the agent should source believable real photos when building public pages.
I built a no-key image CLI/API/MCP called tteg: https://tteg.kushalsm.com / https://github.com/kiluazen/tteg
Possible rule snippet for .cursor/rules/landing-components.mdc or CLAUDE.md:
When a landing page needs a believable real-world image, save a local asset instead of leaving a placeholder:
`uv tool install tteg`
`tteg save "<query>" ./public/static/images/<name> --orientation landscape`
Use the saved file with `next/image`.
The hypothesis is that this helps PageAI/vibe-coded pages avoid placeholder blocks and external image URLs without asking the user for an Unsplash developer key.
If this does not fit PageAI's workflow, I would be interested in the objection: do you prefer generated images, bundled images, or provider-specific image sourcing?
Thanks,
Kushal
Hi PageAI team - I found this starter through your vibe coding guide. Since it already has Cursor/Claude rules for landing page components and
next/image, I think one small missing path is how the agent should source believable real photos when building public pages.I built a no-key image CLI/API/MCP called
tteg: https://tteg.kushalsm.com / https://github.com/kiluazen/ttegPossible rule snippet for
.cursor/rules/landing-components.mdcorCLAUDE.md:The hypothesis is that this helps PageAI/vibe-coded pages avoid placeholder blocks and external image URLs without asking the user for an Unsplash developer key.
If this does not fit PageAI's workflow, I would be interested in the objection: do you prefer generated images, bundled images, or provider-specific image sourcing?
Thanks,
Kushal